Independent information guide India 18+ No account or payment services
Panoramic cricket stadium used for the MegaPari cricket information guide
Cricket editorial

MegaPari Cricket Guide for India: Match Stages, Scores and Mobile View

Updated: 13 July 2026Reviewed by MegaPari.digital
Match information timeline

Before, live and final records need different fields

The sequence below explains interface states without inserting a fixture, result or real-time feed.

01 · BEFORE

Before the Match

  • Competition and venue
  • Scheduled start
  • Teams or published squads
  • Published event categories
02 · LIVE STATE

During Play

  • Innings and runs
  • Wickets and overs
  • Current state
  • Last refresh time
03 · FINAL

After the Result

  • Final score
  • Completed status
  • Result source
  • Correction history
CRICKET INFORMATION ILLUSTRATIONIllustrative interface — not a live scorecard
Competition
Match stateSource required
Innings
Score
Overs
Last checkedNo live feed
Cricket reference panel

Terms that help a score view make sense

TermPlain-language meaningInterface use
InningsA team's turn to bat.Separates the match into scoring periods.
OverA set of valid deliveries by one bowler.Provides the basic progress marker.
Run rateAverage runs scored per over.Adds pace context; it is not a forecast.
Result statusScheduled, delayed, in progress or completed.Prevents archived information being mistaken for live data.

Before a cricket match starts, the useful fields are the competition, venue and scheduled time. During play, attention shifts to the innings, score, wickets and overs. After the result, the final score and completed status should remain stable.

Before the Match

Pre-match information sets the frame for everything that follows. Confirm the competition, teams, venue and published start time before treating a row as the intended match. Squad or category details can be updated before play, so their source time should remain visible.

During Play

Runs, wickets and overs belong to the same innings. Reading one field without the others can produce the wrong picture of play. A current score therefore needs an innings label and refresh time, while a delayed screen should not be described as live merely because it still shows the latest known total.

Run rate is a descriptive calculation from the recorded score and overs. It is not a forecast. Use it only with the innings and refresh context shown on the same screen.

Read the Scorecard Fields Together

The original scorecard above contains dashes and “Source required” labels on purpose. It teaches the layout and does not represent a match.

Runs, Wickets, Overs and Run Rate

Runs are the scoring total for the innings. Wickets record dismissals, while overs show how far the innings has progressed. These fields belong together: a total without wickets can hide the state of the batting side, and an over count without an innings label can be attached to the wrong part of the match.

Run rate describes scoring pace from the recorded runs and overs. It changes as the innings moves and should carry the same refresh time as the score. It does not say what will happen next, settle a result or replace the match rules.

Delays and Revised Targets

LabelMeaning on an information screenReader action
DelayedPlay or the data feed is not continuing as scheduledLook for a revised time or reason
Revised targetThe target has changed under the applicable match conditionsRead the new target with its source and innings
AbandonedThe match did not reach a completed resultDo not treat the last score as final
CompletedA final result has been recordedUse the final source and retain later corrections

Mobile Cricket View

A compact screen should keep the innings, score, wickets, overs and status together. Tournament filters and team names may move into a secondary row, but the fields that define the live state should not disappear behind an icon. Notifications are summaries; reopen the record before relying on a result.

Competition and Format Context

A short-format match and a multi-innings match do not use the same reading rhythm. Keep the competition and format visible near the scorecard so overs, innings and completion labels are not interpreted outside their rules. Team and venue names also need enough space to avoid confusing similarly titled events.

After completion, the final record should keep the result, source and any later correction together. An abandoned match is not a completed match, and the last visible score before abandonment is not automatically a final result.

A revised target should remain attached to the innings and condition that produced it. Without that context, the number can be mistaken for an original target or a final score.

Source and Correction Status

Changing match information needs a dated source. A completed record can still receive a correction, but the correction should identify what changed rather than presenting the new value as though it was always there. Review the wider sports status model or check the source-review record for the evidence rules used here.

Return to the India guide overview for the product map, or use the mobile source checks before trusting an installed route.