Sources and accuracy
RacingDay lists trail running, road running and triathlon races in Hong Kong, mainland China and the Asia-Pacific. This page sets out where the data comes from, what its limits are, and what to do if you find a mistake.
One-minute read
- The data is collected and compiled automatically from public sources compiled automatically — we have no partnership, licensing or sponsorship relationship with any organiser.
- . It can be wrong and it can be out of date.Race dates, distances and entry status always follow the organiser's official announcements.
- This is a search and research tool, not an authoritative record.
- Found a mistake, or want your data removed? Email info@racingday.org,We respond within 24 hours.
Where the data comes from
All of it is Public data. In short, there are three kinds:
- Official organiser announcements — race dates, distance categories and entry status are based on these.
- Public race information — used to fill gaps and add detail, but this is third-party reproduction and less accurate.
- public route data — used to calculate the route profile (see below).
We do not publish a list of individual sources, and we do not publish our collection method. If you want to know where the data for a particular race came from, email us and ask.
Accuracy and limits
Read this section carefully — errors can happen at many levels, and each level feeds into the next:
- The source itself.Race dates, routes, distances, entry status and fees can change, be postponed or be cancelled at any time; public announcements themselves can contain errors or exist in several versions.
- Automation.Collection, matching, organisation and analysis are all carried out automatically — programs and tools can go wrong (parsing failures, matching the wrong race, mis-calculated values, missed updates). “Processed by machine” does not mean accurate.
- Manual review.Important changes are looked at by a person once, but people also miss things or judge them wrongly; Review is an extra layer, not a guarantee.
- Time lag.The data is updated on a cycle, so it may lag behind the organiser's latest announcement.
Always check the official announcement before entering.The data here should not be your only basis for training or race decisions.
How to read entry status
The status labels on the event card and the filter are exactly consistent (the same calculation), so you will not get “the event card says closed but it appears under the ‘Open’ filter”. Status always falls into these six:
Not open yet Open Closing soon Closed TBC Finished
On race day it shows Takes place today; once race day has passed it automatically becomes “Finished”.
Label appearance = data reliability
- Filled (solid background) — confirmed on an official organiser page.“Open” always uses a filled style.
- Dashed border, transparent background— unofficial sources or our own estimate (race directories, inference from convention, or no official closing date).
- Grey “Unconfirmed” — we do not currently have entry status data for this race.
Click or long-press a label for a tooltip stating the data source and the basis for the estimate (official / directory / inferred / no data).
Route profile and GPX export
- The route profile is calculated by us, not a figure published by the organiser — it is calculated from public route data, and will differ from official figures by 1–3%.
- Official route files are always provided as external links (the original file stays on the organiser's own server), and we do not publish it as content of this site.
- So that runners can import routes into a sports watch, we obtain route coordinates separately from public sources to provide analysis and GPX export. Route the organiser.
- Route files may be community versions, may contain GPS drift, may be missing sections or may be from a previous year's route — the organiser's final announcement prevails.
- If an organiser asks for removal, we We respond within 24 hours.
What we do not do
- We do not reproduce or host organisers' logos, photos, articles or maps.
- We do not present entry fees or terms as our own — we always link out to the official page.
- We do not invent races that cannot be traced to a public source.
- We do not collect personal data and we do not use tracking cookies.
- We do not sell or disclose our list of data sources or our collection method.
Corrections / removal
Organisers, rights holders, or anyone who has found a mistake: email info@racingday.org. We will respond within We respond within 24 hours. The same address can be used to suggest a race for inclusion.
English version
In one minute. RacingDay is an independent, one-stop race finder covering trail running, road running and triathlon across Hong Kong, Mainland China and Asia-Pacific. All content is compiled from public sources; we have no partnership, licence or sponsorship with any organiser. Data can be wrong or out of date — always confirm dates, distances and entry status on the organiser's official page. This is a discovery and research tool, not an authoritative record. To report an error or request removal, email info@racingday.org; we act within 24 hours.
Where the data comes from. Public sources only: organisers' own published information (authoritative for date, distance categories and entry status), public race listings (third-party, used to fill gaps, lower accuracy), and publicly available route data (used to compute course profiles). We do not publish our source list or our collection methods; to ask about the provenance of a particular race, email us.
Accuracy and limits. Errors can occur at several layers and carry downwards: (1) the source itself may change, be cancelled, or be published in conflicting versions; (2) collection, matching, normalisation and analysis are automated, and automation and its tools can fail — parsing errors, a race matched to the wrong event, miscalculated values, missed updates; (3) human review exists for significant changes but humans also miss things — it is an extra layer, not a guarantee; (4) there is an update cycle, so the index can lag behind an organiser's latest announcement. Always confirm on the official page before entering.
Entry status. The badge on a card and the status filter use the same calculation, so they never disagree. Every race falls into one of six states: not yet open, open, closing soon, closed, unconfirmed, finished (plus “race day”). The badge style shows how much to trust it: filled = confirmed on the organiser's own page (the “open” state is always filled); dashed = non-official source or our own estimate; grey = we have no status data for that race yet. Tapping or long-pressing a badge shows a tooltip with the source and the reasoning. Some races take entries on the day, and some close in phases or per category — the organiser's published information always prevails.
Course profiles and GPX export. Profiles are computed by us from publicly available route data, not published by the organiser; expect a 1–3% difference from official figures — for studying race segments only. Official route files are provided as external links: the original stays on the organiser's server and we do not present it as our own content. Separately, so that runners can load a course onto a sports watch, we obtain route coordinates from public sources and offer analysis and GPX export; the route remains the organiser's copyright. Route files may be community versions with GPS drift, missing segments or a previous year's route — the organiser's final publication prevails. Removal requests are handled within 24 hours.
What we do not do. We do not reproduce or host organisers' logos, photos, articles or maps; we do not present fees or terms as our own (we always link to the official page); we do not invent events with no traceable public source; we collect no personal data and use no tracking cookies; and we do not sell or publish our source list or collection methods.
Corrections and removal. Organisers, rights holders and anyone who spots an error: email info@racingday.org and we will act within 24 hours. The same address is open to event suggestions.