> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/accuracy-and-freshness-of-tracker-data.md). # Accuracy and freshness of tracker data Tracker accuracy depends on GPS conditions; platform filters unreliable data with too few satellites or interference from jammers ## Question Are the data provided by GPS trackers (location, events) accurate and up-to-date? ## Answer The accuracy and freshness of tracker data depend on both the device itself and the conditions under which it transmits data. For example, if a tracker loses GSM connection, it won't be able to send data to the platform in real time. In this case, most devices store data in their internal memory (exact behavior depends on the model). Once the connection is restored, the tracker uploads this historical data in chronological order. These uploads are clearly marked. If the data is more than 5 minutes old, the platform shows that while the data was received recently, it is no longer current. The device status in this case will indicate "GPS not updated." Regarding accuracy: if the tracker is indoors with a weak satellite signal or is affected by a GPS jammer, it may start reporting incorrect or imprecise coordinates. The tracker calculates its own position, and the platform displays this information as provided. In cases where the tracker can't reliably connect to satellites or is under a strong GPS jammer, it may report very few satellites (for example, fewer than two), and the platform automatically filters out these unreliable data points. Some advanced trackers can detect signal jamming and send a specific event to the platform to indicate this. However, if the device does not support this feature, there is no reliable way for the platform to identify jamming on its own. ## Links * [Connection status](/docs/user/guide/tracking/objects-list/connection-state.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://navixy.com/docs/qna/using-navixy/accuracy-and-freshness-of-tracker-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.