Sports Guides
How the Live Events Schedule/EPG Works
Where schedule data comes from and why it drifts from reality.
Where schedule data comes from
Broadcasters publish their schedules, and metadata companies aggregate, normalise and resell that data to app providers. The app receives a feed and displays it, with limited ability to correct it in real time.
- The broadcaster publishes its own schedule.
- A metadata provider aggregates and normalises it.
- The app provider licenses and displays the feed.
- The viewer sees the schedule in the app's EPG.
The licensing model — broadcaster to metadata vendor to app provider — is standard industry practice and is documented across the guide industry.
The critical detail is that the app does not write the schedule. It displays what a third party has already assembled, which means the quality of the schedule depends entirely on the quality of the metadata provider and on how often the app refreshes the feed.
Why it drifts from reality
Fixtures move after schedules are published: matches slip for weather, rights partners re-time games for television, and leagues change dates late in their seasons. The EPG feed refreshes on a cycle, so the displayed schedule lags the broadcaster's own corrections, sometimes by hours.
| Cause of drift | Example | Consequence |
|---|---|---|
| Weather postponement | Tennis and cricket rain delays | Listed time no longer matches play |
| Television re-timing | League games moved for broadcast | Listed fixture is in the wrong slot |
| Late fixture changes | Playoff dates set late | Channel may be empty or showing a repeat |
| Time-zone confusion | International events | Listed time is wrong for the viewer |
Some sports drift more than others. Tennis and cricket shift constantly because weather reschedules matches mid-day; football shifts because television re-times games days ahead; and late-season league fixtures move because playoff positions change. A schedule that is accurate for one sport can be hopelessly wrong for another.
Refresh cycles and regional variants
EPG feeds are refreshed on a cycle — every few hours at best, often less frequently. A correction published by a broadcaster at midday may not reach the app until the evening, and a viewer who checked at 11am has seen yesterday's data.
- Metadata is compiled in batches, not live.
- Corrections propagate on the provider's refresh cycle.
- The app may cache the last received feed rather than request a fresh one.
- Regional variants of the same channel can show different schedules.
The same channel often exists as several regional variants, each with its own schedule, and the EPG metadata must be matched to the right variant. When the match is wrong, the viewer sees a channel whose listed programme belongs to a different region, which is one of the most confusing forms of drift.
What 'live' actually means in the listing
A row marked 'live' means the feed is expected to be showing an event at that moment, based on the metadata. It does not mean the app has verified the broadcast, and it does not mean the rights holder is actually transmitting that game to you in your territory.
The word 'live' is therefore an assertion about the metadata, not a statement of fact about the feed. When the two disagree, the metadata is the one that is wrong.
How to read the schedule critically
Check the date and time zone, cross-reference marquee fixtures against official sources, and treat channels with no row at all as simply lacking current data rather than being offline.
1.Check the league's own schedule
The league or tournament is the authoritative source for its fixtures.
2.Compare with the broadcaster
The rights holder publishes its own listing, which predates the aggregated EPG.
3.Allow for the refresh cycle
A change announced today may not reach the app until the next refresh.
4.Re-check closer to the event
The metadata is most reliable in the hour before broadcast and least reliable weeks in advance.
There is also a difference between how often the data is refreshed and how often it is accurate. A provider can refresh the feed hourly and still show stale data if the upstream metadata vendor has not published the correction. The viewer cannot tell which stage failed, only that the schedule no longer matches the broadcast.
- A stale feed is usually a metadata problem, not an app problem.
- Corrections can be lost at any stage of the chain.
- Regional variants make a correct entry look wrong.
- The closer to the event, the more reliable the data.
The practical routine is to treat the EPG as a starting point, verify marquee fixtures against the league's own announcements, and accept that mid-card or minor fixtures will occasionally be wrong. None of that makes the schedule useless; it makes it exactly what it is — compiled data with a refresh lag.
There is also a difference between the public schedule and the data behind it. The league's own site and the aggregated EPG are two different documents, and the EPG is the one that arrives late. When they disagree, the league's own announcement is the authority, because it is the source from which the metadata is eventually derived.
- The league's schedule is the source of truth.
- The EPG is a derivative copy that lags behind it.
- Flex changes appear on the league site first.
- The copy catches up on the provider's refresh cycle.
In practice this means checking the league's own announcements for anything you actually plan to watch, and treating the app's schedule as a convenience for browsing rather than as a contract. That single habit removes most of the confusion people experience with live sports listings.
Whether AK47 Sports sources its EPG from a named metadata vendor, and how often its schedule feed refreshes, is not disclosed and cannot be verified.
Worth knowing: The live events schedule in an app is generated from electronic programme guide (EPG) data licensed from third-party metadata providers, which is why it drifts from reality.