Broadcasting · RabbitEars.info

RabbitEars.info - US TV Station and Market Database

Datadory delivers rabbitears info us tv station and market database data covering every US DMA: 604 ranked market rows with populations, city-level Census counts inside each market, station records pairing viewer-facing display channels with physical RF channels, plus TSID records, ATSC 3.0 rollout dates and subchannel detail across roughly 210 DMAs - delivered daily, weekly, or hourly.

API, files, or your warehouse. Daily, weekly, or hourly.

Where it covers
United States end to end - roughly 210 designated market areas across 604 market-list rows, resolved downward to constituent cities and licensed stations, with Canadian broadcasters carried on a separate ISED-sourced list
How far back
A living reference corpus kept since 2008 and current to August 2026, with historic 1952 allotment records retained beside the present-day dial; longitudinal depth accrues across repeated deliveries at whatever cadence you set
How fine
Four nested levels - market, city, station/facility and subchannel - with transmitter coordinates carried to six decimal places, so signal-radius and coverage math starts from real points rather than market centroids

What is the RabbitEars.info US TV station and market database?

It is the American dial written down as rows. RabbitEars.info - US TV Station and Market Database is an independent, single-editor reference to US over-the-air television, operating since 2008 as part of the Worldwide TV-FM DX Association, and its core is deceptively simple: every US designated market area listed with the stations and subchannels licensed within it. The market list runs 604 rows across roughly 210 DMAs, each carrying its rank, market name and total population - New York first at 19,302,889, Los Angeles second at 17,206,901. Per-market city tables take resolution below the DMA border with Census counts for constituent cities; station records then pair the viewer-facing display channel with the physical RF channel, the community of license and transmitter coordinates.

Around that core sit specialist lists almost nobody else keeps in one place: TSID records with raw TSID and TSR date views, an ATSC 3.0 NextGen TV deployment list dated by RENDER milestone, largest stations by maxcontour, deleted stations, channel changes and expirations, VHF Nightmares, channel-sharing arrangements, cross-converted networks, MPEG-4 stations, SD 5.1 operations, datacasts, ancillary service filings and a Canadian roster. The reference also computes its own READS rankings from Longley-Rice coverage predictions and Census population rather than Nielsen figures, publishes a network grid of what reaches which market over the air, and runs location-based signal search plus a live bandscan network streaming from tuners scanning nationwide.

Inside the Datadory catalog - 1,744 datasets averaging 7.81 on the quality rubric - this record scores 8/10, carried by verified field documentation and four nested levels of resolution. Get a sample of this dataset and we return rows shaped exactly like the ones below, cut to your markets.

What do sample rows look like?

Three cuts of the New York story, exactly as they arrive:

# market list - 604 rows, every US DMA, ranked by population
rank : 1     market : New York City, New York       population : 19,302,889
rank : 2     market : Los Angeles, California       population : 17,206,901

# cities within a market - New York market excerpt
city        : Bridgeport, CT                        population : 144,229

# stations in the New York market - viewer channel vs transmitting channel
call_sign : WCBS-TV   community : NEW YORK, NY   display_ch : 2    rf_ch : 36
call_sign : WABC-TV   community : NEW YORK, NY   display_ch : 7    rf_ch : 7
call_sign : WPXN-TV   community : NEW YORK, NY   display_ch : 31   rf_ch : 34

# specialist lists ride alongside the core:
# tsids | atsc 3.0 render dates | deleted stations | channel shares |

Read the anatomy rather than the numbers. First, the hierarchy is real: market rows, city rows and station rows share keys, so a DMA rollup, a city-weighted view and a station lookup come from one schema instead of three reconciliations. Second, the display-versus-RF split is the reason this data exists - WCBS-TV dials as channel 2 and transmits on RF 36, WABC-TV happens to match at 7 and 7, and WPXN-TV sits at 31 displaying what transmits on RF 34. Third, the specialist lists travel with the core rather than behind it, which is what turns a static station table into a dial that can be watched over time.

