Skip to content
F1 2025 Collector
Game Telemetry Setup

F1 2025 Telemetry Configuration

Configure every racing rig to send F1 25 UDPThe network protocol F1 25 uses to send telemetry packets to the collector. Each rig sends to the collector's IP address and its assigned UDP port. telemetry to the collector.

Find the collector address

The collector’s public IP address is shown in the status bar of the Collector page, next to a blue indicator.

  • Splunk Show or cloud deployment: use the public address shown in the status bar.
  • Local Docker: use the Docker host’s LAN address, not localhost, because the game runs on another computer.
  • Same computer: 127.0.0.1 can be used only when F1 25 and the collector run on the same machine.

Configure F1 25

On the racing rig:

  1. Launch F1 25.
  2. Open Game Options → Settings → Telemetry Settings.
  3. Configure:
SettingValue
UDP TelemetryOn
UDP Broadcast ModeOff
UDP IP AddressThe collector address
UDP Port20777 for RIG 1
UDP Send Rate10Hz
UDP Format2025
Your TelemetryRestricted
Show Online IDsOff

F1 25 telemetry settings

Multiple rigs

All rigs use the same collector address but a unique UDP port:

RigUDP port
RIG 120777
RIG 220778
RIG 320779
RIG 420780

Enable the required rig count under Config → General before testing, and deploy. For self-hosted Docker, publish the same UDP ports on the container.

Test the connection

  1. Turn on Master Control and confirm it reads SYSTEMS LIVE.
  2. Enter a driver name on the rig card.
  3. Start a Practice session in the game.
  4. Confirm the card moves to Telemetry live and shows speed, gear, lap, and track.
  5. Open Health and confirm the rig’s packet count increases.
  6. Confirm the card’s destination pills show ✓.

Use the displayed address

Cloud public addresses can change when an instance is replaced. Read the address from the status bar during event setup rather than copying it from an old runbook.

If data does not appear

  • Recheck the IP address and assigned port.
  • Confirm the collector host firewall allows inbound UDP.
  • Confirm the Docker or cloud port mapping exists.
  • Make sure UDP Broadcast Mode is Off.
  • Confirm Master Control is on and the rig count covers this rig.
  • Use Monitoring and Troubleshooting to separate UDP and destination problems.
Pit WallDashboards