To get a HUD in BeamNG.drive, turn on OutGauge in Options → Other → Protocols, point it at 127.0.0.1 on port 4444, and select BeamNG.drive in Horizon Labs. Horizon Labs listens on that port and draws speed, RPM, gear, pedals, fuel and the dashboard lights.
Steps
- In BeamNG.drive, open Options → Other → Protocols and switch on the OutGauge UDP protocol.
- Set the IP to
127.0.0.1(this PC), and use port4444if the game asks for one. - In Horizon Labs, open the Connection section of the settings and choose BeamNG.drive under Game. The host shows
127.0.0.1and the UDP port shows4444. They must match what you typed in the game. - Drive. Spawn a vehicle and the HUD moves.
BeamNG’s own documentation says where to switch the protocol on, but its page does not list the IP and port. The values above are the ones Horizon Labs expects by default; if you change the port, change it on both sides. See the BeamNG.drive page for the family summary.
What OutGauge is
OutGauge is a small UDP dashboard packet that BeamNG.drive sends once per frame to the address you give it. It uses the same layout as Live for Speed, so tools that read OutGauge from Live for Speed can read BeamNG.drive too. The BeamNG documentation notes that not every field of that layout is implemented. For a comparison with other methods, see How racing games send telemetry.
Fields OutGauge has
BeamNG’s documentation marks these as implemented, and Horizon Labs shows them:
- Engine
- Speed (km/h and mph), RPM, gear, turbo boost, engine temperature, oil temperature
- Inputs
- Throttle, brake, clutch, handbrake light
- Car
- Fuel level
- Lights
- Shift light, ABS, traction control
Horizon Labs’ list for BeamNG.drive matches this: speed, RPM, gear, throttle, brake, clutch, handbrake, boost, fuel, engine and oil temperature, shift light, ABS and TC.
Fields OutGauge lacks
- Laps and timing. There are no lap times, lap counts or positions in the packet. A BeamNG HUD cannot show a lap timer.
- Steering and g-forces. They are not part of OutGauge, so steering wheels and g-force widgets stay idle.
- Oil pressure. The documentation lists it as always zero, so Horizon Labs leaves it out.
- Car name. The car field is a fixed value, so a car-name widget would not tell vehicles apart.
- Pit-limiter light. The documentation lists it as not applicable.
When you design a HUD, build around the first list. In the Designer, fields BeamNG does not send are flagged when you bind a layer.
Check that data is arriving
In the Connection section, the Live status block shows the time of the last packet and a packet count for the UDP stream. Spawn a car and drive: if the count rises, OutGauge is reaching Horizon Labs, and any remaining issue is in the overlay or the OBS source.
Show it on screen or on stream
- On screen: run BeamNG.drive in borderless windowed mode so the overlay can sit on top. Exclusive fullscreen can hide it.
- On stream: set Display mode to OBS (browser source) or Both, then add a browser source with
http://127.0.0.1:8088/overlay/index.html. The steps are in Add a live telemetry HUD to OBS. The OBS source does not depend on the game’s window mode.
Troubleshooting
- Nothing moves. Check, in order: OutGauge is switched on in the game, the IP and port match Horizon Labs, and Game says BeamNG.drive. You need a vehicle spawned; the packet is sent per frame while driving.
- Port already in use. Horizon Labs’ Diagnostics tells you when another program is already listening on the port. Close that program, or pick a different port in both the game and Horizon Labs, then click Retry in Diagnostics.
- Gear looks off by one in another tool. OutGauge counts reverse as 0, neutral as 1 and first gear as 2. Horizon Labs converts this to reverse, neutral and 1 upwards for you.
- Another tool reads OutGauge. Two programs cannot normally listen on the same UDP port. Change the port, or close the other tool.
Good to know
Horizon Labs only reads the telemetry BeamNG.drive sends out. It does not inject into the game or edit its files. The game’s own terms still apply.
Sources: BeamNG.drive documentation: Protocols. Checked 2 November 2026.