SimHub Integration

Every lap, captured.
On the right profile.

Live SimHub telemetry into every member profile — lap times, sector splits, fuel burn, top and average speed, tire compound, plus the car, track, session type and weather it was driven in. No clipboards. No screenshots. No retyping times off a sim screen.

Works with every sim SimHub supports — ACC, iRacing, Automobilista, rFactor, and more.

GTLane plugin running inside SimHub on a sim rig
GTLane plugin · SimHub
The problem

Lap times live
on the sim screen.

A driver puts in their session, walks out, and everything they did stays trapped on the rig — best lap on the in-game leaderboard, sectors lost to a session reset, fuel and tires nowhere on paper. The next time they come in, none of it is on their profile.

The workarounds are worse. Phone photos of the timing screen. A staff member typing times into a spreadsheet between sessions. A lounge TV showing yesterday’s best from a CSV someone exported manually. Half the data is missing and the other half is wrong by the time it gets stored.

The GTLane SimHub plugin pulls every lap and every session straight from the telemetry the sim is already emitting. Member profiles, leaderboards, and analytics all run off the same source of truth — captured automatically, per rig, with no one in the loop.

What a manual workflow can't do

  • Capture every lap time and sector split automatically
  • Tag invalid laps so they stay out of personal bests
  • Record fuel, top speed, average speed, and tire compound per lap
  • Stamp each session with car, track, type, and weather context
  • Put every stint on the driver’s member profile in real time
How it works

From the telemetry bus
to the member profile.

01

SimHub runs alongside the sim

Drop the GTLane plugin into SimHub on each rig. It listens to the same telemetry SimHub already reads from Assetto Corsa Competizione, iRacing, Automobilista, rFactor, and the rest — no extra game integration needed.

02

Session start fires once

On the first frame of every session GTLane captures the player, car, track, session type, lap total, and weather. The stint is anchored on a member profile before the green light even drops.

03

Each lap streams to the profile

As laps complete, time, sectors, validity, fuel, speed, and tire compound stream up in real time. The member sees their history grow live; staff sees engagement per driver instead of just bookings.

Setup

Plug it in,
start driving.

Seven small steps the first time you set up a rig. After that, every lap from every member streams to GTLane automatically.

  1. 01

    Download the free plugin

    Grab the GTLane plugin from our download page — no account or license key needed for the download itself.

    Download Plugin
  2. 02

    Move plugin to the SimHub folder

    Copy the plugin into your SimHub install directory. SimHub auto-discovers plugins from this folder on next start.

    C:\Program Files (x86)\SimHub

  3. 03

    Restart SimHub

    Close SimHub if it is running and start it again so it picks up the new plugin assembly.

  4. 04

    Enable the plugin in SimHub

    Open the SimHub plugin list and flip the GTLane toggle on. SimHub will load the plugin and show its panel on the next refresh.

  5. 05

    Generate an API key on GTLane

    Log in to your GTLane org, head to API keys, and create one for this rig. Each rig should ideally get its own key so usage is attributable per simulator.

  6. 06

    Paste the key into the plugin

    Open the GTLane panel inside SimHub and paste the API key into the field. The plugin stores it locally and reuses it across SimHub restarts.

  7. 07

    Send a Ping to confirm

    Click the Ping button in the plugin. If the response shows your API key owner and organization name, the integration is live — laps will stream from your next session.

That's it.

If the Ping response shows your API key owner and organization, the integration is live. Just drive — every lap, sector, fuel reading, top speed, and condition lands on your GTLane profile automatically.

What's included

Everything telemetry
captures for you.

Every lap, every sector

Lap number, total lap time, and sector 1 / 2 / 3 splits stream in from SimHub the moment they cross the line — plus a validity flag so cut laps are tagged and excluded from personal bests automatically.

Fuel, speed, and tire compound

Fuel burn per lap, top speed, average speed, and the tire compound the lap was set on. The numbers drivers actually argue about over the lounge bar — captured per lap with no clipboard and no manual entry.

Session context, captured once