What fields does the dataset include?

Eight verified fields carry every delivery, splitting into three jobs. The market frame: Rank, Market Name and Total Population - the DMA ladder every US television question ultimately climbs. Intra-market geography: City and Population, the Census counts that let a market argument get argued city by city. Station identity: Call sign, Display Channel and Digital Channel, with the display-versus-RF distinction kept explicitly rather than collapsed - the single most consequential column pair in post-repack broadcast work.

Beyond the spine, the reference's specialist lists hold real structure but uneven shapes, so they fold under additional fields on request: TSID and TSR date views, ATSC 3.0 RENDER dates, READS ranking values, maxcontour and channel-sharing references, deleted-station and expiration records, and the network-grid, signal-prediction and bandscan surfaces. Each gets mapped and populated when your sample is cut rather than promised blind here.

Where does coverage run, and at what grain?

  • Geography - the United States end to end: roughly 210 designated market areas across 604 market-list rows, resolved downward to constituent cities and licensed stations, with Canadian broadcasters carried on a separate ISED-sourced list. DMA borders are the geography US television still plans by.
  • Temporal - a living reference corpus kept since 2008 and current to August 2026, with historic 1952 allotment records retained beside today's dial. Longitudinal depth accrues across repeated deliveries at whatever cadence you set - the cadence conversation is yours, not a fixed schedule.
  • Granularity - four nested levels: market, city, station/facility and subchannel, with transmitter coordinates carried to six decimal places. Signal-radius and coverage math starts from real transmit points rather than market centroids.

The honest caveat: population figures are published estimates, suitable as weighting inputs rather than census-grade truths, and the strongest fit is 'what exists on the dial right now' rather than decades of history.

How is the data delivered?

API, files, or your warehouse. Daily, weekly, or hourly.

You pick the channel and the cadence; the field dictionary above travels unchanged through all three. Files suit overnight loads into BI and warehouse tables, structured responses suit availability dashboards and station lookups that need to breathe with the dial, and warehouse delivery puts the station table one join away from your own market or customer data. Rows arrive flattened - market, city and station layers joined on their keys, display and RF channels typed as integers, nothing left inside markup to strip. Cadence changes are a settings conversation, not a re-integration project, and a sample cut to your markets comes first either way.

Who uses this data, and for what?

  • NextGen TV transition tracking - follow ATSC 3.0 deployments station by station against their RENDER dates instead of press-release anecdotes.
  • DMA footprint and reach sizing - weight markets by published populations and resolve them to constituent cities for defensible reach math.
  • Antenna-decision and OTA availability tooling - pair display-versus-RF records with transmitter coordinates and signal predictions for cord-cutting calculators and installer quoting.
  • Tuner and guide-data provisioning - key equipment configuration on TSID records so receivers match virtual channels to their carriers correctly the first time.
  • Dial-change monitoring - watch channel changes, expirations, deletions and channel-sharing arrangements land as they happen.
  • Network availability mapping - read the grid of which networks reach which markets over the air as the base layer for distribution-gap analysis.

Which personas get the most value?

Developers and data-product builders land at relevance 3 - antenna apps, availability tools and station lookups are exactly the products this data powers, and typed rows with a documented display-versus-RF distinction save weeks of parsing. Competitive-intel product teams and market researchers and consultants sit at relevance 2: station churn and subchannel launches read as competitive signals, while DMA populations and city counts anchor territory and reach studies. Journalists, academics and students also ride at relevance 2, citing a named reference behind every market rank and deployment date. Data scientists, sales and growth teams and investors and quants hold relevance 1 - propagation features, territory grounding and broadcast-group diligence respectively.

Persona-by-persona workflows expand on the developers and builders, competitive intel and data science pages.

How does it compare to other broadcasting datasets?

