Discover Events
Find road, trail, ultra and triathlon races by place, date, distance and registration status.
Discover running, trail, ultra and triathlon events across Europe. Plan A-, B- and C-races with countdowns, training blocks and realistic recovery windows.
Find road, trail, ultra and triathlon races by place, date, distance and registration status.
Compare race dates and avoid stacking key events too close together.
Organize A-, B- and C-races, track training blocks and keep your calendar realistic.
Search, filter and open event details while the map and list stay synchronized.
Keep the next important start date, priority and location visible.
Review race load, sport mix, spacing and monthly density in one place.
Spot useful build phases and tight recovery gaps before they surprise you.
Discover events that fit your current distance, sport and timing profile.
Submit races with an official website so they can be reviewed before they appear on the map.
Event Wiki is the knowledge area for verified detail information on endurance events, from course profile and cut-off times to race guide links, registration details and planning notes.
Route character, surface, aid stations, pacers and PB potential will be shown in a consistent structure.
Race-day limits, intermediate cut-offs and triathlon check-in windows will be separated from generic notes.
Elevation gain, terrain, wind, heat, technical trails or open-water conditions will be marked when verified.
Start documents, official race guide links, bag drop and medical information will stay close to the event facts.
Entry status, price phases, lottery rules, sold-out notes and official registration links will remain source-based.
Event-specific atmosphere, target group, logistics and preparation notes will be added only when they can be checked.
Der bestehende Planner bleibt erhalten und ist jetzt als eigener Plattformbereich erreichbar. Events können aus Discovery und Eventdetails heraus hinzugefügt werden.
Der Planner zeigt gespeicherte Events, Countdown, Prioritäten, Notizen, Kalender und Training Blocks.
Wenn du nicht eingeloggt bist, bekommst du eine klare Login-Aufforderung statt eines stillen Fehlers.
Akzeptierte Planner-Aktionen verwenden weiterhin die bestehende Favoriten- und Supabase-Synchronisierung.
Community is planned as a practical layer around events: questions and answers, rideshares, shared lodging, race reports, organizer news and finding people for training or race day.
Ask event-specific questions about course, cut-off, bib pickup, heat, waves or logistics.
Coordinate travel with athletes heading to the same start area or city.
Prepare shared hotel, apartment or rental car plans around crowded race weekends.
Collect practical experience from athletes who already raced the event.
Keep relevant organizer news close to the event instead of spreading it across channels.
Find people preparing for the same distance, event month or race-day goal.
Manage your login details and track your race achievements.
This is the email connected to your Sport Event Map account.
Email changes may require confirmation through a link sent by Supabase.
Sign out on this device. Your saved races and season plan stay connected to your account.
Organize A-, B- and C-races, track spacing and keep your training calendar realistic.
Your saved races as a month-by-month season plan with spacing and priority context.
The download is an .ics calendar file, the standard format used by Apple Calendar, Outlook and Google Calendar import.
Season Balance describes how demanding your saved race calendar looks overall. It combines race volume, race difficulty, priorities and tight recovery windows into one simple planning signal.
Shorter races count as lighter load. Marathons, ultras, 70.3 races and full-distance triathlons increase the planning load.
More saved races increase the load. A busy calendar is not automatically bad, but it needs more careful spacing.
A-races count more strongly than B-, C- or training races, because they usually need more preparation and recovery focus.
If two races are closer together than the recommended recovery window, Season Balance becomes more demanding.
Use Season Balance as a quick reality check: if it says demanding, review whether every race belongs in your season or whether some should stay as C-races or training events.
Race Mix shows what kind of season you are building. It highlights your dominant sport type and the distances that appear most often in your plan.
A clear dominant sport can be useful when you are preparing for one main goal, such as a marathon or triathlon season.
Running, triathlon and ultra events are separated so you can quickly see whether your calendar fits your actual training focus.
Repeated distances show what kind of preparation your season demands, for example shorter races, marathons, ultras or triathlon formats.
Use Race Mix as a quick reality check. If your plan contains very different race types, make sure your training blocks still match the most important goals.
Training Blocks show the time between two upcoming planned races. Past races are not included, so this stays focused on the season ahead.
Very tight spacing. This is usually more recovery and logistics than meaningful training.
A short block. Useful for recovery, light sharpening or maintaining fitness.
A strong planning window. Often enough time for a focused training phase between races.
A longer build phase. Good for base work, a new focus block or preparing for an A-race.
The goal is not to fill every gap. Good seasons usually alternate races, recovery and focused build phases.
The Season Score is a planning signal from 0 to 100. It is not a medical training metric. It helps you spot whether your race calendar looks realistic, balanced and recoverable.
Races scheduled too closely together reduce the score. Larger races such as marathons, ultras and triathlons need more recovery time than shorter events.
Too many A-races lower the score. A strong season usually has a few main goals and supporting B- or C-races around them.
If too many races sit in the same month, the score drops. The planner rewards a calendar that spreads load more evenly.
Very short gaps are risky. Extremely long gaps are only lightly marked, because they may still be useful training blocks.
Use the score as a decision helper: review tight recovery gaps, reduce unnecessary A-races and keep your season focused on the races that matter most.
The platform is ready to use, but event data and planning workflows are still being refined with beta feedback.
Help improve the closed beta. Please keep personal or sensitive information out of your message.
Found a missing event or want to send more context? Use this form or email feedback@[your-domain].com.
Review submissions, monitor data quality and respond to beta feedback.
Loading submissions...
Read-only review of the curated CSV. Changes continue through the import workflow.
Only real issues appear here: official website, date, coordinates, source, duplicates and stale checks.
Bearbeite strukturierte Detaildaten, Quellen und FAQ für die statisch generierten Event-Guides.
Waehle ein Event, um Detaildaten zu bearbeiten.
Starte einen Tool-Job für fehlende Detaildaten. Ergebnisse landen als Review-Vorschläge und werden nie automatisch public.
npm run research:event-knowledge -- --scope high --limit 10
Research jobs run through the local tool script. Refresh after the job completes to review proposals.
Prüfe fehlende Knowledge-Daten, öffne Research Tasks und übernimm nur geprüfte Kandidaten in Supabase.
Run npm run audit:event-knowledge and npm run enrich:event-knowledge to create the review queue.
New events should enter the pending review list first. Approve only events with official websites, current dates, coordinates, sport, distance and a clear source.
Preview first, then save as pending. Imported rows still require admin review before they become public.
Load a validated staging CSV, review the rows, then save them to Supabase as non-public staging events.
Choose a file like data/imports/staging/germany-road-running-batch-01.staging.csv.
Use this area as the manual checklist before adding large event batches to the map.
Understand whether testers discover events, return to the product and use the Season Planner.
Last 30 days
Do testers come back after the first visit?
What people search for and whether searches lead to event opens.
Which events attract attention and convert into planning intent.
Whether testers move from discovery into real season planning.
Quality of beta feedback and open product issues.
Filter beta feedback and update its internal review status.
Loading feedback...