On the first frame of every session GTLane records who was driving, the car model and class, the track, the session type, and total or remaining laps. You always know what was driven, by whom, where — independent of whether any lap was completed.

Weather in the data, not the memory

Air temp, road temp, and rain density are stamped onto the session at the start. A 1:42 in the dry and a 1:42 in the wet stop looking like the same lap — both in the member profile and in your leaderboards.

Straight into the member profile

Every stint a member drives — laps, sectors, fuel, speed, tires, car, track, conditions — lands on their profile. They see their full history across visits; you see real engagement data per member, not just bookings.

Feeds leaderboards and analytics

The same telemetry pushes into the leaderboard software and the driving analytics dashboard. Track records, car records, and member rankings update from real lap data — not from someone retyping times off a sim screen.

Data captured

The full picture,
per lap and per session.

Two layers of data come off every rig — a one-shot session header the moment a driver loads in, and a stream of lap records as each lap completes.

Per lap

  • Lap number
  • Lap time
  • Sector 1 / 2 / 3 splits
  • Valid / invalid flag
  • Fuel used (litres)
  • Top speed (km/h)
  • Average speed (km/h)
  • Tire compound

Per session

  • Player name
  • Game title
  • Car model, ID, and class
  • Track name
  • Session type
  • Total / remaining laps
  • Air and road temperature
  • Rain density
Comparison

Real telemetry,
not screenshots.

Manual Tracking Screenshots & CSVs GTLane
Lap times captured automatically per rig Manual
Sector 1 / 2 / 3 splits stored per lap
Fuel, speed, and tire compound per lap
Car, track, and weather context per session ManualManual
Invalid laps tagged and excluded from PBs Manual
Every lap lands in the driver’s member profile
Pit-stop pricing

One hour of rental.
Per rig. Per month.

Whatever you charge for one hour on a sim — that's your monthly fee per rig. No upfront payment. No setup fees. The math couldn't be simpler.

Your monthly bill — calculator

Rigs
×
$
Your hourly rate
=
$120 / month
Hourly rate × rigs equals your monthly bill. Same simple formula whether you run 2 rigs or 20.

No upfront payment

Start today. We bill you next month.

No setup fees

Self-guided onboarding gets you live in 24h.

Cancel anytime

Month-to-month. No long contracts.

FAQ

Frequently asked questions

Which sims does the SimHub integration support?
Anything SimHub already reads telemetry from. That covers Assetto Corsa, Assetto Corsa Competizione, iRacing, Automobilista 2, rFactor 2, Le Mans Ultimate, RaceRoom, F1, Project CARS, and the rest of the SimHub-supported list. If SimHub can see the telemetry, GTLane can capture it.
What data is captured per lap?
Lap number, lap time, sector 1 / 2 / 3 splits, a valid-or-invalid flag, fuel used in litres, top speed and average speed in km/h, and the tire compound the lap was set on. Each lap is timestamped and tied to the active session.
What data is captured per session?
On the first frame of every session GTLane records the player name, game, car model and class, car ID, track, session type, total laps, remaining laps, air temperature, road temperature, and rain density. That context anchors the stint even if the driver never finishes a clean lap.
How does the data end up on a member’s profile?
Each rig is tied to your venue. When a member checks in for a booking, the session telemetry from that rig is attached to their member profile — laps, sectors, fuel, speed, tires, plus the car, track, and weather context. They see their full history across visits; you see real engagement data per driver.
What happens if SimHub or the network drops mid-session?
Laps are buffered locally by the SimHub plugin and synced when the connection returns. A short network blip does not cost you a stint — once SimHub reconnects, the missed laps are uploaded with their original timestamps and slot onto the member profile in order.
Do I need a separate license for SimHub?
SimHub is free for personal use and has a low-cost license for commercial venues — that license is between you and the SimHub author. GTLane reads the data SimHub already collects, so there is no separate per-rig fee from us for the integration.

Every stint,
on the right profile.

Try the live demo to see member profiles built from real lap telemetry — or contact us to launch on your own branded gtlane.com subdomain in 2-5 business days.