Skip to content
AxleGuard
Demo

Roundup

Six ways to plan a road a truck can actually take

These products are frequently compared as though they were interchangeable, and they are not. One of them is a mileage reference, one is a fleet management business, and the rest are mapping suppliers with different geographic strengths. This is what each is for.

  • Six products
  • Published documentation only
  • Assessed August 2026

Method

How we assessed them

A roundup is only useful if you know what it did and did not look at, so here is exactly that.

Everything below comes from documentation each company publishes openly, read as of August 2026. Nothing here is based on a private briefing, a sales conversation or a benchmark we ran, because we could not run a fair one across six products with six different commercial arrangements.

Where a capability is documented, the comparison marks it supported. Where the documentation describes something narrower than the row asks for, it is marked partial. Where we could not find the answer published, it is marked not published rather than absent — the vendor may well do it, and we are not going to assert an absence we cannot demonstrate. Where a product genuinely does not do something and does not claim to, it is marked not supported, and that is not a criticism.

The routing vendors do not claim to solve per-axle weight from cargo placement, evaluate every consecutive bridge subset, or commission a physical axle signal. That is an honest category boundary, not a flaw. Those products are routing tools rather than load-planning or hardware- commissioning systems. The rows are in the table because buyers regularly assume that a truck-legal route implies a legal load, and it does not.

What we did not assess

Price, contract terms, support quality, service availability and map freshness are all material to a purchase and none of them are things we can compare honestly from public documentation. We have not invented scores for them. Ask each vendor directly, and ask for the answer in writing.

Where we could not find an answer published, the comparison says not published rather than absent. We are not going to assert an absence we cannot demonstrate.

The six

What each one is for, and where it stops

In no particular order, because they are not competing for the same job.

01 · Location data and routing services

HERE

What it is genuinely good at

HERE is a location data company, and the routing services it publishes carry commercial-vehicle attributes properly: height, width, length, weight, axle count and hazardous goods classes, evaluated against restriction data on the road network. Alongside routing it publishes geocoding, distance matrices, reachable-area calculations and traffic, and it licenses map data for use inside other companies' navigation products. Coverage is genuinely global, which matters if your lanes are not confined to one continent.

Where it stops

It is a location services business, and the boundary of what it does is the road. The freight in the trailer, where each item sits and what that does to the axle groups are outside its scope, and it does not publish an axle-weight solver or a bridge formula check. It will tell you a road your combination fits on. It has no way of knowing whether you will pass the scale sitting on it.

02 · Logistics optimisation, strongest in Europe

PTV Group

What it is genuinely good at

PTV approaches routing through transport optimisation rather than mapping. Its developer services cover truck attributes, toll costs and vehicle restrictions. The wider family also plans tours and fleet routes, including which vehicle serves each stop and in what order. European road, restriction and toll modelling is a long-standing strength.

Where it stops

The same boundary applies: it optimises journeys, not load distribution. The product family is not built around axle weights, the Federal Bridge Formula or US state weight tables. North American users should read the coverage documents rather than assume they match the European data.

03 · The North American mileage reference

Trimble MAPS

What it is genuinely good at

Trimble MAPS holds a distinct position here. Its mileage is a common reference for freight rating and settlement in North America, so its reported miles are often the paid miles. It also offers commercial-vehicle routing, restrictions, tolls, hours-aware trip planning and in-cab navigation. That reduces friction for carriers reconciling planned and billed miles.

Where it stops

Its subject is the road and mileage, not the trailer. It does not publish a per-axle solver based on freight position. A route that is legal for the declared gross weight still says nothing about weight distribution across axle groups.

04 · Mapping inside a cloud you may already run on

Azure Maps

What it is genuinely good at

Azure Maps offers truck routing with vehicle dimensions, weight and load type. It also includes geocoding, traffic, matrices and weather inside Microsoft's cloud. Its strongest argument is organisational: if your systems, identity and billing already live there, adding mapping is easier than adding a new supplier. The commercial and security review may already be done.

Where it stops

It is a general-purpose mapping service that supports commercial vehicles, not a freight product. There is no first-party in-cab navigation offering for drivers, no fleet telematics, and nothing that models the load itself. Toll cost modelling is not something we found published in a form comparable to the freight-focused suppliers, so the comparison below marks it as not published rather than assuming either way.

05 · Maps and navigation, with truck profiles

TomTom

What it is genuinely good at

TomTom publishes map data, routing and navigation with commercial vehicle profiles, so a route can be planned around a truck's dimensions and weight and then driven with turn-by-turn guidance built on the same data. The navigation heritage shows: the products are oriented towards what a driver sees and follows, rather than only towards a planning answer computed in an office.

Where it stops

As with the other mapping suppliers, the load is not modelled. Nothing in the product line solves axle weights from cargo placement or evaluates consecutive axle subsets, and its telematics business is no longer part of the same company, so fleet tracking is a separate purchase.

06 · Fleet management first, routing second

Verizon Connect

What it is genuinely good at

