Revenue per Truck per Week and Fleet Utilization

Monday's fleet report says revenue per truck rose 12% last week, and the operations meeting spends ten minutes congratulating the planners. By Wednesday someone notices that a brokered load was booked against an idle tractor's unit number, a two-day run that delivered on Monday was counted entirely in the prior week, and the Indian business unit pulled invoice totals with GST included. The fleet did not get busier. The arithmetic did.

Revenue per truck per week is a simple ratio, but only when the numerator, the denominator and the week boundary are written down and enforced by the transport management system. Fixing those three rules gives a figure that moves only when trucks earn more, and a decomposition into miles, loaded share and rate that tells the fleet manager which lever changed.

• What this page defines: which revenue lines count, which trucks sit in the denominator, how to split a load that runs across the weekly cut-off, and how empty legs pull the figure down.
• What it works through: a five-truck week in US dollars and the same structure for an Indian fleet in rupees, a formula block you can paste into a query, and a checklist before the number goes to management.

What revenue per truck per week measures, and what it leaves out

Revenue per truck per week answers one question: how much freight income each power unit produced in a seven-day period. It says nothing about profit, so read it beside cost per mile, never instead of it. A fleet can raise the figure by chasing long, cheap lanes while margin falls.

Three ratios usually hide under the same label. Revenue per owned truck divides by every unit on the asset register, so idle and unseated trucks drag it down; owners and lenders care about that view. Revenue per available truck removes days in the workshop. Revenue per seated truck also removes days without a driver, which isolates how well dispatch used the trucks that could actually run.

Keep the cost side in its own report. Our guide to trucking cost per mile builds the per-mile cost from fuel, pay, tyres and fixed charges; revenue per truck per week is the matching income measure. Put the two together and you get weekly contribution per truck, which is the number that should drive decisions about adding or parking equipment.

Building the numerator: linehaul, fuel surcharge and accessorial lines

Count every charge the customer pays for work the fleet's own trucks performed, net of tax collected for the government and net of pass-through costs. That rule keeps linehaul, fuel surcharge and earned accessorials in, and keeps brokered loads, sales tax and reimbursed tolls out.

• Linehaul: the base rate per mile, per kilometre, per load or per tonne. Always in.
• Fuel surcharge or diesel escalation: include it. The surcharge exists to pay for fuel the truck burned, and leaving it out makes a fleet look less productive whenever diesel prices rise. Report it as a separate column so rate changes stay visible.
• Earned accessorials: detention, layover, stop-off, loading and unloading charges, and truck-ordered-not-used fees. A TONU fee is revenue with no miles; our page on TONU, layover and redelivery fees covers when those charges are billable.
• Pass-through items: lumper receipts, permits or tolls rebilled at cost. Exclude them, or the figure rises every time a customer's dock charges more for unloading.
• Brokered or subcontracted loads: exclude them entirely. They used someone else's truck, so booking them to one of yours inflates that unit and hides the shortage of capacity that made you broker the load.

In India, tax collected on a goods transport agency invoice is not revenue. Ind AS 115 paragraph 47 defines the transaction price as excluding amounts collected on behalf of third parties, such as some sales taxes. Since 22 September 2025, a GTA charges either 5% without input credit or 18% with full credit, according to the GST Council's FAQ on its 56th meeting; under reverse charge the invoice carries no GST at all.

Revenue per truck per week for an Indian fleet should be computed from taxable value, not invoice total, because Ind AS 115 paragraph 47 excludes amounts collected for third parties; on a ₹6,35,500 week with ₹48,600 of 18% forward-charge GST, including the tax overstates the ratio by 7.65%.

The practical consequence is a data rule, not an accounting debate. Pull the taxable value field from the invoice line, never the grand total. A fleet that bills some customers under forward charge and others under reverse charge will otherwise show higher revenue per truck on the forward-charge lanes for no operational reason.

Choosing the denominator: active, seated or available trucks

Measure the denominator in truck-days, not in trucks, and divide by seven. A unit that joined the fleet on Thursday contributes four-sevenths of a truck-week, and a tractor in the shop for three days contributes four-sevenths to the available count.

Take the status from the maintenance work order and the driver assignment log, not from what the planner remembers. A truck is unavailable on a day when an open work order or an out-of-service inspection blocks dispatch for more than half the day. A truck is unseated when no driver is assigned for that day. Write both thresholds into the report specification so the numbers are reproducible.

