Skip to main content

Overview

Track status codes indicate racing conditions and safety measures during a session. These codes appear in the status field of lap times data and help identify what conditions affected each lap.
The status field in laptimes.json is a string containing all track status codes that occurred during that lap (e.g., “1” for normal racing, “216” for multiple statuses).

Track Status Codes

Status CodeStatus NameDescriptionTypical When It AppearsNotes
1Track ClearIndicates normal racing conditions with no restrictions. The circuit is considered safe for full-speed racing.At the start of a session, after incidents are cleared, or when other track control statuses end.Often used as a reset state after other flags or control measures.
2Yellow FlagWarns drivers of a hazard on the track (accident, debris, stopped car, etc.). Drivers must slow down and overtaking is prohibited in affected sectors.During incidents where marshals or recovery vehicles may be near the track.Sector-level information may not always be specified in this status, meaning the exact affected sectors can be unknown in the data feed.
3Unknown / UnusedA status code listed in the system but rarely or never observed in real telemetry or timing data.Not typically seen in real race data.Likely reserved for a future state, legacy compatibility, or internal system use. In many datasets it appears unused.
4Safety CarA physical safety car is deployed on track to control the pace while marshals clear hazards or debris. Drivers must follow the safety car at reduced speed and overtaking is restricted.Major accidents, heavy debris, or dangerous track conditions requiring neutralization of the race.Race control manages field order behind the safety car. Lapped cars may be allowed to overtake depending on regulations.
5Red FlagThe session or race is stopped due to unsafe conditions (serious accident, barrier damage, severe weather, etc.). Cars return to the pit lane or stop as directed.Major incidents or conditions where continuing even behind a safety car is unsafe.Timing may be paused depending on session type. Restart procedures vary by race regulations.
6Virtual Safety Car (VSC) DeployedA neutralization procedure where drivers must follow a controlled speed delta instead of following a physical safety car.Smaller incidents where marshals need time on track but a full safety car is unnecessary.Drivers maintain a regulated pace via dashboard delta timing rather than forming a queue behind a safety car.
7Virtual Safety Car EndingSignals that the Virtual Safety Car period is about to end and racing will resume shortly.Immediately before the VSC period concludes.Drivers see the “VSC ending” notification on steering wheels and broadcast graphics. Status ‘1’ will follow to confirm the return to normal racing conditions.

Status Code Details

Conditions: Normal racing with no restrictionsDriver Rules:
  • Full racing speed permitted
  • Overtaking allowed
  • No special caution required
Common Usage: Default state at session start and after clearing incidents
Conditions: Hazard on track requiring cautionDriver Rules:
  • Must slow down in affected sector(s)
  • No overtaking in yellow flag sectors
  • Must be prepared to stop if necessary
Important Note: Sector-level detail may not always be available in the data feed, so the exact location of the yellow flag may be unknown from status code alone.
Status: Reserved but not actively usedObservations: Rarely or never appears in real race telemetry dataLikely Purpose: Legacy compatibility or reserved for future implementation
Conditions: Physical safety car deployed on trackDriver Rules:
  • Must reduce speed and follow safety car
  • No overtaking (except lapped cars when permitted by race control)
  • Must maintain position in queue
When Used: Major incidents requiring on-track marshaling or debris clearanceRace Control: Manages field order; may allow lapped cars to unlap themselves
Conditions: Session stopped due to unsafe conditionsDriver Rules:
  • Return to pit lane immediately (or stop on track as directed)
  • No racing activity permitted
  • Await restart instructions
Common Causes:
  • Serious accidents
  • Barrier damage
  • Severe weather
  • Track surface issues
Timing Impact: Session timing may be paused; restart procedures vary by regulations
Conditions: Controlled neutralization without physical safety carDriver Rules:
  • Must maintain speed delta shown on dashboard
  • No overtaking
  • Controlled pace via electronic timing system
When Used: Incidents requiring marshal intervention but not severe enough for full safety carAdvantage: More predictable timing for pit stops; less bunch-up than physical safety car
Conditions: VSC period about to concludeDriver Rules:
  • Prepare to resume racing
  • Watch for green light/notification
  • Status ‘1’ (Track Clear) will follow
Display: Drivers see “VSC ending” message on steering wheel displays and broadcast graphicsTiming: Brief transition period before full racing resumes

Multiple Status Codes

A single lap may experience multiple track statuses. In the data, these are concatenated as a string. Example:
  • "1" = Track clear throughout lap
  • "216" = Track clear (1), then yellow flag (2), then VSC deployed (6)
When analyzing lap times, always check the status field. Laps completed under yellow flags, safety car, or VSC conditions will be slower and should not be compared directly to laps under status ‘1’ (track clear).

See Also

Build docs developers (and LLMs) love