Truck Fuel Consumption in Kenya: How to Calculate km/L and Build a Reliable Baseline

Ask five operators what a truck should do per litre and you will get five confident answers. Most will be borrowed from a different vehicle, a lighter load, an easier route, or a week when somebody forgot to record a fill. The arithmetic is simple. The difficult part is making sure the kilometres and litres describe the same work.

A useful fuel figure is not a promise from a brochure and it is not one good trip. It is a baseline learned from the vehicle itself: enough clean distance and complete fuel records to show what normal looks like before an unusual result is treated as a problem.

The two fuel-consumption formulas

Kenyan fleet teams usually speak in kilometres per litre. Reports may use litres per 100 kilometres instead. Both describe the same result from opposite directions.

To convert either way, divide 100 by the figure. A result of 2.0 km/L is 50 L/100 km. A result of 40 L/100 km is 2.5 km/L. Keep one unit on the vehicle record and in every report; switching formats halfway through a review creates mistakes that look like operational variance.

Run a clean full-to-full measurement

The most practical manual method is to return the tank to a consistent level after a known distance. The litres required to restore that level approximate what the truck consumed. It only works when every litre in between is counted.

• Use one vehicle, one odometer source, and one unit throughout the test
• Start and finish at a consistent tank level, ideally at the same pump and on level ground
• Record every litre added between the two readings, including top-ups away from the usual station
• Measure a meaningful working distance rather than a short depot run
• Note payload, route, idling, trailer use, and any maintenance issue that changed the duty

A fuel gauge is useful for direction, not precise accounting. Tank shape is irregular, fuel moves on gradients and rough roads, and the top half of a gauge does not always represent the same litres as the bottom half. If your tracker reads tank level, use settled readings and trends rather than treating every percentage movement as a fill or a loss.

Build a baseline for each vehicle, not one number for the fleet

Two trucks with the same badge can still do different work. One pulls a trailer on the Northern Corridor; another runs local drops in Nairobi traffic. One returns empty; the other carries dense cargo in both directions. Averaging them produces a neat number that describes neither truck.

Start with several clean fills and enough working distance to dilute the noise of one top-up, one hill, or one queue. Keep learning as the vehicle works. Compare a new trip with that vehicle's own established range and, where possible, with trips of similar route, payload, trailer, and traffic conditions.

Cost per kilometre then becomes useful. Divide the diesel price per litre by km/L. If the price changes, cost per kilometre changes even when the truck's physical economy does not, which is why litres and money should stay as separate measures in an operating review.

When the number looks wrong, audit the record before the driver

An impossible result is often a broken measurement window. Before treating variance as waste or theft, make sure the inputs belong together.

• A missed fill, duplicate receipt, or fill assigned to the wrong registration
• A typed odometer with a missing digit, a unit mismatch, or a tracker counter that restarted
• A partial fill compared with a previous full-tank reading
• Fuel transferred to a second tank, generator, refrigeration unit, or another vehicle
• A replaced tank or an incorrect tank-capacity figure on the vehicle record
• Two records captured on different dates even though the vehicle worked between them

Once the record survives that check, look for a change in the work or the vehicle.

• A heavier load, empty return, trailer, steep route, rough road, or long congestion window
• Extended idling, power take-off work, refrigeration, or other engine-driven auxiliary load
• Low tyre pressure, brake drag, poor alignment, clogged filters, or an overdue service
• Harsh acceleration, speeding, high engine revs, or repeated route deviation
• A level drop while parked, litres that exceed physical tank capacity, or repeated rapid refills

None of those signals is a verdict by itself. A 20% change on one short trip is a reason to look. The same change across repeated comparable trips, supported by location, engine-hours, maintenance, and tank-level evidence, is a reason to act.

Turn the baseline into an operating control

A spreadsheet can calculate km/L. The operating value comes from connecting that result to the trip that created it. Dispatch knows the route and load. Telematics knows the distance, movement, and engine time. The fuel record knows the litres. Maintenance knows whether tyre pressure, brakes, filters, or a repair changed the vehicle.

Keep those records on one timeline and the review question changes from “Why did we spend so much on diesel?” at month-end to “What changed on this vehicle on this trip?” while the evidence still exists. For the hardware side of that record, read the guide to fuel monitoring systems in Kenya. For the investigation workflow, see how fleets can make unexplained diesel loss visible.

Frequently asked questions