SatIndex Daily Transponder Scan Database
Datadory delivers satindex daily transponder scan database data covering 8,621 channels on 17 European satellite positions - anchored on Astra 19.2°E and Hotbird 13°E - resolved per channel into frequency, symbol rate, FEC, modulation, TSID, video/audio/PMT PIDs and encryption status, refreshed by daily scans plus a nightly automated AI scan. Delivered daily, weekly, or hourly - your call.
What is the SatIndex Daily Transponder Scan Database?
A German scanning operation whose full name - Satelliten, Sender und Frequenzen, satellites, channels and frequencies - is also an accurate table of contents. It scans several European satellite positions every day and publishes what it finds as two nested layers: the transponder, then the channels riding it. The current state of the scans counts 17 satellites and 8,621 channels - 7,043 TV services, of which 2,871 broadcast in HD, split between 1,640 free-to-air and 5,403 encrypted.
The two flagship positions carry the weight: Astra 19.2°E with 894 programmes and Hotbird 13°E with roughly 1,200, the two orbital slots most European dish owners can receive with a fixed installation. Fifteen further satellites get their own sections, alongside Pay-TV provider pages and country views.
Beyond the tables the operation runs tooling that most channel directories do not bother with: a Sender Sonar, a PID scanner, live blindscans, channel screenshots, a feed ticker of new and discontinued channels, and a nightly automated AI scan layered on top of the daily human-driven passes.
It scores 7 out of 10 on Datadory's quality rubric, with field definitions verified against delivered rows rather than inferred.
Get a sample of this dataset cut to your satellites, transponders or channels.
What do sample rows from the dataset look like?
One row per channel per transponder, keyed by service identifiers and stamped with the date of the last scan that touched it. Four straight from the channel tables:
Sender : Arena Premium 1
SID : 1451
Video PID : 251
Audio PID : 3511
PMT PID : 151
Update : 03.04.2025
Sender : Arena Sport 1
SID : 1455
Video PID : 255
Audio PID : 3551
PMT PID : 155
Update : 18.06.2026
Sender : HBO HD
SID : 1454
Video PID : 254
Audio PID : 3541 | eng 3545
PMT PID : 154
Update : 01.07.2024
Sender : N1 HD Kategorie: Nachrichten
SID : 1466
Video PID : 266
Audio PID : 3661 | srp
PMT PID : 166
Update : 01.07.2024Four rows, four things worth noticing. The identifier spine - SID, video PID, audio PID, PMT PID - means a channel keys into a demultiplexer configuration or your own title database without fuzzy matching; HBO HD resolves to exactly one service at SID 1454. Audio PIDs arrive with ISO language tags (3541 | eng, 3661 | srp), so multilingual tracks are separable at parse time rather than guessed from channel names. Category arrives in German (Nachrichten = news) because the source interface is entirely German - a translation pass is part of any pipeline built on it. And the Update stamps span more than two years across these four rows alone, which tells you the honest thing about this data: freshness is per channel, not global.
What fields does the dataset include?
Nineteen documented fields in two groups. The carrier group describes the transponder itself: frequency, polarization, symbol rate, FEC, modulation, roll-off factor, transmission standard, network name, TSID, measured bandwidth and beam. The service group describes each channel on that carrier: channel name, encryption status, country and category, the four identifiers (SID, video PID, audio PID, PMT PID), the teletext PID, and the update stamp. Every definition below was verified against a worked example - one real frequency page pins a DVB-S2 8PSK carrier at 11,679 MHz vertical, 30,000 kS/s, FEC 3/4, roll-off 0.20, network "Total TV Network", TSID 30204, carrying a measured 66.85 Mbit/s on beam 1P.
Additional fields on request. Signal level readings sit alongside bandwidth on the frequency pages, and the change-log side of the operation - new and discontinued channels, changed PIDs, encryption flips, resolution changes - can be shaped into a delta feed keyed on the same identifiers. Each gets defined and exemplified against delivered records before your schema locks.
Where does coverage reach across geography, time and granularity?
- Geo: Seventeen European satellite positions, anchored on Astra 19.2°E and Hotbird 13°E - the two slots a fixed European dish actually sees - with fifteen further positions in dedicated sections. Channel entries themselves span many countries, tagged per row.
- Temporal: A rolling current-state snapshot, re-scanned daily with an automated AI pass running nightly on top. Every channel row carries its own dated update stamp, so the age of any single record is explicit - sample rows run from 2024 to June 2026. There is no historical archive behind the current state; longitudinal depth accrues from repeated deliveries at your cadence, not from the source holding history.
- Granularity: One row per channel per transponder per satellite, grouped under the frequency page that carries the carrier-level parameters. The finest cut is the individual PID; the coarsest useful frame is the whole orbital position.
That shape is the pitch. Most channel lists tell you a channel exists; this one tells you which carrier it rides, at what symbol rate, encrypted how, and when the scan last confirmed it.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
Cadence should follow the decision being fed. Monitoring a competitor's lineup moves wants the fastest tick you can justify - new and discontinued channels surface within a day of the scan that caught them, and being late to an encryption flip or a channel exit is the same as not knowing. Building a receiver or headend configuration takes a different shape: a full backfill of the positions you serve, then quiet increments keyed on SID so nothing drifts. Research on the European broadcast market usually wants a pinned snapshot, so a chart built today reproduces next quarter.
Because every row carries its own identifiers and update date, incremental pulls key cleanly - yesterday's HBO HD at SID 1454 and today's are joinable without deduplication logic. The sample comes first: name the satellites, transponders or channels you care about, and real rows come back cut to that scope before anything reaches production.
Who builds on it, and for what?
- Competitive intelligence and product teams watch lineup exits and encryption changes land within a day of the scan that caught them - a pay-TV operator losing a marquee channel, or gaining one, shows up here before it shows up in a press release. Patterns collected under competitive intel product teams use cases.
- Data scientists and ML engineers train models on the structured residue of the dial: encryption flags against channel categories, HD adoption curves by country, PID-level fingerprints for automatic channel identification. See data scientists use cases.
- Developers and data-product builders need receiver, app and EPG configurations keyed to real multiplexes - the identifier spine is exactly what a demux setup consumes. Workflows collected under developers builders use cases.
- Journalists, academics and students cite the current European satellite lineup with per-channel evidence rather than an aggregate claim, and the dated update stamps make any citation auditable.
The fit has edges: this record measures the broadcast layer, not the business layer. Revenue, subscriber and pricing questions belong to other datasets; sales-growth teams will find no prospecting signal in a transponder table.
Which notes and neighboring datasets pair with it?
Three notes before you request a sample. First, freshness is per row: there is no single "as of" date for the whole database, so if your use case needs uniform recency, scope the sample to the channels where the update stamps are recent and let the rest age visibly rather than silently. Second, the interface is German throughout - channel names are proper nouns but categories, statuses and section labels are not, so budget for a translation mapping in the pipeline. Third, it documents the carrier and the service, not the fleet: pair it with an orbital-side dataset when the question needs both layers.
Notes and neighbors that pair well with this page:
- The cable & satellite data hub collects all six datasets in the industry, this one included.
- Orbital frame: SatBeams Satellite Coverage & Channel Database covers 500+ geostationary assets with EIRP footprints and dish-size lookups - the layer above this one's carrier detail.
- Head-to-head: SatBeams vs SatIndex Daily Transponder Scan Database - fleet context against per-PID scan depth, and why the join between them runs on orbital position strings.
- Breadth alternative: KingOfSat European Satellite Zapping Directory spans 25,839 channels across 162 countries where SatIndex runs deeper per transponder on fewer, hotter positions.
- Terminology: transponder scan - what a pass of this scanner actually does.
Field dictionary
Every field below is documented against real records. The full dictionary ships with the sample.
| field | type | definition | example |
|---|---|---|---|
Frequenz | number | Carrier frequency in MHz. | 11679 |
Polarisation | enum | Polarization of the carrier, H or V. | V |
Symbolrate | number | Symbol rate in kS/s. | 30000 |
FEC | string | Forward error correction ratio. | 3/4 |
Modulation | enum | Modulation scheme, e.g. QPSK or 8PSK. | 8PSK |
Roll | number | DVB-S2 roll-off factor. | 0.20 |
Art | enum | Transmission standard, e.g. DVB-S2. | DVB-S2 |
Netzwerk | string | DVB network name of the transport stream. | Total TV Network |
TSID | integer | Transport Stream ID identifying the multiplex. | 30204 |
Bandbreite | number | Measured transport bandwidth in Mbit/s. | 66.85 |
Beam | string | Beam carrying the transponder. | 1P |
Field dictionary — service level, one row per channel
| field | type | definition | example |
|---|---|---|---|
| Sender | string | Channel name. | HBO HD |
| Codierung | string | Encryption / conditional-access status of the channel. | encrypted |
| Kategorie | string | Genre category, in German. | Nachrichten |
| SID | integer | Service ID - the primary key of a channel within its transport stream. | 1454 |
| Video PID | integer | Packet identifier of the video elementary stream. | 254 |
| Audio PID | string | Audio PID(s), possibly multiple with ISO language tags. | 3541 | eng 3545 |
| PMT PID | integer | Program Map Table PID describing the service's stream layout. | 154 |
| VT PID | integer | Teletext PID, 0 where none is present. | 0 |
| Update | date | Date of the last scan that verified the channel row. | 01.07.2024 |
Coverage chips — geography, time, granularity
| dimension | coverage |
|---|---|
| Geographic | 17 European satellite positions anchored on Astra 19.2°E and Hotbird 13°E; channel rows span many countries |
| Temporal | Current scan state refreshed daily plus a nightly automated AI scan; every channel row stamped with its own last-scan date; no historical archive |
| Granularity | One row per channel per transponder per satellite; carrier parameters grouped by frequency; finest cut is the individual PID |
Scale snapshot — what one full pull contains
| measure | value |
|---|---|
| Satellites scanned | 17 |
| Total channels | 8,621 |
| TV services | 7,043 |
| HD services | 2,871 |
| Free-to-air vs encrypted | 1,640 / 5,403 |
| Flagship positions | Astra 19.2°E (894 programmes); Hotbird 13°E (~1,200) |
Questions buyers ask
How fresh is satindex daily transponder scan database data?
Scans run daily across several satellite positions, with a nightly automated AI pass on top, live blindscans and a feed ticker reporting new and discontinued channels, changed PIDs, encryption changes and resolution changes. Recency is declared per row: each channel carries an Update stamp from its last verifying scan, and those stamps range widely - sample rows run from April 2025 to June 2026 - so check the stamp on the specific channels your use case depends on rather than assuming a global refresh date.
Which satellites and how many channels does the database cover?
Seventeen European satellite positions holding 8,621 channels: 7,043 TV services, 2,871 of them in HD, split between 1,640 free-to-air and 5,403 encrypted. Astra 19.2°E anchors the set with 894 programmes and Hotbird 13°E carries roughly 1,200 - the two positions a fixed European dish receives - while the remaining fifteen positions have their own dedicated sections alongside Pay-TV provider and country views.
What fields does each transponder and channel record include?
Two levels. Carrier level: frequency in MHz, polarization, symbol rate in kS/s, FEC ratio, modulation scheme, DVB-S2 roll-off, transmission standard, network name, Transport Stream ID, measured bandwidth in Mbit/s and beam. Service level: channel name, encryption status, country, category, SID, video PID, audio PIDs with language tags, PMT PID, teletext PID and the last-scan update date. All nineteen documented definitions were verified against worked examples on real frequency pages, and additional fields are defined against delivered rows at sample time.
Can a sample be scoped to my satellites, transponders or channels?
Yes - that is what the sample is for. Name the orbital positions, the frequency ranges or the channel sets you care about, and real rows come back cut to that scope with field definitions pinned against the delivered records, so you validate the exact extract your pipeline will receive - including how the German-language category and status labels translate - rather than judging from a generic preview.
Does the database keep historical versions of channel lineups?
No archive ships with the current state; the source reports what the latest scan found, plus a ticker of recent changes. History is built by accumulation instead: repeated deliveries on your cadence stack into a longitudinal series keyed on SID and TSID, so a channel's encryption flip or disappearance becomes a dated event in your own tables rather than something reconstructed after the fact.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.