Join the Discord! →

Join hundreds of racers just like you! We love to help answer questions and race together.


How to Show Telemtry in Iracing

Learn how to show telemtry in iRacing with quick, actionable steps for iRacing drivers. Get live and replay telemetry working fast — firewall, ports, and viewer checks.

If you want to know how to show telemtry in iracing, the short answer is: run a telemetry viewer and let it read iRacing’s live feed or replay files. You’re in the right place to fix it fast — follow the steps below.

Quick Answer — how to show telemtry in iracing

iRacing broadcasts telemetry that external apps can read live (or you can open session replay files). Install a telemetry viewer (VRS, Z1, MoTeC, etc.), run it before or during your session, set it to listen (usually UDP port 32000 or “auto”), and allow it through your firewall. For replay data, open the session replay in the viewer or export the replay.

What’s really going on

Telemetry is the raw car data: throttle, brake, steering, speed, gear, suspension, etc. iRacing provides that data live over the network (UDP) and saves it in session/replay files. iRacing itself does not draw advanced telemetry graphs on screen — you need a telemetry app or dashboard to view that data live or analyze replays. Most problems come from the viewer not listening, firewall blocking data, or using the wrong file/source.

Step-by-step fix

  1. Pick a telemetry viewer. Popular choices: Virtual Racing School (VRS), Z1 Dashboard, MoTeC i2, Atlas/Telemetry Tool or third-party dashboards.
  2. Start the viewer on the same PC (simplest). Set it to “listen” or “receive” telemetry — use UDP port 32000 or “auto” if available.
  3. Start iRacing and join a session. The viewer should populate with live data immediately. If nothing appears, quit both apps and relaunch the viewer first, then iRacing.
  4. Check firewall and antivirus. Allow the viewer and iRacing through Windows Firewall. If the apps are on different machines, ensure both are on the same local network.
  5. For replay telemetry: save your session replay in iRacing (My Sessions → Watch Replay), then open the replay file in your telemetry app or use the viewer’s “open replay” option.

Extra tips / checklist

  • Default UDP port: many apps use port 32000. If you change ports in the viewer, match them on the receiving app.
  • Same-machine rule: running viewer and iRacing on the same PC avoids network issues.
  • Run as admin if the viewer can’t bind to the port.
  • If you see garbled values, try “localhost” or 127.0.0.1 in the viewer instead of the PC name.
  • Replay troubleshooting: make sure the replay file is fully saved (exit session) before opening it.

FAQs

Q: Do I need to enable telemetry in iRacing settings?
A: No menu toggle is usually required — iRacing broadcasts telemetry by default. Just run a viewer to listen for it. Check your firewall if it’s blocked.

Q: Which viewers work with iRacing?
A: VRS, Z1 Dashboard, MoTeC i2, Atlas, and many others. Pick one and follow its setup guide for iRacing.

Q: Telemetry still not showing — what now?
A: Close both apps, allow them through your firewall, run the viewer first, then start iRacing. Try localhost/127.0.0.1 and verify port 32000.

Q: Can I record telemetry for later analysis?
A: Yes. Most viewers can read replay files or log telemetry to disk for post-session analysis.

Short wrap-up

Showing telemetry in iRacing usually takes two things: a telemetry viewer and an allowed network feed. Install a viewer, let it listen (port 32000 or auto), check firewall, and either watch live or open your replay. Next session, try one corner and verify values — then use the data to improve.