200+ Kilometres of data, heat, speed and real validation

On June 12th, the Vetkuro team joined Trackmasters at Slovakia Ring for another full day of real-world testing.

This time, it was not just about recording laps. It was about putting the next stage of Vetkuro under pressure: our test Renault Clio, one of the fastest circuits in Europe, more than 200 kilometres of track driving, a prototype of our new measurement device, and new features across the mobile and web platform.

That is exactly the kind of environment where a telemetry product either starts to make sense - or shows you what still needs work.

Slovakia Ring is fast, flowing and demanding. Long straights, high-speed corners and heavy braking zones make it a proper test for both driver and data system. For us, that matters.

If Vetkuro is going to help drivers understand where they gain and lose time, it has to work in real track-day conditions: heat, vibration, traffic, repeated sessions, changing pace, and imperfect circumstances. A clean lab test is useful, but it does not tell the whole story. A full day on track does.

Our Clio covered more than 200 kilometres during the event, giving us a large amount of real telemetry to analyse after the day. Every lap was another chance to validate how the system behaves when it is no longer just a prototype on a desk, but a tool used in a moving race car.

One of the most important parts of the day was testing the prototype of our new measurement device.

Over the last months, the device has been redesigned to become more reliable, more functional and better prepared for real motorsport use. The goal is simple: Vetkuro should not depend only on the limitations of a phone sensor. The hardware layer has to provide a stronger foundation for accurate telemetry, repeatable data and deeper analysis.

On track, that means validating things that are hard to simulate properly outside the car: signal stability, power behaviour, mounting, vibration, temperature, data consistency and the whole user flow around recording a session.

This is still development work, but the direction is clear. Vetkuro is becoming more than an app. It is becoming a full telemetry ecosystem.

In the mobile app, we are now focusing heavily on comparison. Lap time alone is useful, but it is only the beginning. The more important question is: how does your lap compare to another driver on the same track?

That is where Vetkuro is heading. We want users to be able to understand not only their own progress, but also how they compare with others driving the same layout. Different braking points, different minimum speeds, different lines, different throttle behaviour - these are the details that turn a lap time into a learning tool.

Track days are social by nature. Drivers talk in the paddock, compare times, ask where someone was faster, and try to understand what changed between one session and the next. Vetkuro should make that conversation more objective.

Instead of guessing, you should be able to open the app and see the difference.

The web application is where we are pushing the more advanced side of Vetkuro. A phone is great in the paddock. But when you want to properly analyse a session, compare laps, inspect a track map and look at telemetry traces in detail, a larger screen gives you much more space to work. During and after the Slovakia Ring test, we used the collected data to further refine the advanced session analysis flow. The goal is to make the web platform powerful enough for serious analysis, but still readable for drivers who do not want to become race engineers just to understand their own laps.

We do not want to simply show more charts. We want to help drivers answer better questions:

• Where did I lose time?
• Was the difference in braking, corner speed or exit?
• Was my faster lap actually better everywhere, or only in one sector?
• Can I repeat my best parts in one clean lap?

This is the direction we are building towards.

The biggest value of a day like this is not one single result. It is the combination of many small observations. Some things worked as expected. Some parts need refinement. Some ideas that looked good in development became even more important once we saw the data from real sessions. That is why these tests matter.

Motorsport is not a controlled environment. Cars get hot. Drivers make mistakes. Sessions are interrupted. The track changes. Phones lose battery. Hardware is exposed to vibration. Data is never as clean as you want it to be. A telemetry product has to handle that reality.

The Slovakia Ring test gave us another strong dataset, another round of practical feedback, and another step toward making Vetkuro more reliable, more useful and more focused on what drivers actually need.

For me, "Turn Data into Speed" is not just a tagline. It means taking everything that happens on track - position, speed, inputs, laps, sectors, comparisons, mistakes and improvements - and turning it into something a driver can use.

More than 200 kilometres, a faster and more demanding track. A redesigned device prototype. New mobile comparison features. Deeper web analysis - and most importantly: real data from real laps.

Pawel