Motorsport telemetry
Telemetry that tells you exactly where the lap time goes.
Telemetry analysis for race teams, driver schools and karting. Open your MoTeC, AiM and iRacing files without the vendor's own software, and without your data ever leaving your machine.
Fuji Speedway. The layout is drawn from one real lap of GPS out of an AiM .xrk: 4,514 m measured along the driven line, against the 4,563 m centreline the circuit declares. The 9 turns come from curvature, and match exactly how Race Studio 3 segments them.
- measured by GPS on one driven lap of Fuji
- 4.514 m
- turns, identical to Race Studio 3
- 9
- logger formats supported
- 8
- bytes of telemetry sent to a server
- 0
On this page
- The problem
- FUJI
- Laps
- 15
The problem
You already have the data. What is missing is the answer.
- Vendor software only reads its own hardware
- Change logger and you lose your history. A team running MoTeC in one car and AiM in another works in two programs that do not talk to each other.
- The analysis is manual and slow
- Overlaying laps, finding the corner where the time goes and quantifying it is engineer work. Between sessions there is no time for it.
- A graph does not tell you what to change
- Seeing the speed trace is not the same as knowing you braked twelve metres early into T4 and that it costs you two tenths a lap.
- The product
- REF L15
- Best lap
- 2:04.975
The product
Screenshots of the real application, with real data. Every caption states what was measured.
The evidence
Five figures, and not one of them is an illustration. Each is the output of the same analysis that runs on your files, on a session that ships in this repository, drawn at full rate and captioned with what it measured.
- Evidence
- 5
- Invented
- 0
- Fixture
- Inferno86_Fuji_2248.xrk
Where the time changes hands
Two laps of the same driver at Fuji. The colour is not the accumulated gap: that would turn the whole back half of the lap red after one mistake at turn one. It is the change in the gap across a 50-metre sliding window, so red means time was lost here, and the windows sum back to the lap difference exactly.
Time lostTime gainedUnchanged
One corner, every lap
Turn 1 is the corner the analysis ranks first, and this is every comparable race lap through it over the analyser's own window: forty metres before the apex to twenty after. The reference is not the fastest lap of the session. It is this driver's best execution of this corner, which is a different lap, because a best lap is rarely the best version of every corner.
Best executionOther laps
One cursor, every channel
Speed, throttle and brake on a single shared distance axis, so a corner at 1 842 metres lands at the same place in every pane. This is the MoTeC i2 grammar rather than a redesign of it: an engineer already reads this shape, and making them learn a new one buys nothing.
Reference lapComparison
Why the peaks are measured first
The trace your browser receives is 500 points, and interpolating onto 500 points does not preserve a maximum. So every extreme is measured on the full-rate data inside the analysis, before anything is drawn. This is that difference, on one lap.
The relief, with its own noise
GPS resolves height two to three times worse than position, so this profile is an average over the session and the receiver's residual scatter is drawn around it at true scale. The band is wider than several real undulations. That is the honest picture, and it is why no claim on this site rests on a single altitude reading.
What nobody else does
Three decisions you can see in the number.
These are not opinions about the product. They are measurements taken on real files that live in the repository, and anyone can repeat them.
- Extremes are measured before anything is drawn
- The trace that reaches the browser is reduced to 500 points, and there the peak longitudinal G reads 0.60 g against a true 1.03 g. Interpolation does not preserve a maximum. So every extreme is measured on the full-rate data in the analysis, never on what gets drawn.
- 42 %
- Corners come from physics, not from a fit
- Against the Race Studio 3 segmentation on three circuits: 10, 9 and 9 turns against a true 10, 9 and 9, with the left-right order exact on all three. The test requires the result to be a subsequence of the truth, so a corner can never be invented.
- 10 / 9 / 9
- What cannot be measured is said out loud
- There is no off-track detection. Measured over eleven laps at Fuji, 88 % of the samples reading as “outside” were on straights, because onboard GPS drifts by as much as the width of the asphalt. Rather than invent it, the measured drift is published beside the room you had.
- 88 %
- Privacy
- 0 bytes
Your data
Your data never leaves your machine.
Wild Telemetry is a desktop application, not a cloud service. The sessions you import, your setups, your team's formulas and your history all live on your own computer. There is no server receiving them, because none exists.
- Sessions are stored in your user folder, not on a server.
- The AI runs locally; if you prefer your own provider, the key stays on the device.
- Your team's formulas and maths channels are its intellectual property and are never transmitted.
- If your licence lapses the app becomes read-only: everything you already imported stays open. It never locks you out of your own data.
- Comparison
- i2 · RS3
The full comparison, including the rows we lose.
This table comes from docs/competitive-gap-analysis.md, which is checked against the code rather than against marketing material. The gaps are here because they are real.
| Capability | MoTeC i2 | Race Studio 3 | Wild |
|---|---|---|---|
| Multi-channel time / distance overlay | yes | yes | yes |
| Synchronised cursor across panes | yes | yes | yes |
| GPS track map | yes | yes | yes |
| Time gain / loss channel | yes | yes | yes |
| Maths / calculated channels | yes | yes | yes |
| Theoretical ideal lap | yes | yes | yes |
| FFT | yes | yes | partial |
| Channel report (min / max / average) | yes | yes | yes |
| Suspension analysis | yes | yes | yes |
| Saved worksheets and layouts | yes | yes | yes |
| Video sync | yes | yes | yes |
| Reads other vendors' files | partial | no | yes |
| Tyre degradation by regression | no | no | yes |
| Race strategy simulator | no | no | yes |
| AI narration grounded in real numbers | no | no | yes |
i2 Standard is free with MoTeC hardware; i2 Pro is unlocked by a licence bought through a dealer. Race Studio 3 reads AiM hardware.
- Start
- .drk .xrk .ld
Start
Three steps, and we do the middle one.
You do not need to install anything to find out whether this is useful to you.
You send us a file
A .drk, an .xrk or an .ld from one of your own runs. Telling us the logger is enough; if we cannot open it, we say so and that is the end of it.
We analyse it
On your data, not on a demo. Out comes the per-corner report: where the time goes, how much, and which of your own laps it is being compared against.
We go through it
You get it back as a PDF and, if you want, twenty minutes on a call to talk it over. No commitment and nothing to install.
We send back the analysis, done on your own data.
Every request is answered by hand. Tell us which logger you use and we will confirm whether we can open your files before you install anything.
- Questions