Fairplay guide to rate displays and scorecards, separating portal data from fair play in sport, predictions and uncertain final results with care.
What a rate can tell you—and what a scorecard can tell you
A Fairplay rate display records a named market at one observed moment; a scorecard records reported match events. Compare them only after attaching fixture, format, status and times to both. Neither display establishes why a match changed, what will happen next or a recommended outcome.
This guide is narrower than the Fair Play odds field guide, which defines board fields, and the scorecard reading guide, which covers notation. Its job is to test whether a dated rate snapshot can sit beside a verified fixture, innings state and result without filling gaps.
Key takeaways
- Record fixture identity, format, status and board-capture time before comparing values.
- Treat a visible update label or page-check as display evidence, not an upstream timestamp unless labelled as one.
- Use an official fixture or scorecard for identity; if status or score is absent or conflicts, record an incomplete comparison.
- Read back, lay and stake fields as observed display data, never as a prediction or a reason to act.
Record the fixture, format, status, and rate timestamp
Start with a snapshot note, not a number. Preserve the event name, competition and format labels, scheduled start, status, runner names, board-capture time and every supplied limit or delay. A later refresh can show different levels, so an uncaptured number has little comparison value.
Keep three times separate: scheduled start, visible update label and capture or page-check time. Only a source-labelled provider timestamp establishes when an upstream record changed. The public Fair Play Rates board says it refreshes every 10 seconds and labels unavailable values; that does not make a board check an official score update.
Format belongs in the note. The ICC publishes separate current playing conditions for Tests, ODIs and T20Is. Here, format defines the record being checked; it does not make separate matches or dates comparable.
Match the runner name to the official scorecard
Check a runner label against an official fixture before treating it as a scorecard team. Match both team names, competition, date, format and venue where supplied. Abbreviations, A sides and domestic competitions can otherwise create a false match.
For the retained 12 October 2026 example, Cricket Australia lists Victoria v South Australia in the One-Day Cup 2026–27 at Junction Oval, Melbourne. That supports the Fairplay card’s team, date and competition identity. The official match-centre entry rendered as Upcoming in this review and exposed no innings or result. Identity is verified; the scorecard is not.
Use an official competition title and state as the reference when available. A portal card can help locate a match but cannot replace that record.
Read back, lay, and stake fields without turning them into a tip
After identity is established, transcribe each runner’s fields as a snapshot. Keep every rate beside its displayed stake and board side. Do not combine levels into an invented price, reverse runners or pass off a later value as the same observation.
Handle limits the same way. If minimum and maximum do not form a coherent pair, record “conflicting or unavailable”, not a corrected limit. The board presents display and virtual-use information only; a stake field is not proof of availability, a transaction or an outcome.
Use How Fairplay Works for portal boundaries. It keeps market formatting distinct from match analysis and from sporting fair play.
Compare the market snapshot with innings state and final result
Compare in order: rate snapshot, scorecard state at a separately identified source time, then official result after completion. A live innings gives context at one moment; it does not explain a snapshot taken earlier or later. A final result closes the match record but does not explain a board value.
The Fairplay results archive says to open the scorecard before separating an outcome from an innings score. It shows Australia Women 168/3 after Bangladesh Women 166 all out, recorded as a seven-wicket win. That portal example remains separate from official corroboration for any broader claim.
A rain record shows the limit. Cricket Australia reported on 18 September 2026 that Western Australia made 9-238, South Australia were 0-58 after 7.4 overs, and rain left the match a no result because South Australia had not faced 15 overs. That declared state—not a reconstructed total—is the result.
Worked example using a dated real scorecard and retained display capture
This is a reproducible but incomplete comparison, not an interpretation. The Fairplay rendered-rates capture was taken at 07:20:46 UTC on 12 October 2026 (12:50:46 pm IST). Its screen said “Updated 12:50 pm” and “Refreshing every 10 seconds”; it showed Australia One Day Cup, Victoria v South Australia, 12 Oct 08:30 am IST, “Open market” and “Live”. No upstream-source update time was visible.
The displayed runner fields were: Victoria back 1.94 (1,05,399 stake), 1.93 (44,258), 1.92 (16,181); Victoria lay 2.02 (609), 2.04 (29,084), 2.06 (189). South Australia back 1.98 (30,453), 1.97 (135), 1.94 (10,991); South Australia lay 2.08 (1,39,371), 2.10 (14,794), 2.12 (334). The card showed minimum stake 100, maximum stake 1 and six-second delay. That conflicting pair is unavailable for comparison, not a valid limit.
The official fixture supports teams, competition, date and venue, but its retrieved match-centre text gave no innings or result and labelled the fixture Upcoming. The parallel Fairplay score desk showed zero rows while its selected-date request was still loading at the same displayed minute; that is a pending display, not a confirmed empty response. Observed: dated rate card and conflicting limit. Context: official fixture for the same teams, date and venue. Unknown: matching official innings, result and upstream update time.
| Evidence item | What was retained | What it supports—and what it does not |
|---|---|---|
| Fairplay board capture | 07:20:46 UTC; display label 12:50 pm IST; Victoria and South Australia runners; Open market and Live; levels, stakes, minimum 100, maximum 1, delay 6 sec | A time-specific display snapshot. It does not supply an upstream time or official score. |
| Cricket Australia series listing | One-Day Cup 2026–27; Victoria v South Australia; 12 October; Junction Oval, Melbourne | Official fixture identity and venue. |
| Official match-centre retrieval | The relevant entry rendered Upcoming; no innings or result in retrieved text | An unresolved status/scorecard gap, not a reconciliation. |
| Fairplay score-desk capture | Source and checked labels both 12:50 pm IST; zero displayed rows while the selected-date request was loading | The desk did not supply a matching public scorecard at that displayed check. |
Missing data, changed markets, and source disagreement
Missing data is a result, not a gap to smooth. Preserve a dash, absent runner, missing scorecard or contradictory limit, then say which comparison cannot be made: board-to-score, one capture-to-later capture, or snapshot-to-final result.
Two real One-Day Cup records also show why same format does not make records comparable. South Australia’s 23 September 2026 seven-run win over Tasmania finished 383/7 to 376/8; Western Australia v South Australia on 18 September ended no result after rain. Neither has a retained matching Victoria board snapshot, so neither explains the 12 October fields or their movement.
If sources disagree, report it next to the field rather than selecting a convenient status. Cricket Analysis offers source-bounded context; Fairplay’s editorial policy requires missing values to stay missing.
Why this is context, not a prediction or wagering guide
A careful comparison asks limited questions: Which fixture did the card name? When was it captured? Which fields were visible? Does an official fixture confirm identity? Was an innings or result actually published? It does not create a probability, recommendation or advance result.
Keep a short audit note: capture reference, fixture, format, runners, displayed-update time, capture time, upstream time if labelled, official links, and every absence or conflict. Add an official result as a new dated record rather than rewriting the old snapshot.
Fairplay is the portal name here. Sporting fair play concerns conduct; a rate display and scorecard concern different kinds of cricket information.
Questions, answered
Are Fairplay cricket rates the same as a scorecard?
No. A rate display preserves supplied market fields at an observation time; a scorecard records innings and match information. Match fixture and times before comparing them.
What time should I record from a cricket rates board?
Record scheduled fixture time, visible update label, and board-capture or page-check time separately. Treat an upstream time as unknown unless the source labels it.
What if the official scorecard is missing or says a different status?
Document the identity match and disagreement, then stop. Do not create a score, result or reconciliation from a rate display, partial card or later refresh.
Why can a minimum and maximum stake field not be used as a limit?
A minimum of 100 and maximum of 1 do not form a coherent limit. Preserve both and mark the limit conflicting or unavailable.
Does a final result prove what an earlier rate meant?
No. A result records how the match ended; it does not reveal the earlier source state, explain a rate or turn it into a prediction.
Sources and evidence
- Fair Play Rates board
Retrieved 2026-10-12. Public board scope: display-only rates, back and lay fields, status, context, refresh and unavailable-value language; detailed 12 October snapshot preserved in private evidence.
- Cricket Australia — One-Day Cup 2026–27
Retrieved 2026-10-12. Official series listing for Victoria v South Australia on 12 October 2026 at Junction Oval, Melbourne.
- Cricket Australia — Victoria v South Australia match centre
Retrieved 2026-10-12. Official match-centre page; retrieved text rendered no innings or result, so the scorecard gap is retained.
- ICC Playing Conditions
Retrieved 2026-10-12. Official hub listing separate current playing conditions for Test, ODI and T20I cricket.
- Fair Play Live Score
Retrieved 2026-10-12. Source-time/check-time, coverage and missing-scorecard boundary language.
- Fair Play Cricket Result archive
Retrieved 2026-10-12. Dated returned-result examples and guidance not to infer margins from incomplete score data.
- Cricket Australia — South Australia v Tasmania match report
Retrieved 2026-10-12. Official 23 September 2026 One-Day Cup report: South Australia 7-383, Tasmania 8-376, South Australia won by seven runs.
- Cricket Australia — Western Australia v South Australia rain report
Retrieved 2026-10-12. Official 18 September 2026 rain/no-result report: WA 9-238 and South Australia 0-58 after 7.4 overs.
- Fairplay Editorial Policy
Retrieved 2026-10-12. Publication policy on traceable sources and preserving missing values rather than inventing figures.
Scheduled facts and sourced history are separate from live match data. Source attribution does not imply affiliation with IPL, BCCI, ICC or players.