MyLMU Logo
Documentation
Sign inGet Started
AnalyticsDeeper Analytics
Getting Started
Product Overview
MyLMU App
MyLMU Telemetry
MyLMU Coach (AI)
MyLMU Sync Agent
Sessions
Getting Started
Session History
Session Details
Import
Sync Agent
Analytics
Overall AnalyticsLap Times ExplorerDeeper AnalyticsTrack Library
Milestones
MyLMU Telemetry
Getting Started
File Library
Telemetry Viewer
Leaderboard
Teams
Plans & Limits
AI Coach
Troubleshooting
MyLMU Sync Agent
Getting Started
Sessions Sync
Telemetry Sync
Daily Usage
Troubleshooting
Privacy & Security
MyLMU Coach (AI)
Getting Started
Coaching Modes
Coach Features
Troubleshooting
Privacy & Terms
Teams
Getting Started
Team Dashboard
Sharing with Your Team
Discord & Alerts
Team Calendar
Profile
Plans & Limits
Rankings
Getting Started
Skill & Discipline
Placement & Tiers
Community Leaderboard
Driver Profiles
Sessions & Imports
Notifications
Plans & Limits
Troubleshooting
Community
Getting Started
Activity
Leaderboards
Friends
Friend Groups
Lap Records
Track & Car Stats
Weekly Meta
Overall Community Stats
Feature Requests
Privacy
Troubleshooting
Misc
Opening Settings
Account & Data Lifecycle
Profile
Notifications
Appearance
Feedback
Using the Documentation
DocsSessionsAnalyticsDeeper Analytics

Deeper Analytics

Technical benchmarks for a specific track and car — tyre wear, consumption, top speed, and community comparison.

Last updated July 14, 2026

Summarize this page with AI

The Deeper Analytics tab provides advanced technical benchmarks for a specific track + car combination, compared against community data where available.

For lap-time trends, reference pace, and consistency across your full history, use Lap Times Explorer on the Overall tab instead.

Getting started

  1. Open Dashboard → Analytics
  2. Switch to the Deeper Analytics tab
  3. Select a track and car
  4. Set View (Races / Qualifying / Practice) and Mode (Online / Offline)
  5. Choose a metric — Tyre Wear, Consumption, or Top Speed

Until you pick both a track and car, an empty state prompts you to make selections.

Metrics

Deeper Analytics has three metric tabs:

MetricWhat it shows
Tyre WearAverage wear per lap by corner vs community
ConsumptionFuel and virtual energy use per lap vs community
Top SpeedAverage and session maximum speeds vs community

Tyre Wear

  • Per-corner comparison cards: Front Left, Front Right, Rear Left, Rear Right (% wear per lap)
  • Tyre compound selector when multiple compounds were used in your data
  • Handling Balance card — axle balance (front/rear) and lateral balance (left/right) vs community, with alignment indicator

Consumption

  • Fuel — average % of tank used per lap, with estimated volume per lap based on car tank capacity
  • Virtual Energy — average VE % used per lap
  • Fuel Calculator — plan race strategy from benchmarks:
    • Total race time and average lap time inputs
    • Fuel and energy per lap (your average or community)
    • Tank capacity, stint laps, pit stops
    • Optional 2x consumption multiplier
    • Total, per-stint, and final fuel/energy estimates

Top Speed

  • Avg. Max Speed and Session Max vs community
  • Weekly Performance Trend chart (community data) when enough historical records exist — shows how community top speeds evolved over recent weeks

Community comparison

Where enough data exists, your averages are plotted against community benchmarks for the same track, car, view, and mode:

  • Your Average vs Community Average on each metric card
  • Sample Size — community lap count in the context bar
  • Your Data — your lap count contributing to the average
  • Low confidence badge when community sample size is below 15 laps

Limited data

If insufficient community records exist for a track/car combo, you will see a Limited Competitive Data notice. Import and race more sessions in that combination to unlock benchmarks. Offline mode uses a separate community dataset from online.

Data constraints

An info icon in the context bar lists which laps are excluded from aggregates:

  • Incomplete or invalid laps
  • Laps with driver swaps
  • Sessions with invalid fuel/wear data
  • Laps slower than 110% reference pace (Wet/Inter compounds excluded)

Driver swap and export gaps can skew fuel and wear numbers — see Driver Swaps & Data Gaps.

Tips

  • Deeper Analytics needs sufficient laps on a track/car combo
  • Online and Offline modes have separate community datasets
  • Link telemetry for corner-level detail beyond result XML
  • Ask MyLMU Coach to interpret trends on a specific session

Related

  • Lap Times Explorer
  • Overall Analytics
  • Driver Swaps & Data Gaps
  • MyLMU Coach (session mode)

Was this page helpful?

PreviousLap Times ExplorerNextTrack Library

On this page

  • Getting started
  • Metrics
  • Tyre Wear
  • Consumption
  • Top Speed
  • Community comparison
  • Limited data
  • Data constraints
  • Tips
  • Related

Was this page helpful?

Documentation

  • Getting started
  • Product overview
  • Sessions
  • MyLMU Telemetry
  • MyLMU Sync Agent
  • MyLMU Coach (AI)
  • Teams
  • Rankings
  • Community
  • Misc

Product

  • Open dashboard
  • Sync Agent
  • Contact
  • Pricing
  • Changelog
  • FAQs
  • Branding

Community

  • Instagram
  • Community forum
  • YouTube
  • X

© 2026 MyLMU

•Privacy Policy•Terms of Service•Cookie Policy