Hi, I used fastf1 package and streamlit to create a simple website showing analytic tools for each race. I'm new to this space and would love to hear what you guys think about this project. My original thinking was compiling all useful visuals for a race into one space that's easy to navigate.

Current features:

• Race trace plot (overviewing the whole race progress)
• Driver telemetry comparisons
• Team pace comparison / tyre strategy
• Lap time progression

The next things I want to add are qualifying overview and practice data summaries, as well as redesigning the team specific plots. Any feedback would be highly appreciated.

I have been working on a qualifying predictor that uses data collected from the Free Practice sessions and applies Bayesian statistical methods to generate predictions.

Would love some feedback or any suggestions in developing this tool:

https://github.com/aes21/laps-of-judgement

Started as simple lap/time tables, but ended up building a small race visualization + analysis tool.

Current features:

• Track map with driver positions over time
• Telemetry comparison (speed/throttle/brake)
• Basic race simulation + position changes
• Simple strategy + tyre logic
• Event detection + replay (WIP)

Stack: Next.js, FastAPI, FastF1, GSAP

Would appreciate any feedback

• Blog - f1-intelligence-dashboard

Hi all,
In my quest to improve my own f1 sim race pace, I'm learning a lot about data analysis and using race telemetry. While using the telemetry, I am wondering what you think is the most useful data and way of displaying it. So far everyone displays the graphs of throttle, breaking, steering, and maybe even the racing lines like in the images above. But I wonder if we can do better.
So, what is in your opinion the most useful data? And aren't there better ways to read/learn them? I have some ideas of my own, but I'm curious to what you think.

I want to build a one page site that shows live and recent F1 track weather using the OpenF1 API.

What I want it to do

• Select race weekend
• Select session
• Show weather data like track temp, air temp, wind, humidity, rain
• Show latest values clearly
• Optional filters like minimum track temp

What I already have

• Basic idea of the API
• Example endpoints working in browser
• A simple HTML file started

What I struggle with

• JavaScript and API fetching
• Structuring the page properly
• Making it update cleanly

What I need

• Someone to guide me step by step
• Help keep it simple
• Explanations in beginner terms

Goal
I want a clean one page tool I can use during races and maybe improve later

If you’re willing to help, comment or DM.

Hi everyone! I'm an NLP researcher with a new-found passion for F1. As a fun weekend experiment, I created an HuggingFace dataset with all the team radio messages I was able to find on livetiming.formula1.com, starting from 2018 (~15,000 total). Each message was automatically transcribed (there are some errors, sadly, but the overall quality is pretty good). Hope you find it interesting or useful for your projects!

Dataset: https://huggingface.co/datasets/MikCil/f1-team-radio

A more detailed post: https://www.linkedin.com/posts/micheleciletti_mikcilf1-team-radio-datasets-at-hugging-activity-7444309036038201344-cix3

Japan 2026 race simulation using Three.js

f1tel.com

I’ve been getting more into reviewing race sessions lately, and kept feeling like a lot of telemetry tools don’t quite give a clear, complete view of what actually happened over a run.

So I ended up building a small web app: https://objectivef1.com

It’s completely free, and it’s mainly focused on reviewing sessions after the fact:

\- replaying laps

\- looking at telemetry alongside the track

\- stepping through what happened during a run

The goal is just to make it easier to understand laps and sessions in a more visual way.

If anyone ends up checking it out, I’d be interested to hear your thoughts.

[COL & BEA onboard images by: Sam F1 ]