It answers what is on the dial; the neighbors answer adjacent questions. The FCC TV Query System is the regulatory layer - roughly 30,000-plus authorised facility records with effective radiated power, antenna heights and licensee entities, organized by filing rather than by viewer experience. This dataset organizes the same dial by market and by what viewers actually tune, adds subchannel detail and the ATSC 3.0 timeline the registry does not frame. On the demand side, Barb's UK products measure what was watched, not what transmits; the Internet Archive TV News Archive holds what was said, at caption-searchable grain. The head-to-head with the measurement side is worked through in BARB Viewing Data Hub vs RabbitEars.info.

What should I know before requesting a sample?

Four things, all knowable upfront. First, populations are estimates - useful denominators for weighting and reach work, not census-grade counts, so treat derived per-capita measures as directional. Second, this is a curated reference, not a registry of record: breadth comes from one editor's discipline, and regulatory-authority questions belong to the FCC pair, where filings are the ground truth. Third, specialist lists vary in shape - TSID views, RENDER dates and bandscan reads each carry their own grain, so scope them explicitly at sample time and the delivered schema extends to match. Fourth, history has a boundary: deep coverage of the current dial plus 1952 allotments, with longitudinal series accruing from repeated deliveries - start the cadence before the quarter you need the trend.

Why request this through Datadory

Because a reference this good deserves better than being retyped by hand, one market at a time. Datadory resolves the whole thing into typed rows: the market-city-station-subchannel hierarchy joined on its keys, display and RF channels distinguished by construction rather than convention, TSIDs and deployment dates attached to the stations they belong to, and the specialist lists scoped to whatever your project actually touches. Start with a sample cut to your markets and stations, then browse the rest of the slice on the broadcasting data hub or the best broadcasting datasets ranking.

Field dictionary

Every field below is documented against real records. The full dictionary ships with the sample.

Field dictionary - the eight verified fields behind every market, city and station row
FieldTypeDefinitionExample
RankintegerMarket rank in the market list table, ordered by total population - the frame every DMA-level analysis keys on.1
Market NamestringDesignated market area name as the reference lists it, the geography US television planning still organizes itself around.New York City, New York
Total PopulationnumberEstimated population of the market - a weighting input for footprint and reach math, quoted as published.19,302,889
CitystringCity name from a market's constituent-city table, taking market resolution below DMA borders.Bridgeport, CT
PopulationnumberCensus population count for a city within a market, the finer-grained companion to the market-level figure.144,229
Call signstringStation call sign, the join key that carries a station across market, subchannel and specialist-list views.WCBS-TV
Display ChannelintegerVirtual channel number viewers tune and guides show - the number that survives repacks even when physics moves.2
Digital ChannelintegerPhysical RF channel the station actually transmits on, which diverged from display numbers en masse during the repack.36

RabbitEars.info - US TV Station and Market Database - product specification

AttributeValue
IndustryBroadcasting
Records604 market-list rows across roughly 210 DMAs, plus per-market city tables, station records and subchannel detail
Fields8 verified core fields; TSID, ATSC 3.0, READS, network-grid and bandscan structures folded under additional fields on request
Geographic coverageUnited States - every DMA, its cities and its licensed stations; Canadian broadcasters on a separate ISED-sourced list
Temporal coverageLiving reference kept since 2008, current to August 2026, with historic 1952 allotments retained
GranularityMarket, city, station/facility and subchannel levels, with transmitter coordinates to six decimal places
Delivery cadenceDaily, weekly, or hourly
SourceRabbitEars.info

What teams do with it

  • NextGen TV transition tracking Follow ATSC 3.0 deployments station by station against their RENDER dates instead of press-release anecdotes - who has actually flipped, market by market.
  • DMA footprint and reach sizing Weight markets by their published populations and resolve them to constituent cities, putting a defensible denominator under media-planning reach claims.
  • Antenna-decision and OTA availability tooling Pair display-versus-RF channel records with transmitter coordinates and signal predictions to power cord-cutting calculators and installer quoting.
  • Tuner and guide-data provisioning Key equipment configuration on TSID records so receivers match virtual channels to their carriers correctly the first time.
  • Dial-change monitoring Watch channel changes, expirations, deletions and channel-sharing arrangements as they land - the unglamorous churn that breaks stale station tables.
  • Network availability mapping Read the network grid to see which networks reach which markets over the air, the base layer for distribution-gap analysis.

