> 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/speed-does-not-match-with-device-status-in-the-point-report.md).

# Speed does not match with device status in the point report

Status in the point report reflects trip state based on parking detection settings, not the instantaneous GPS speed at that moment

## Question

Why does speed not match the device's status in the points report?

## Answer

It's quite common to think that the speed is directly related to the status in the points report, but it also takes into account the parking detection settings.

This means that if the car is on a trip and there is a red light on the road, the vehicle will stop, showing 0 speed, but the status may still be **moving** due to the fact that the vehicle is still on a trip.

On the other hand, if the vehicle is parked and there is GPS drift, but the ignition is set to be considered in the parking state, then it will remain parked even though it might show speed.

## Links

* [Types of reports](/docs/user/guide/reports/report-types.md)
* [Parking detection](/docs/user/guide/devices-and-settings/location-and-movement/parking-detection.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/speed-does-not-match-with-device-status-in-the-point-report.md?ask=<question>&goal=<user_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.