Fleet, telematics & modem makers

Which carrier should your vehicles use in each region, and where do routes go thin?

Compare measured carrier signal across the regions your fleet drives, check coverage along routes on an H3 grid, and pull raw readings when you need to model it yourself.

14 days free · no card · Coverage API key in a minute · US organizations

MeasuredFrom real phones, not a propagation model
Per bandCarrier, band and generation on every row
H3-nativeResolutions 3 to 10, JSON or GeoJSON
LTE + 5G NRRSRP, RSRQ and SINR with reading counts
Use cases

How fleet and telematics teams use the Coverage API

Carrier selection per region

Pull coverage hexes for each operating region and compare measured signal by carrier and band to pick a primary and a fallback network.

GET /coverage · H3 JSON or GeoJSON extract

Coverage along routes

Convert route polylines to H3 cells and check them in batches to find stretches with weak signal or insufficient evidence.

GET /coverage/h3 · one unit per H3 cell

Paired carrier comparison

The network benchmark compares carriers only over cells measured for both, so the comparison is like for like. It compares RF evidence, not speed.

GET /network-benchmark · paired-cell comparison

Raw readings for your own models

On paid plans, page through de-identified individual readings with exact time and position for the corridors you care about.

GET /measurements · paid plans only

See the data

What a measured market looks like

This is the live San Francisco sample of the LTE Discovery Coverage Intelligence API: every hexagon is an H3 cell where phones recorded LTE or 5G NR signal, coloured by the strongest P90 RSRP any carrier reached there. Your evaluation key returns the same kind of evidence, broken out per carrier and band.

  • Density varies. Busy areas have deep evidence; quiet areas can be thin. Every row carries its reading count.
  • No data is not no coverage. Places without enough readings come back as insufficient evidence.
  • Cell identity, not site locations. The API never publishes where towers are.
  • No rankings. We report measured signal per carrier and band and leave the conclusions to you.
  • US only. Data and plans cover the United States and US-based organizations.
Live sample · San Francisco · H3 res 8Open the interactive sample

Loading measured hexagons…

Best P90 RSRP-120 dBm-105 dBm-95 dBm-85 dBm-75 dBmBlank areas mean no published readings, not no coverage.

Plans for fleet and telematics teams

Fleets in a handful of metros fit Region or Scale. Corridor and nationwide programs fit Enterprise. Self-service plans start at $249/month with transparent unit pricing.

FAQ

Questions from fleet and telematics teams

Can I check coverage along a route?

Yes. Convert the route to H3 cells and query them with coverage/h3, up to 100 cells per request, or pull a coverage extract for the bounding area.

Are raw measurements included?

Raw measurements are available on paid plans (Market, Region, Scale and Enterprise), not during the free evaluation. They are de-identified but keep exact time and position.

Does it rank carriers?

No. It reports measured signal per carrier and band. The benchmark compares carriers over the same measured cells so you can draw your own conclusions for your regions.

More answers on the Coverage API overview, or explore other solutions:

Contact

Talk to us about fleet and telematics coverage data

Nationwide or state scope, embedded or customer-facing use, invoicing and procurement: tell us what you need and we will scope it with you.

Prefer email? support@ltediscovery.app

Ready to try it yourself? Start the free 14-day evaluation.