Fit a tracker to your vehicle and FuelSense shows you how far it drove, how long it sat idling with the engine running, roughly how much fuel that used, and what it cost in naira.
Works with the Teltonika FMC150. No fuel sensor to install.
Every vehicle sits on a live map with its trail behind it. Trips open and close from the ignition, stops are detected and given real addresses, and the tank drains in step with the distance. Scroll to drive the route.
Harsh braking, harsh cornering and harsh acceleration are computed from the speed and heading the tracker already sends — no extra sensor, no accelerometer scenario to switch on. Declare a speed limit and sustained stretches above it are found the same way. The track is coloured by measured speed, so a flagged moment is something you can see in context rather than a label you have to trust.
One drive, every detection the tracker supports, in the order they fired.
Speed
18 km/h
Distance
0.0 km
Tank (modelled)
39.7 L
Fuel spent
₦0
Ignition ON · Depot, Kubwa
AVL 239 ignition edge
4.1 m/s² · 0.42 g · from 63 km/h
Derived from the GPS speed trace
3.6 m/s² lateral at 51 km/h
Speed × rate of heading change
118 km/h peak · 1 min 40 s over
Measured speed vs your 100 km/h limit
6 min 12 s · 0.12 L · ₦156
Engine on, speed below 2 km/h
Scripted demonstration, not a live vehicle. The detection method, thresholds and units are the ones the product actually uses — this particular drive is not real.
What is not here matters as much. Nothing on this page comes from an engine computer, because these trackers have no CAN or OBD link — so FuelSense does not claim engine load, RPM or a sensed fuel level. Every colour above is derived from position, speed and time, and the replay shows you the working.
You know what you paid at the pump. You do not know how much of it moved the vehicle, how much burned standing still with the engine running, or how much never reached the tank. Every argument with a driver becomes one person’s word against another’s.
₦0
Per litre, and moving
Pump prices change faster than receipts accumulate. You set the price; earlier months keep the price that applied when the fuel was actually burned.
0 L/h
Burned going nowhere
A 2.5L engine idling in traffic. Twenty minutes at a gate is fuel spent on zero kilometres, and invisible without engine data.
0%
Of trips, evidenced
Every trip carries its route, stops, idle time and fuel. Disputes get settled with a replay, not an accusation.
Nothing is spliced into the fuel line and there is no sensor in the tank. The work is done by a Teltonika FMC150 fitted to the vehicle, and by the satellite fixes it already collects.
An FMC150 wires into the vehicle’s power and ignition. From that moment it reports position, speed, ignition and movement over the mobile network: every few seconds while driving, hourly at rest.
AVL 239 · ignition
AVL 240 · movement
AVL 16 · odometer
The device computes fuel itself. Using satellite-measured speed and acceleration against the vehicle’s consumption profile, its firmware reports a running total of fuel used and the rate it is burning right now.
AVL 12 · fuel used (ml)
AVL 13 · fuel rate (L/h)
FuelSense keeps a virtual tank per vehicle, drains it against real burn, credits it from the receipts you log, and prices the result at the fuel price in force that day so last month’s spend never changes when today’s price does.
30.4 km ÷ 7.0 km/L
= 4.3 L × ₦1,330 = ₦5,779
The easy way to estimate fleet fuel is to multiply distance by a figure from a brochure. That figure assumes smooth roads, steady speeds and no air conditioning, none of which describe Lagos or Abuja. It cannot tell a crawling hour from a flowing one, and it reports nothing at all for a vehicle that sat idling the whole afternoon.
AVL 12 is the tracker’s own running total of fuel consumed, built up continuously from how the vehicle actually moved: every acceleration, every crawl, every minute of idling. Paired with AVL 13, the live burn rate, it separates a hard-driven hour from an easy one on the same route.
It is still a model, and we say so. Rather than claim a fuel figure is exact, every trip carries a confidence score. Three hours crawling through Lagos gridlock registers almost no distance while the engine keeps burning, so FuelSense reads that state from the tracker, estimates the idle burn, and lowers the score with the reason attached. Receipts you log calibrate the model further. Managing expectations honestly is what makes the outliers worth acting on.
The three lines that matter
Fuel burned between two pings
ΔAVL12 × k ÷ 1000
(7514 − 7461) × 2.396 ÷ 1000=0.127 L
The tracker reports millilitres burned. k corrects it.
The correction, k
rate̅ AVL13 ÷ rate̅ AVL12
2.221 ÷ 0.927=2.396
The device’s own two fuel elements, measured against each other while idling. Receipts override this once they exist.
Unaccounted fuel at a fill
added − (capacity − level)
45 − (60 − 30)=15 L
No tank accepts more than its empty space. The excess is what the model wrongly believed was aboard.
Figures from one day on the live RAV4. Nothing is hidden behind a “proprietary algorithm”, because a number you cannot check is a number you cannot act on. See all seven, with worked numbers
What you are actually buying
One tracker, wired to the battery, watching fuel, distance and power. Drag the vehicle to look around — the markers are the same ones your fleet manager taps in the dashboard.
0 km/h
Tap the dot for the battery reading
50,829
miles, anchored to the dash
19.1 L
32% of tank · modelled
12.2 V
read every fix
3.8 V
survives power cuts
15 s
while the engine runs
±5 m
GNSS with DOP filtering
The hardware
A Teltonika FMC150 wired behind the dash. It reads GPS, ignition and its own fuel counter, then streams them over the mobile network.
A trip opens when the ignition turns and closes after 30 minutes at rest. Distance is odometer-validated, with GPS jitter and impossible hops rejected.
Any halt over three minutes becomes a stop with a real address, so a route reads as a sequence of places rather than coordinates.
Engine on and stationary is tracked to the minute and priced. It is the most common invisible cost in a fleet, and the easiest to fix.
Low fuel, tracker unplugged, movement without ignition. Each is a flag for investigation with the evidence attached, never a verdict.
There is no sensor in your tank, so FuelSense never claims to have watched fuel leave it. What it can do is measure the burn from the vehicle’s own movement and set it beside the receipts your drivers upload. Where the two disagree, you have a specific number and a specific day to ask about.
Measured by the tracker
GNSS distance and burn, accumulated ping by ping
Declared by the driver
Driver uploads from their phone, OCR reads the slip
The difference
A question to ask, not a verdict to deliver
A photo of the pump slip at the forecourt. OCR reads the merchant, litres and amount, so nobody types figures into a spreadsheet a week later.
A logged purchase is matched against the refuel the tracker saw at that time, then credited to the vehicle’s virtual tank.
Receipts set the real naira-per-litre for the day they cover, and every cost figure for that period is valued at it.
Each verified fill-up sharpens the vehicle’s consumption model, so the estimate stops being a class average and becomes this vehicle.
Every figure shows its working. These are the panels you land on.
Operational snapshot
Spend, with the distance that earned it
Fuel spend · 7d
₦48,300
286 km · ₦169/km
Money saved
₦6,420
vs benchmark
Idling
3h 40m
7.9 L burned
Economy
7.4 km/L
vs 7.0 benchmark
286 km at the 7.0 km/L benchmark = 40.9 L, which at ₦1,330/L is ₦54,720. Actual spend was ₦48,300, a saving of ₦6,420.
Vehicle data
Every signal the tracker sends, named and explained in plain words
Efficiency and driving behaviour
Per vehicle and per driver, against a realistic baseline
Also inside: trip history with exact date ranges, fuel-level charts with idling shaded, event replay, driver receipt uploads read by OCR, and email alerts you choose.
Start with one vehicle. We supply and configure the Teltonika hardware, or work with trackers you already run.