Known issues & legacy fields - Telemax Docs

This page lists unit conventions and known behaviours of the Telemax API response format.

Units reference

Fields where the unit is not obvious from the field name:

Field	Unit	Notes
`speed`	km/h
`odometer`	km
`voltage`	V (volts)	Vehicle battery voltage
`fuelLevel`	% (0–100)	Integer percentage
`fuelVolume`	litres (float)	Nullable — `null` for vehicles without a volumetric sensor. V2 only.
`drivingTime`	seconds	`utcTime` − `startMovingTime`, in whole seconds; `null` when `startMovingTime` is `null`. See Last position
`ignitionTime`	seconds	Never `null`. Engine on: request time − `utcTime`; engine off: the duration of the previous ignition-on period. See Last position
`engineHours`	—	Always `0`; not populated
`fatigue`	.NET TimeSpan string	`[d.]hh:mm:ss[.fffffff]`. Always `"00:00:00"` on single-vehicle last position. See Last position
`distance` (TripDto)	km	Trip distance, measured inside the requested window; `null` when either odometer reading is missing
`distance` / `realDistance` (nearest)	degrees	Planar distance from the query point; `distance` is rounded to a multiple of 100, so results are not in nearness order. See Nearest vehicles
`radius` (nearest parameter)	degrees	Compared with the rounded `distance`. See Nearest vehicles
`lat` / `lng`	WGS84 decimal degrees
`course` / `direction`	degrees	N = 0°, E = 90°, S = 180°, W = 270°
`secondsAgo`	seconds

Timestamp format

Timestamps serialise as 2025-05-01T14:32:00 (no fractional seconds, no Z suffix). Exceptions: trip replay startTimeUser/endTimeUser use MM/dd/yyyy HH:mm:ss, and webhook Timestamp values are ISO 8601 with Z and can include fractional seconds (Webhooks).

Field suffix	Timezone
`utcTime`, `startMovingTime`, `lastMovementTime`, `startedTime`	UTC (despite no `Z`)
`endTime`	Server-local time, which is UTC on the hosted API
`userTime`, `startMovingTimeUser`, `lastMovementTimeUser`, engine-code `detectedAt`, replay `timeUser`/`startTimeUser`/`endTimeUser`	The API key’s time zone (offset not included in the string)
`*Formatted` fields (e.g. `userTimeFormatted`)	The API key’s date format plus `hh:mm:ss tt` (e.g. `"15/01/2024 12:30:00 PM"`)