Home / Metros
Coverage
Freight coverage by metro
The lane model prices 2,450 corridors from 50 origin cities in 26 states. This page indexes 20 metro pages — each prints the modeled lanes from that city, the hubs it connects, planning miles and the planning band derived from the directory. An origin hub is a place the model prices from — not an office, terminal or staffed location we claim to have.
Last reviewed 2026-11-17 - Portlandia Logistics dispatch
The twenty metros in this build
Every hub in the directory carries the same number of outbound cards, so the table follows the curated metro list rather than inventing a ranking. Counts are rendered from lib/lanes.js; they are not hand-typed.
| Metro | Region | Outbound modeled lanes | Metros connected | Inbound modeled lanes | Planning miles range |
|---|---|---|---|---|---|
| Louisville Kentucky |
South | 49 | 49 | 49 | 105-2,310 |
| Chicago Illinois |
Midwest | 49 | 49 | 49 | 95-2,160 |
| Atlanta Georgia |
South | 49 | 49 | 49 | 250-2,550 |
| Dallas Texas |
South | 49 | 49 | 49 | 215-1,965 |
| Houston Texas |
South | 49 | 49 | 49 | 170-2,210 |
| Los Angeles California |
Pacific | 49 | 49 | 49 | 25-2,850 |
| Phoenix Arizona |
West | 49 | 49 | 49 | 125-2,495 |
| Denver Colorado |
West | 49 | 49 | 49 | 390-2,020 |
| Seattle Washington |
Pacific | 49 | 49 | 49 | 30-3,195 |
| Portland Oregon |
Pacific | 49 | 49 | 49 | 140-3,165 |
| Memphis Tennessee |
South | 49 | 49 | 49 | 230-2,180 |
| Nashville Tennessee |
South | 49 | 49 | 49 | 180-2,305 |
| Columbus Ohio |
Midwest | 49 | 49 | 49 | 115-2,460 |
| Indianapolis Indiana |
Midwest | 49 | 49 | 49 | 115-2,265 |
| Kansas City Missouri |
Midwest | 49 | 49 | 49 | 255-1,760 |
| St. Louis Missouri |
Midwest | 49 | 49 | 49 | 270-2,030 |
| Charlotte North Carolina |
South | 49 | 49 | 49 | 150-2,680 |
| Savannah Georgia |
South | 49 | 49 | 49 | 145-2,810 |
| Newark New Jersey |
Northeast | 49 | 49 | 49 | 190-2,980 |
| Miami Florida |
South | 49 | 49 | 49 | 240-3,195 |
An outbound lane page is a corridor the model prices from the metro; inbound cards run the other way from another modeled hub. A model card is not a booking, a capacity commitment or a transit promise.
What this index does not claim
- No offices, terminals or equipment. The metro names are model points. We do not own tractors, trailers, chassis, warehouses, cross-docks or terminals, and we hold no port or rail facility rights.
- No authority claim. Pre-launch: no broker authority is claimed and no tenders are accepted yet. Nothing on this site is an offer to arrange freight.
- No coverage percentage. The counts are model card counts, not a share of any market and not a promise of capacity on a lane.
- No transit promise. Planning miles and planning bands are model output; the firm window and rate are on a rate confirmation naming the carrier.
Why these twenty metros
The lane directory is a full mesh: every origin hub prices a card to each of the other 49 hubs, so every hub carries the same outbound count. The twenty pages here are the curated metro set named for this build. A metro without a page is still priced by the instant estimate: any lower-48 ZIP pair returns the same planning range, mileage and band.
Talk to dispatch
Mon–Fri 8:00am–6:00pm ET
After hours, email the lane and the pickup window; the on-call dispatcher replies for loads already in transit, and new quotes are answered the next business day.
(502) 385-3399 Email the deskAuthority status
Pre-launch: no broker authority is claimed and no tenders are accepted yet. Nothing on this site is an offer to arrange freight.
How the model derives these pages
Outbound cards, connected metros and inbound cards come from the hub record; miles are the model's 1.17 road factor and the band adds one day for an LTL break. Add a lane to lib/lane-index.json and every affected metro page updates on the next render.
Start with the lane
Two ZIPs, a weight and a class return the planning range, the mileage and the transit band for the metro you are shipping out of or into.