Verizon Connect is a fleet management business rather than a routing supplier. Its centre of gravity is vehicle tracking, driver behaviour, maintenance and logging-device compliance, with truck-aware navigation provided to drivers as part of that. If the problem you are solving is knowing where the fleet is and keeping the hours-of-service records straight, this is a different category of product from the five above and a reasonable answer to a different question.

Where it stops

It is not something you build a planning system on top of, and it does not publish routing as a service for other systems to call in the way HERE, PTV, Trimble MAPS, Azure Maps and TomTom do. Several of the capabilities in the comparison below are marked as not published for this reason rather than as absent — the product is documented for fleet managers, not for the people integrating it.

A truck-legal road is a necessary condition for a legal load. It is not a sufficient one.

Capabilities published as supported, by product

of 11 rows
  • HERE4 of 11 rows

    3 not published

  • PTV Group5 of 11 rows

    2 not published

  • Trimble MAPS7 of 11 rows

    2 not published

  • Azure Maps3 of 11 rows

    1 not published

  • TomTom5 of 11 rows

    2 not published

  • Verizon Connect4 of 11 rows

    4 not published

Counted from the grid below. Every product here plans a road around a truck's dimensions and weight; the spread between the columns is about what else each one publishes alongside that.

Every cell in the grid, by what the documentation said

cells
42%
36%
21%
  • Published as supported28 cells
  • Not supported, and not claimed24 cells
  • Not published14 cells

All 66 cells of the grid below. 14 of them are marked not published, which is a fact about the documentation rather than a claim about any product.

Side by side

The capability grid

Read the not-published marks as missing information rather than missing capability. They mean we could not find it documented, which is a fact about the documentation.

Published capabilities of six commercial vehicle routing and fleet products, assessed from public documentation in August 2026.
CapabilityHEREPTV GroupTrimble MAPSAzure MapsTomTomVerizon Connect
Routes planned around vehicle dimensions and weightheight, width, length and gross weight as routing inputsYesYesYesYesYesYes
Hazardous materials route restrictionsYesYesYesYesYesn/p
Toll cost estimationYesYesYesn/pYesn/p
Distance matrices and reachable-area calculationsYesYesn/pYesYesn/p
First-party in-cab navigation for driversn/pYesYesNoYesYes
Fleet telematics as part of the same productn/pn/pYesNon/pYes
Mileage used as a reference for freight rating in North AmericaNoNoYesNoNoNo
Driving-hours constraints in the trip plann/pn/pYesNon/pYes
Per-axle weight solved from cargo placementnone of these are load planning products, and none claim to beNoNoNoNoNoNo
Bridge formula evaluated on every consecutive axle subsetNoNoNoNoNoNo
Physical axle signal after truck commissioningNoNon/pNoNon/p
supportedpart partly, or with limits not supportedn/p not published by the vendor

The verdict

Which one to pick when

Six answers to six different questions. If more than one of these describes you, the honest answer is that you need two of them.

  1. 01

    If your miles have to match what you bill, start with Trimble MAPS

    When planned miles and settled miles have to reconcile, the mileage reference in use across North American freight rating is worth more than any individual routing feature. Choosing something else means explaining a mileage difference to a customer every time it comes up, which is a recurring cost with no upside.

  2. 02

    If your lanes are European, look hard at PTV Group first

    European road restrictions, toll structures and cross-border rules are where PTV has the deepest history, and its optimisation heritage means it is thinking about which vehicle does which drops rather than only about one vehicle's road.

  3. 03

    If you need one supplier across several continents, HERE is the straightforward answer

    Global coverage with commercial-vehicle attributes carried consistently, plus the surrounding services — geocoding, matrices, reachable areas — that a planning system ends up needing anyway. It is the least surprising choice for a multi-region operation.

  4. 04

    If your organisation already runs on Microsoft's cloud, Azure Maps saves you a procurement

    The technical case is ordinary and the organisational case is strong: identity, billing, data residency and the security review are already settled. For a team whose bottleneck is approval rather than capability, that is worth more than a feature comparison suggests.

  5. 05

    If the driver's experience is the point, TomTom's navigation heritage shows

    When what matters is what the person in the cab sees and follows, a supplier whose products grew out of navigation rather than out of data licensing tends to get the details right. Note that fleet tracking is a separate purchase.

  6. 06

    If the real question is where the fleet is, Verizon Connect is a different category

    Tracking, driver behaviour, maintenance and logging-device compliance, with truck-aware navigation included. It is not a routing service you build a planning system on, and it is a reasonable answer if the problem is fleet visibility rather than route computation.

  7. 07

    If the question is whether the load will pass the scale, none of them

    That is not a criticism of these products. Load legality is a different problem. It depends on freight position, equipment geometry, every bridge-formula axle subset, and tire and axle ratings. A truck-legal road is necessary, but it is not enough.

Dated, and honest about it

Assessed from publicly published documentation as of August 2026. Products in this category change quickly, and a capability marked as not published here may be published tomorrow. Where a row matters to your decision, ask the vendor directly and get the answer in writing rather than relying on a comparison somebody else wrote.

Next step

Put the truck-routing comparison against one real load.

Bring the route, configuration or scale ticket that made the truck-routing comparison matter. We will work through it in plain English and show where AxleGuard changes the decision.