Understand Fairplay’s ten cricket-data pages, the supplied API views, refresh limits, record method and simulated virtual-coin calculations.
Fairplay is a public cricket-data portal
Fairplay organizes available cricket fixtures, score-oriented match views, older result summaries, statistics, analysis, news and practical guides. Fair Play and Fairplay are names for this portal, not separate products or companies. The aim is clear browsing of supplied data rather than a promise about any cricket outcome.
The portal has no accounts, transactions or purchases. It also does not supply a brand history, staff list, affiliation or personal biographies, so this guide does not invent them. It describes the pages, data route, refresh behavior and calculation rules that are actually available.
The ten pages separate live viewing, schedules, records and reading
Fair Play Live, Cricket, Live Score, Fair Play Rates, Upcoming, Result, Statistics, Analysis, News and Guide are the portal’s ten pages. They direct a visitor to the appropriate information state, but no page adds data the supplied route does not provide.
| Page | Use | Boundary |
|---|---|---|
| Fair Play Live | Live-facing match view | Checked time is not score freshness. |
| Cricket | Broad cricket entry point | Not a complete careers database. |
| Live Score | Available score view | Fields depend on match supply. |
| Fair Play Rates | Virtual-coin display | Not prices or probabilities. |
| Upcoming | Scheduled fixtures | A fixture is not a result. |
| Result | Older result summaries | Not a full historical archive. |
| Statistics | Portal records | Eligibility rules apply. |
| Analysis | Data context | No calibrated predictions. |
| News | Portal content | No live-news feed. |
| Guide | Method explanations | Cannot add missing data. |
The supplied cricket-data route supports focused views
Fairplay uses https://jalaxshwholesaleltd.com/api/cricket-data.php. The public route supports all, date, series and match views: a broad collection, a date-filtered collection, series context or one match. These views address the same supplied service and do not mean every response contains every possible cricket field.
The route can provide fixtures, older result summaries, and match innings and team availability. A fixture means scheduled; an older summary is the result information supplied for a previous match; innings and team availability says whether those components are present. If a field is absent upstream, Fairplay should leave it absent rather than reconstruct a full scorecard.
The route does not supply a live-news feed, complete player careers, calibrated predictions or external prices. Therefore News is not a live wire, Analysis is not a calibrated forecast service, and Fair Play Rates does not reproduce outside prices.
| View | Portal use |
|---|---|
| all | Browse a broad supplied collection. |
| date | Browse data narrowed to a date. |
| series | Read supplied series context. |
| match | Inspect available match innings and team data. |
Polling tells visitors when Fairplay checks for data
Fairplay begins with static dated snapshots, then client-polls a visible page. A visible live page polls every 10 seconds; a visible non-live page polls every 45 seconds. This gives an open page a predictable checking cadence without treating every portal route as an always-running live request.
A polling interval does not guarantee score freshness. Upstream caching can return a response already cached before Fairplay checks. A checked-at label can show when the portal asked for data, but cannot prove when a ball, wicket, innings change or result first became available upstream. If no new innings or team information is supplied, the existing state remains the responsible display.
- Visible live pages: every 10 seconds.
- Visible non-live pages: every 45 seconds.
- Static dated snapshots are the starting state.
- Upstream caching can make new checks return older data.
Read fixtures, scores and results as separate states
For a scheduled match, use Upcoming and treat the entry as a fixture. For a previous outcome, use Result and read the available older summary. For a match being followed, use Fair Play Live or Live Score, then check whether innings and team details are present. Cricket is the broad entry point when the visitor has not yet chosen a question.
This separation avoids treating an upcoming match as a result or a partial response as a complete scorecard. It also explains why a score may not move after a poll: the supplied response may be cached upstream, or the particular innings and team fields may not be available.
Statistics use deduplicated completed matches and exact grouping
Fairplay record counts deduplicate completed matches. The same completed match should not raise a count twice because it appears more than once in supplied material or is reached through more than one view. This is a method for the portal’s available records, not a claim to have collected every match ever played.
A largest team total is grouped by exact team name and exact format. This preserves the categories in the data rather than silently merging similar labels. Innings strings containing ampersand or plus markers are excluded because they are combined expressions, not the single-team, single-format comparison used for this record.
A portal record is consequently not an all-time cricket record. Before comparing it with another database, compare the scope, completed-match rule, exact team naming, format grouping and treatment of combined innings strings.
- Deduplicate before counting completed matches.
- Group largest totals by exact team and exact format.
- Exclude innings strings containing ampersand or plus markers.
- Do not label the resulting figures all-time records.
Fair Play Rates uses a deterministic virtual-coin demonstration
Fair Play Rates creates a simulated rate for each fixture side. Its input is fixture ID plus side. For each character, checksum = (checksum × 31 + characterCode) % 1000003. The factor is 1 + (checksum % 151) / 100, producing an arbitrary demonstration from 1.00 to 2.50 virtual coins per unit.
The same fixture-side input produces the same factor, which makes the display reproducible but not predictive. It is not derived from team strength, score state, player careers, news, external prices or a calibrated model. The factor is neither a probability nor a recommendation, offer or transaction price.
Worked example: a fictional fixture-side input with remainder 37 when divided by 151 has a factor of 1 + 37 / 100 = 1.37 virtual coins per unit. This arithmetic explains the display only, not the fixture. For more detail, visit /guide/virtual-coin-rates-explained/.
- The figure is a simulated virtual-coin rate.
- The formula ranges from 1.00 to 2.50 coins per unit.
- It is not an external price or probability.
- No account, purchase or transaction is attached.
Analysis, News and Guide explain available information
Analysis can add context to supplied fixtures, results, innings availability, team availability and record methods. Its useful role is explaining what supports a point and where the source stops; it should not present a calibrated chance of winning. News is portal content rather than a live-news feed.
Guide explains refresh behavior, records and the virtual-coin calculation. It cannot turn the supplied route into a complete careers source. These pages are most useful when their method and source boundary remain visible to the reader.
Use the page purpose and data boundary before drawing a conclusion
Choose Upcoming for fixtures, Result for older summaries, Fair Play Live or Live Score for available score information, and Statistics only with its completed-match and innings rules in mind. Treat Fair Play Rates as a reproducible virtual-coin demonstration. A changed checked time with an unchanged score may reflect upstream caching.
Fairplay is clearest when a visitor can distinguish a dated snapshot, supplied match field, method-limited record and simulated factor. It can identify those states without claiming live news, complete careers, external prices or calibrated predictions. Clear labels make the ten-page structure more useful than unsupported certainty.
Questions, answered
Does Fairplay provide live cricket scores?
Fair Play Live and Live Score are live-facing score pages. A visible live page polls every 10 seconds, but upstream caching means that check does not prove score freshness. Innings and team details depend on match-data availability.
What can the cricket-data API be viewed by?
The supplied route supports all, date, series and match views. It can provide fixtures, older result summaries, and available match innings and team data, but not live news, complete careers, calibrated predictions or external prices.
Are Fair Play Rates odds or probabilities?
No. They are arbitrary deterministic virtual-coin demonstrations between 1.00 and 2.50 coins per unit, calculated from fixture ID and side. They are not external prices, probabilities, forecasts, purchases or transactions.
Why are Fairplay records not all-time records?
They use deduplicated completed matches and largest totals grouped by exact team and format, excluding combined innings strings with ampersand or plus markers. They describe eligible available portal data, not every cricket match in history.
Sources and evidence
- Supplied public cricket-data API
Supports all, date, series and match views; the portal represents only the supplied data described here.
- Fair Play virtual coin rates guide
Internal explanation of the simulated virtual-coin rate display.
Scheduled facts and sourced history are separate from live match data. Source attribution does not imply affiliation with IPL, BCCI, ICC or players.