For truck fleets, fuel is often the biggest cost after salaries, and fuel theft is a real problem: siphoning at night, fake refuel bills, or a "quick stop" that empties half a tank. Traccar can watch fuel levels and alert you when fuel disappears.
Step 1: get fuel data into Traccar
GPS alone can't measure fuel. You need one of these:
| Source | How it works | Accuracy |
|---|---|---|
| Fuel level sensor in the tank | Capacitive or ultrasonic sensor connected to the tracker (analog input or RS232/RS485) | Best, a few percent |
| CAN bus data | Tracker reads the vehicle's own fuel level from the CAN bus (common on newer trucks) | Good, depends on the vehicle |
| Vehicle float sensor | Tracker reads the dashboard fuel gauge signal | Rough, not good enough for theft detection |
For theft detection, a proper fuel level sensor is worth it.
Your tracker must support the sensor. Teltonika, Ruptela, Queclink and many other trackers do. Check yours on our supported GPS devices list and in its manual.
Step 2: see the raw value
Once connected, the tracker sends the sensor value with each position. Open the device in Traccar and look at the position attributes. Depending on the tracker, you'll see:
- A ready fuel attribute (often from CAN), or
- A raw value like adc1, io followed by a number, or a sensor-specific attribute
Write down the value with the tank empty, quarter, half and full.
Step 3: convert to litres with a computed attribute
Traccar's computed attributes turn raw values into useful ones. Create one:
- Attribute: Fuel level (
fuel) - Expression: a formula that maps your raw value to litres
For a sensor that's linear, it might be as simple as:
adc1 * 0.25
For tanks that aren't a simple box (most truck tanks), use a calibration table from the sensor installer and a formula with steps. Link the computed attribute to the device or its group.
Step 4: turn on fuel drop and refuel events
Traccar creates fuel drop and fuel increase events when the fuel level changes by more than a threshold between positions. Set these attributes on the device or group:
- fuelDropThreshold: for example 10 (litres, or whatever unit your fuel attribute uses)
- fuelIncreaseThreshold: for example 20, to log refuels
Then create notifications for Fuel drop (and Fuel increase if you want refuel records), sent to the web interface, mobile app, email or SMS.
Avoiding false alarms
Fuel moves in the tank. Braking, hills and corners make the level jump. To avoid alerts every time a truck brakes:
- Use a sensor with built-in filtering (averaging), and set it during installation
- Set the threshold high enough for your tank size, for example 5 to 10% of the tank
- Treat drops while stopped with ignition off as the most suspicious: that's when siphoning happens
- Compare the fuel level before and after each stop, not position by position
That last point is where custom logic or AI helps most.
Reports that catch theft
Useful reports for fleet owners:
- Refuels: date, place and litres added, to compare with fuel bills
- Drops: date, place and litres lost, with the vehicle's state (moving, stopped, ignition)
- Consumption: litres per 100 km per vehicle, to spot vehicles that use more than they should
A truck that suddenly uses 20% more fuel per 100 km than last month, with no route change, deserves a look.
Where AI helps
Rules catch obvious theft. AI catches the clever kind:
- Learns each vehicle's normal consumption on each route
- Flags slow siphoning spread over several stops
- Separates real drops from sensor noise, so alerts are fewer and more trustworthy
Summary
- Install a proper fuel level sensor or use CAN fuel data.
- Convert the raw value to litres with a computed attribute.
- Set fuelDropThreshold and notifications for fuel drops.
- Focus on drops while stopped, and compare consumption over time.
Want fuel monitoring and theft alerts in your platform? See AI features for fleet tracking or ask about custom Traccar development.
