> 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/user/guide/devices-and-settings/location-and-movement/odometer.md).

# Odometer

Tracks a vehicle's total mileage and lets you correct measurement error. Readings can come from GPS-based mileage, hardware/CAN mileage, a tachograph, or a measurement sensor you've created. It integrates with [Fleet maintenance](/docs/user/guide/fleet-management/maintenance.md) so you can schedule service by mileage and receive reminders.

![](/files/dvEQ1brRMrUcCpYWPLtH)

## Settings

* **Data source**: GPS-based mileage, hardware/CAN mileage, tachograph, or a measurement sensor. Additional sources appear only after you create the matching [measurement sensor](/docs/user/guide/devices-and-settings/vehicle-sensors/measurement-sensors.md).
* **Current value**: Set the odometer to match the vehicle. Kilometers, 0–99,999,999, up to 2 decimals.
* **Correction multiplier**: Adjust readings up or down by a percentage. Range about −95% … +95% (a positive value increases readings, negative decreases them).

## Activation

{% stepper %}
{% step %}

### Open the block

Open **Devices and settings**, select the object, and go to the **Odometer** block.
{% endstep %}

{% step %}

### Add the odometer

If none exists yet, click **Add odometer**.
{% endstep %}

{% step %}

### Choose a source and set the value

Pick the data source, set the initial mileage value, and click **Save**.
{% endstep %}
{% endstepper %}

## Availability

Appears on device models that support an odometer.

## Limitations

* The Navixy platform odometer rarely equals the vehicle's physical odometer. It counts all GPS points and allows for manufacturer error. Use the multiplier to correct a consistent offset, and collect about 200 km of data first to estimate it.
* Additional sources (e.g. CAN mileage) only appear after the matching measurement sensor is created.
* The **Odometer** value is also accessible from the device's [Object widget](/docs/user/guide/tracking/objects-list/object-widget.md).

## See also

* [Engine hours](/docs/user/guide/devices-and-settings/location-and-movement/engine-hours.md): the equivalent counter for engine running time.
* [Fleet maintenance](/docs/user/guide/fleet-management/maintenance.md): schedule service by mileage.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/user/guide/devices-and-settings/location-and-movement/odometer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.