• Team-driven trucks: count the truck once. Teams should produce more revenue per truck; report revenue per driver separately if you need to compare solos and teams.
• Slip-seat operations: several drivers share one unit across shifts. The truck is seated whenever any driver holds it.
• Spare units: a deliberate spare kept for breakdowns belongs in the owned count but can be flagged so that management sees its cost without blaming dispatch for it.
• Owner-operators: keep leased-on owner-operator trucks in a separate fleet line. Their revenue is shared under a settlement agreement, so mixing them with company trucks distorts both groups.

Splitting a load that crosses the Sunday midnight cut-off

Allocate each load to weeks by the share of its loaded miles run in each week. Pickup-date and delivery-date rules are easier to code but move large amounts of revenue across the boundary and make weekly figures swing for no operational reason.

Take load L-4471 on truck T105: picked up Saturday 7 November 2026 at 14:00, 1,100 loaded miles, delivered Monday 9 November at 10:00, for $2,750 including fuel surcharge. The ELD odometer shows 640 loaded miles completed by Sunday 23:59. Mileage allocation books $1,600 to ISO week 45 and $1,150 to week 46. A pickup-date rule would book all $2,750 to week 45; a delivery-date rule would book none of it.

The mileage rule needs a timestamped odometer reading at the cut-off for each load still in transit. Most ELDs and telematics units record that. Where a reading is missing, fall back to planned miles from the routing engine and flag the load, so the analyst can see how much of the week rests on estimates.

Keep the weekly KPI allocation separate from the general ledger. Finance may recognise revenue on a different basis at month-end, and the two should be reconciled, not forced to match. Over a full month, the sum of weekly allocations must equal the net revenue invoiced for completed loads plus the allocated share of loads still in transit.

Miles, loads and empty legs behind the weekly revenue figure

Every change in revenue per seated truck comes from one of three places: the truck ran more miles, a larger share of those miles was loaded, or each loaded mile earned more. Report the three factors every week, and the headline ratio explains itself.

Revenue per truck-week (RPTW)
  RPTW = R_w / TW

  R_w  = sum over loads i of (L_i + F_i + A_i) * (m_i,w / m_i)
         L_i  linehaul for load i, net of GST or sales tax
         F_i  fuel surcharge or diesel escalation for load i
         A_i  earned accessorials (detention, layover, TONU, stop-off)
         m_i  total loaded miles (or km) of load i
         m_i,w loaded miles of load i run inside week w
  TW   = sum over trucks t of d_t / 7
         d_t  days truck t was in the chosen class (owned, available or seated)

Decomposition (per seated truck-week)
  RPTW = M x lambda x r
         M      total miles run per seated truck-week (loaded + empty)
         lambda loaded miles / total miles
         r      revenue per loaded mile = R_w / loaded miles

Control check
  sum of R_w over the weeks in a month = net invoiced revenue
  for loads completed in that month + allocated share of loads in transit,
  tolerance 1 USD or 100 INR per truck

The loaded share, lambda, is where empty legs show up. A truck that runs 2,750 miles but only 2,035 loaded, as T105 did in the worked week below, has a loaded share of 74%. Raising it to 80% at the same total miles and the same rate per loaded mile would have added about $480 of revenue that week without one extra hour of driving.

Empty miles are not always a planning failure. A dedicated lane with no backhaul market runs empty one way by design, and the rate should already price that in. Our guide to deciding whether a backhaul is worth accepting covers the trade-off on a single return load; this page measures the weekly result across the fleet, which is where repeated bad or good backhaul decisions show up.

Weekly fleet revenue analysis in a transport management system should split revenue per seated truck-week into total miles, loaded share and revenue per loaded mile; in the illustrative US week, 2,464 miles at a 79.6% loaded share and $2.951 per loaded mile reproduce the $5,789 headline within $1.

A five-truck week worked in dollars and in rupees

The example uses ISO week 45 of 2026, Monday 2 November to Sunday 8 November. All figures are illustrative. The US fleet runs five tractors on dry van freight; T103 spent three days in the shop and T104 had no driver all week.

The same $20,675 produces three different headlines. Divided by five owned trucks it is $4,135. Divided by 4.571 available truck-weeks (T103 contributes four-sevenths) it is $4,523. Divided by 3.571 seated truck-weeks, removing T104 and T103's shop days, it is $5,789. The gap between $4,135 and $5,789 is the cost of one unseated tractor and one shop visit, and it belongs in the recruiting and maintenance discussion, not the dispatch one.

The Indian fleet below has the same structure: five 32-foot container trucks on contract lanes, figures in kilometres and rupees. Two customers are billed under 18% forward charge and the rest under reverse charge, so the invoice totals and the taxable values differ.

