Map Notes

Developed by Anthony Fiti (Twitter).

In the newest version of the map (version 5), the data is sourced from the FCC’s weekly transaction files. Previous versions sourced the data from the FCC License View and the FCC’s Spectrum Dashboard. As time moves forward, this data might not be 100% complete or accurate. I make no claim as to the accuracy of this data. If you have a problem with it, double check it with the FCC’s ULS database, then take it up with them.

Data is refreshed from the FCC on a weekly basis, typically Monday afternoons.

All names and colors are trademarked/copyright of their respective owners, I take no claim of ownership.

Known Map Issues

  • The map does not include Hawaii, Alaska, PR, American Samoa, etc. I left them off because I’m focused on the lower 48. Generally speaking, outside of the lower 48, spectrum isn’t in that desperate of a need because there isn’t sufficient population density to worry about it.
  • In some cases, a license can be divided in terms of both frequency (subdividing a 10MHz chunk of spectrum into two 5MHz pieces for the entire area) or in terms of geography, or both. For example, AWS-1 block E (1740-1745, 2140-2145) Western Region is owned by AT&T, however they let MetroPCS use this spectrum in Santa Barbara County, CA – this is geographical division. My mapping system doesn’t support visualizing the geographic divisions within a license area, so it just looks like they both own that slice of spectrum. Google Maps doesn’t support populating this data at the county level (too many polygons for the browser to handle).