Questions buyers ask

What does the rabbitears info us tv station and market database data contain?

Four nested layers of the US over-the-air dial: 604 ranked DMA markets with total populations, per-market city tables with Census population counts, station records pairing display channels with physical RF channels alongside community of license and transmitter coordinates, and subchannel detail - plus specialist lists for TSIDs, ATSC 3.0 deployments, deleted stations and channel-sharing arrangements.

How many markets and stations does it cover?

604 market-list rows spanning roughly 210 designated market areas, led by New York at 19,302,889 population and Los Angeles at 17,206,901. Large markets carry city tables hundreds of rows deep, and station-level views extend across the full dial, including Canadian broadcasters on a separate ISED-sourced list.

What is a TSID and why does it matter?

A transmission signal ID - the identifier that lets a receiver match the virtual channel a viewer selects to the physical carrier transmitting it. When TSIDs are wrong or missing, guides and remaps misbehave in ways that are miserable to debug, which is why provisioning and set-top work treats the TSID list as operational infrastructure rather than trivia.

Does it track the ATSC 3.0 NextGen TV transition?

Yes - a dedicated deployment list records NextGen TV stations with their RENDER dates, giving a station-by-station public timeline of who has actually lit up the new standard and when. Read it against the channel-share and channel-change lists and the transition's real texture - mergers of muxes, moved facilities, repacked RF homes - becomes visible market by market.

How do READS rankings differ from Nielsen ratings?

Different question entirely. READS rankings are computed from Longley-Rice coverage predictions combined with Census population - who can receive a station - while Nielsen-style ratings measure who is watching. Use READS for availability, coverage and signal-reach arguments; use a measurement currency when the argument is about audiences.

How far back does coverage go?

The reference has operated since 2008 and stays current to August 2026, with historic 1952 allotment records retained alongside the modern dial. Deep history between those markers accrues from repeated captures on your chosen cadence, so longitudinal projects should start recording early rather than assume a full retrospective archive.

Can deliveries extend past the eight core fields?

Yes - ask at sample request. Deliveries can attach TSID and TSR date views, ATSC 3.0 RENDER dates, READS values, maxcontour and channel-sharing references, deleted-station and expiration records, and the network-grid, signal-prediction and bandscan surfaces. Each is mapped against live records when the sample is cut, so the schema you evaluate is the schema you ship against.

Notes on this record

  • Provenance RabbitEars.info - an independent, single-editor US broadcast-television reference operating since 2008 and a member of the Worldwide TV-FM DX Association. One obsessive curator is why the edge cases exist at all.
  • Display versus RF is the whole point WCBS-TV dials as channel 2 and transmits on RF 36. The repack scattered physical channels across the dial while viewers kept dialing familiar numbers - any tool that conflates the two is wrong in ways users will find immediately.
  • READS, not ratings The reference computes its own READS rankings from Longley-Rice coverage predictions and Census population rather than Nielsen figures - a who-can-receive-it lens instead of a who-is-watching lens.
  • Scored 8 out of 10 Against Datadory's rubric that sits above the 7.81 catalog-wide average across all 1,744 datasets, carried by verified field documentation and four nested levels of geographic resolution.
  • Sample policy Samples ship in the exact schema shown above, filtered to the markets, stations and specialist lists you name; anything beyond the eight spine fields is confirmed against live records when the sample is cut.

Datasets that pair with this one

See the rows before you pay anything.

Name this dataset and we send real records from it — scoped to the fields you asked for.

See pricing