Had the Indian report used invoice totals, revenue per seated truck-week would have read ₹1,54,474, 7.65% higher, simply because two customers are on forward charge. Indian fleet owners often think in trips and revenue per truck per month. Converting both to the same weekly basis lets one dashboard cover both markets, provided the distance unit and currency are labelled on every column.

Driving-hour and e-way bill limits that cap weekly truck output

Total miles per truck-week has a legal ceiling in the US and a documentary trail in India. Know both, because a planner who sets a weekly mileage target above what a driver can lawfully run is setting up either a violation or a missed delivery.

Under 49 CFR 395.3, a property-carrying driver needs 10 consecutive hours off duty before driving, may drive 11 hours within a 14-hour window, and needs a 30-minute interruption after 8 hours of driving. Weekly on-duty time is capped at 60 hours in 7 days, or 70 hours in 8 days for a carrier operating every day, with a 34-hour restart available. Those limits apply to the driver, which is why a team-driven truck can run far more miles than a solo one.

• Set a practical ceiling: derive a weekly miles-per-seated-truck ceiling from your own ELD history for each operation type, rather than from a national average. In the worked week, a ceiling of 3,000 miles puts the US fleet at 82% of practical distance.
• Read the gap correctly: a truck far below its ceiling with a high loaded share was waiting, usually at docks; a truck near its ceiling with a low loaded share was running empty.
• Do not reward violations: exclude any truck-week with an hours-of-service violation from league tables of top-earning units, or the incentive points the wrong way.

India's GST e-way bill gives an independent record of which vehicle carried which consignment. Rule 138 of the CGST Rules requires the conveyance details in Part B, and Rule 138(10) sets validity at one day for up to 200 km plus one day for every further 200 km or part, with shorter steps for over-dimensional cargo. Matching Part B vehicle numbers to the dispatch record is a quick test that loaded kilometres were booked to the right truck.

Weekly loaded-kilometre reporting for an Indian goods carrier can be cross-checked against e-way bill Part B vehicle numbers under CGST Rule 138; any truck whose dispatched loaded legs exceed its matched e-way bills by more than 5% of kilometres should be reviewed before revenue per truck is published.

Who supplies each field and who signs the weekly fleet report

The weekly figure is assembled from five sources, and each needs a named owner. When the report is wrong, the owner table tells you who fixes the input rather than who argues about the output.

A placeholder unit number is the most common source of error in this list. Dispatchers sometimes attach a brokered or rescheduled load to whichever tractor is open on the screen. Require a real unit number with a matching ELD trip, or a brokered-load flag, before a load can be closed.

Rules the TMS should enforce and judgments left to the fleet manager

Most of this KPI should be computed by fixed rules with no human step, because any manual adjustment invites argument every Monday. Software can help a person on the few tasks that need judgment, such as reading a workshop note or explaining a sudden swing.

The decomposition makes the swing explanation almost mechanical. If revenue per seated truck fell 8% and loaded share fell from 80% to 72% while miles and rate held steady, the commentary writes itself: empty running rose. A text model can draft that sentence; a person should check it against what dispatch actually saw that week.

Checklist before publishing the weekly revenue per truck figure

Run these checks every Monday before the number leaves the analyst's desk. They take about twenty minutes once the queries exist and catch nearly every error described at the top of this page.

The trace below shows how one missed check produced the inflated figure in the opening example. Times are from the US fleet's own week 45 close, with illustrative record numbers.

1. Monday 07:10, report run: the scheduled TMS job publishes revenue per seated truck of $6,481 for week 45, up 12% on week 44.
2. Monday 09:40, review: the fleet analyst sees T104 credited with $2,470 although the ELD roster shows no driver logged on T104 all week.
3. Monday 10:15, root cause: load LD-77120 was brokered to an outside carrier, but dispatch closed it in transaction LOAD-CLOSE against unit T104 as a placeholder. The brokered-load flag was blank.
4. Monday 11:05, correction: billing re-codes LD-77120 as brokered revenue, T104 returns to $0, and the published figure is restated to $5,789.
5. Tuesday, control added: LOAD-CLOSE now rejects any load without a matched ELD trip on the assigned unit unless the brokered flag is set.

Monthly reconciliation of weekly truck revenue allocations against the billing ledger should agree within $1 or ₹100 per truck, with in-transit loads split by ELD odometer at the Sunday cut-off; a gap larger than 2% of monthly fleet revenue usually means brokered loads or tax were booked to company trucks.

For more fleet measures, browse the logistics and supply chain library. If you want the weekly calculation, the unit-to-ELD validation and the three-ratio report built into your dispatch and billing systems, send your fleet profile and data sources through our request for proposal form.