What the tracker can see
Every insight, and the signal behind it
A Teltonika FMC150 reports a fixed set of AVL elements, and this fleet's devices send exactly fifteen of them: 12, 13, 16, 21, 24, 68, 69, 181, 182, 199, 200, 239, 240, 241, 449. Everything the dashboard shows is built from those, and anything that would need an element outside that list is marked as such below rather than estimated into existence.
Position, trips and distance
In the productGNSS lat/lng · AVL 16 (total odometer, metres) · AVL 240 (movement)
Every trip, stop and kilometre on the dashboard comes from these. Distance is taken from the odometer in metres and cross-checked against GPS hops, which agree to within 0.03%.
Overspeeding
In the productAVL 24 (speed) · GNSS speed
Speed arrives with every frame and is already stored on each telemetry row, so a limit can be applied over any window without touching the device.
Idling and idle fuel waste
In the productAVL 239 (ignition) · AVL 24 (speed) · AVL 13 (fuel rate)
Engine on with the vehicle stationary. The tracker never sends an idling event — that scenario is not enabled — so FuelSense derives the stretches from ignition and speed, timed from the record timestamps rather than frame counts.
Harsh acceleration and braking
Derivable from stored dataAVL 24 (speed), sampled ~1 s apart while driving
Not sent as events, but computable: the change in speed between consecutive fixes gives acceleration directly. At the cadence this device reports while moving, a hard stop is unmistakable in the series.
To have it: Needs the derivation built — no hardware or configurator change.
Harsh cornering
Derivable from stored datagps_raw.angle (heading), stored on every device frame
Heading is captured with each frame. Rate of heading change against speed identifies a corner taken hard, without an accelerometer event.
To have it: Needs the derivation built — no hardware or configurator change.
Crash, towing, jamming, power unplug
Not possible on this hardwareAVL 247, 246, 249, 252 — not enabled, never sent
These are device scenarios: the tracker computes them internally and emits an event only when the scenario is switched on in its configuration. This fleet sends 15 elements and none of these are among them.
To have it: Enable the scenarios in the Teltonika configurator. No new hardware, but the device must be reconfigured.
Fuel level in the tank
Not possible on this hardwareAVL 48 / 89 / 201 / 389 — absent, no sensor fitted
Nothing on this vehicle measures how much fuel is in the tank. During a verified 11.5 L refuel, AVL 12 sat flat at 7,514 ml through the entire fill and only rose once the engine restarted — it counts fuel burned and cannot decrease.
To have it: A capacitive level sensor wired to the analog input, or a CAN adapter reading the vehicle bus. Roughly $60–150 per vehicle.
Fuel consumed
In the productAVL 12 (fuel used, ml accumulator) · AVL 13 (burn rate, L/h)
A running total of fuel burned, built from how the vehicle actually moved. It is a model, not a measurement, so every trip carries a confidence score with its reasons attached.
Why we publish this
A fuel figure the tracker cannot support is worse than no figure at all — it gets a driver accused, survives one round of scrutiny, and then loses the manager's trust in every other number on the screen. Each insight above either has a signal behind it or says plainly what it would take. Where the evidence runs out, FuelSense says so instead of guessing.