01
What you need
The console or PC and phone must be on a mutually reachable local network. A wired console and Wi-Fi phone are fine when the router permits LAN-to-WLAN traffic. Open Victory, choose F1 25, and note the phone’s local IPv4 address and listening port.
The default port is 20777. If you change it, use the same port in both F1 25 and Victory.
02
Configure F1 25
In F1 25, open Settings, then Telemetry Settings. Turn UDP Telemetry on. Set UDP IP Address to the phone’s local IPv4 address—not the router, public IP, or console address. Set UDP Port to 20777 unless both sides use another value. Select the UDP format or mode that matches the base game or 2026 Season Pack.
The flow is F1 25 console or PC → phone local IPv4 and port → Victory listener. Victory does not need a cloud relay for this local stream.
03
Verify the connection on track
Start an on-track session; menus may not send the full packet stream. Confirm that speed, gear, RPM, lap, tyre, or session values update in Victory. A connected network indicator without changing telemetry is not enough.
Once packets arrive, Victory can combine lap, telemetry, setup, session, weather, race-control, penalty, damage, tyre, ERS/DRS, and opponent-position data. Not every field is shown on every screen.
04
Troubleshoot in the right order
Recheck the phone IP after reconnecting to Wi-Fi. Confirm port values match. Grant local-network permission. Disable VPNs, guest Wi-Fi, client isolation, and restrictive firewall rules. Close another app that may already own the UDP port. On PC, verify F1 25 is sending through the active adapter.
If the 2026 Season Pack is enabled, verify the matching UDP mode. Finally restart the app, game, and network connection before changing several settings at once.
- Wrong destination IP is the most common failure.
- Phone IP addresses can change.
- Test while actively driving.
- Keep the same port on both sides.
