Horse racing and football resultsIndependent sport. No betting promotions. Our story
results.fast

Explore

Your dashboardOverview The form book Journal Saved eventsSports glossarySettlement tools

Behind the results

Data & coverage Editorial standards About us Corrections

Independent information. No betting affiliates.

Horse racing result statuses explained

The status tells you how to read a race result. A race may be planned, under review or confirmed. A blank result does not tell you which of these applies.

Illustration accompanying Horse racing result statuses explained
AI-generated illustration. Does not depict a specific event.

How to apply this guide

A practical guide to provisional results, enquiries, non-runners and abandoned races.

For a close finish, the photo-finish and dead-heat guide explains the distinction. Browse the horse racing archive to inspect stored finishing orders and their reported status.

Treat a status as part of the result

The finishing order tells you who crossed the line in which position. The status tells you how to interpret that information. An early order can be provisional; an enquiry may lead to a change. A results page that strips away these labels loses an important part of the record.

Our service preserves provider labels and does not promote an ambiguous status to “official”. If the provider does not supply confirmation, we say so.

A race that has not produced a result

Scheduled means an event is expected to take place. A delay is not a cancellation, and an abandoned meeting is not a race with zero finishers. Keep those situations separate when searching an archive.

A blank result does not prove that the race was abandoned. It may mean coverage is unavailable or that the data has not arrived. We show an empty coverage message instead of interpreting missing data as a sporting outcome.

A runner that does not have a finishing place

A non-runner should be distinguished from a horse that started and did not finish. Codes such as pulled up, fell or unseated rider describe different circumstances. Where supplied, keep the original label with the runner.

Do not include non-runners in a count of finishers. Equally, do not assign a finishing rank to a horse simply to make a table look complete. A meaningful gap is more accurate than an invented number.

Corrections are part of accurate reporting

Later corrections can update spelling, connections or the order itself. A stable race identifier keeps those revisions attached to one event instead of producing duplicate pages.

When comparing an old image with a current page, check the status and update time. Our results pipeline replaces the event’s current record with the latest successful provider response and keeps collection health separate from race confirmation.

Keep race status and runner status separate

A race can be complete even though an individual runner did not finish. Conversely, the presence of a list of declared runners does not mean the race has taken place. Use an event-level status for the race and a runner-level code for the horse.

This distinction matters when counting participants. A declaration list, a count of starters and a count of finishers answer different questions. If a provider supplies only a runner array without a separate participation count, describe it as the records supplied rather than claiming every entry completed the race.

Follow an amendment without creating a second race

When an order or a runner detail changes, the event remains the same race. A stable identifier allows a service to update the record while keeping bookmarks useful. Comparing two snapshots is easier when each includes the collection time and the original status.

An archive should not silently treat an incomplete early report as a new event when fuller information arrives. It should also avoid suggesting that a successful data download proves an official decision. The sporting authority determines the outcome; the collection system reports the information it received.

Race and runner labels

Race and runner labels
LabelLevelHow to read it
ScheduledRacePlanned event; no result implied.
ProvisionalRaceAn early report that may change.
AbandonedRace or meetingThe event did not proceed to its normal completion.
NRRunnerNon-runner; did not take part.
PURunnerPulled up; not an ordinary finishing place.
F / URRunnerFell / unseated rider; preserve the supplied code.
DSQRunnerDisqualified; check the applicable result record.

A complete race with an incomplete field

A fictional jumps race might list three numbered finishers and a fourth runner marked PU. The race has a result, but the fourth horse should not be displayed as fourth merely because its row follows the third finisher. A non-completion code carries information that a number would erase. If the same result also contains a non-runner, that horse belongs to a different participation category again. Use the provider’s labels to distinguish the outcomes rather than converting every row into a consecutive placing.

A practical reading checklist

  1. Check whether the label applies to the race or a horse.
  2. Do not count declarations as confirmed starters.
  3. Keep non-completion codes visible.
  4. Recheck an early order if an enquiry is reported.

For unfamiliar terms, use the racing and football glossary alongside the result.

Common questions

Does “result received” mean the result is official?

No. On this site it means a provider result was received without a separate official-confirmation field. It is deliberately different from an explicit official verdict.

What should I infer from an empty result?

Only that the record is unavailable in the selected coverage. A connection problem, subscription limit or delayed report can all produce an empty view.

Sources and further reference

Examples in this guide explain how to read a record; they are not reports of actual events. Competition-specific rules and the provider’s field definitions take priority for a particular result.

Editorial standards · Report a correction

Related reading

All guides