Head to head

Mileage and road, done properly. The axles are a different question.

PC*Miler is the distance a large part of the freight industry agrees to be paid on, and CoPilot puts truck-legal guidance in the cab. Neither has ever been shown the pallets.

Trimble MAPS
12 comparison criteria
Public documentation, August 2026

Who it is for

North American carriers and brokers, in the office and in the cab.

Few products are as woven into the day-to-day arithmetic of freight as this one, and that position was earned.

When a broker and a carrier agree a rate on a mileage figure, that figure very often came from PC*Miler. Being the number two parties agree to be bound by is a far harder position to earn than being the most accurate, and it has real commercial weight. A mileage dispute that both sides can settle by looking at the same source is a dispute that does not happen.

Alongside it, CoPilot puts truck-legal turn-by-turn navigation in the cab with the vehicle profile applied, and the toll and hazardous route data underneath is deep. For a fleet that wants the office and the cab to speak the same distance language, having both from one house removes an entire class of argument between dispatch and driver.

The road data itself is the product of years of maintenance. Bridge clearances, weight-restricted structures, municipal truck routes and turn restrictions across a continent do not stay correct on their own.

Miles, tolls and turns are all facts about the road. Legal or not legal is a fact about the freight.

What we are not claiming

We do not produce a mileage figure anyone rates on, we have no in-cab navigation, and we do not calculate tolls. Those rows are a plain no in our column below.

The job it was not built for

Its subject is distance and road, and it publishes that thoroughly.

Per-axle load distribution from cargo position is not part of that subject, and the vendor has never suggested it is.

The vehicle profile is an input

You describe the truck and the service returns a road that respects the description. Where the numbers in that description came from is your side of the line.

A route is one road for one load

A run with four drops is a single road. The load after drop two is a different load with different axle weights, and it can fail a rule the departing load passed easily.

Distance does not carry a verdict

Miles, tolls and turns are all facts about the road. Legal or not legal is a fact about the freight, and it needs a model of where that freight sits.

Twelve rows, and almost no overlap

One row in that table is a yes on both sides. The other eleven belong cleanly to one column or the other, which is unusual for a comparison page and is the reason this one is worth reading twice.

The 12 rows above, by which column owns them

rows

42%

50%

Mileage, navigation, tolls, traffic and hazmat routing5 rows
Truck-legal routing, where both say yes1 rows
Axles, statute and the correction6 rows

Counted from the table above. Nothing in the first group is a row we intend to contest, and nothing in the third is a row the vendor has ever claimed.

Side by side

Twelve comparison criteria, including six where we are the no.

Mileage of record, in-cab navigation, tolls, traffic and hazardous routing all belong on the other side of this table.

The whole routing category

AxleGuard compared with Trimble MAPS across twelve dated criteria
Capability	AxleGuard	Trimble MAPS
Truck-legal routing from vehicle dimensions	Yes	Yes
Mileage used as the figure of record for rating	No	Yes
Turn-by-turn truck navigation in the cab	No	Yes
Toll cost calculation along the route	No	Yes
Hazardous cargo road restrictions	part	Yes
Live traffic taken into account	No	Yes
Axle weights solved from where the freight sits	Yes	No
Bridge formula on every consecutive axle group	Yes	No
Tire and axle-rating limits layered on statute	Yes	No
Corrective move in slider holes and inches	Yes	No
Verdict recomputed per leg as freight comes off	Yes	No
Permit pathway when no legal position exists	Yes	n/p

supportedpart partly, or with limits not supportedn/p not published by the vendor

Methodology

Drawn from publicly published product documentation as of August 2026. Where the vendor has not published a capability the cell reads not published rather than no. Trimble MAPS is an active product family that ships changes continuously — verify with the vendor before relying on a row here.

When to pick them instead

Four situations where the answer is Trimble MAPS.

Your rates are agreed on a published mileage standard. That figure has to keep coming from the vendor your customers and carriers already accept, and nothing here changes that.
You need truck-legal turn-by-turn guidance in the cab with the vehicle profile applied. We do not do turn-by-turn.
Toll cost needs to be in the quote before the load is accepted. Toll data at that depth is a real product and it is not ours.
Your compliance problem is bridge strikes and restricted roads rather than axle weights. That is the routing category's problem to solve, and it solves it well.

Working together

Four steps, and nobody re-argues a rate.

01
The load is solved before a mile is quoted
Axle by axle, against the jurisdictions on the lane, with the binding rule named. A load that cannot be made legal never reaches the routing stage.
02
Mileage of record stays where it is
If your rates are agreed on a particular mileage standard, that standard keeps coming from the same place. We are not asking anyone to re-argue a rate.
03
The road is planned around the real equipment
Height, length, width and weight from the tractor and trailer on file rather than a generic profile, with anything relaxed surfaced before the route is shown.
04
The cab keeps its navigation
In-cab guidance, traffic and tolls carry on exactly as they do today. What changes is that the freight behind the driver has already been checked.

The category, the matrix and the neighbours.

Same lane, same mileage, different question.

Take a lane you already rate and route today. We will solve the axles on one of its loads and you can see whether the two answers ever disagree.

Bring one lane Open AxleGuard