How the challenge works
Lars plays every Trackmania map whose TMX ID is a prime number, in order, and has to beat the author time on each one. Every Twitch Prime sub gifted to him during the stream raises the target by one, so the community can keep the challenge alive: more primes means more maps to beat. With Amazon Prime that Prime sub is free once a month.
The latest statistics could not be loaded. Please try again.
Some coverage data is unavailable. Map durations are marked as uncertain.
Prime Buffer - How close to the end?
About this chart
The Prime Buffer is the recorded target minus the current prime index. At zero, the current map is the last one still to finish, unless more primes arrive.
Green means a comfortable buffer; yellow, orange and red show it getting tight. Temporary negative differences caused by delayed counter updates are displayed as zero. Grey vertical lines mark pauses or gaps between VODs.
Scroll or drag to zoom; click a data point to open the VOD.
The climb
About this chart
Three cumulative counters: maps played, prime IDs processed and primes counted. A constant slope means a steady pace.
The dashed line connects the first and last displayed “Maps played” points: it shows the average slope over that interval, including when days are filtered.
Scroll or drag to zoom; click a point on the maps or prime-ID line to open the VOD.
Forecast: where does this end?
How this forecast is calculated
The Void
Every stream day, and its longest map
About this table
Maps played, processed prime IDs, incoming primes and play time per stream day. Net is the change in the Prime Buffer: positive means it grew; negative means Lars caught up.
Median playtime and Longest map use measured durations of non-skipped maps. The total-row median is the median of the daily medians.
The highlighted overall longest map covers all days, even when the table is filtered.
Longest map links into the stream at that map; Full VOD opens the whole stream of that day from the start.
What 198 hours are
How to read these
The first row is measured: it comes out of this archive and out of nothing else. Personal bests are the last confirmed online times, which may have been set before or after the stream - so the winning runs are what his best laps add up to, not a stopwatch on the stream itself.
The second row is for scale, not for science. Every comparison names the record or duration it divides by; those change, our numbers do not. Nobody runs 98 marathons at world-record pace, and that is the point.
Both rows cover the whole challenge and ignore the day filter.
What the challenge says about itself.
For scale, not for science: the whole playtime of 197:53 h, set against records and everyday things from real life.
Detailed analysis
Explore played maps, Lars vs. Scrapie, pace, map types and mappers Everything the challenge left behind: the PB comparison and all detailed charts and statistics
Played Maps
What the default view shows
Shown by default: the last 15 maps he played, newest first - sort any column, or expand for all. Click a map for the VOD; use the type and difficulty selectors below to narrow the list.
Lars vs. Scrapie on prime maps
How the comparison works
Last confirmed online personal bests on the maps in this archive. These records may have been set before or after the stream. Each map UID counts once; only maps with two valid PBs decide the score.
On old maps played in the challenge today, Lars brings his current skill, game knowledge and training, while Scrapie may have set his PB years earlier. The comparison reflects their recorded times, not necessarily both players' current ability or the same stage of their training.
Gap vs. Scrapie = (Lars PB − Scrapie PB) / Scrapie PB. Negative means Lars is faster. The chart shows Lars above zero and Scrapie below, using square-root spacing to gently spread out small gaps. The Void is compressed into a marked window. Tooltips retain the exact gaps. This is not a historical rivalry timeline.
Search covers at most the first 1,000 leaderboard entries. Missing or unknown times never count as a loss. Failed refreshes keep an older confirmed PB and show its age.
Opponent: Scrapie98 on trackmania.io ↗.
Top styles are ranked by the lead in map wins (wins minus losses), using all shared PBs in the selected days. Table search and result filters do not change these rankings. A map with several Type tags counts once in each style; styles without a lead are omitted. Each score shows the named player's wins first.
Lars · Top 5 styles
Scrapie · Top 5 styles
The race: maps cleared vs. primes gifted
How the rates are averaged
Averaging over the surrounding hour keeps single maps from spiking the line. The Void is left out: the counters were caught up by hand there, which is neither a playing nor a gifting rate.
Both rates on one axis, averaged over the surrounding hour of play time.
Playtime per map
Which durations are in here
The same colours as the tag cloud further down. Only reliably measured durations are in here - a coverage gap falsifies the duration, and the duration is the whole statement of this chart.
Colour = the map's first TMX tag. Click a dot for the VOD. Log scale: every gridline doubles the playtime, so the two-minute crowd is not flattened by the hour-long maps.
Daily net progress, and Lars against his own average
What the three bars mean
Green, buffer grew: the community pulled ahead, more primes came in than maps were played. Red, Lars caught up: the end moved closer. Blue and orange: the day against Lars' overall average - maps played and maps per played hour, as percent deviation on the right axis. Zero means exactly average, and all bars share the zero line. Hover a day for the numbers.
How the buffer of maps still owed changed each stream day - and whether Lars was faster or slower than his usual self that day.
Where the pace is heading
Both rates as a running average over all stream days so far, with peak days above the 95th percentile left out. The faint dashed lines are the single days behind them. Left axis: maps per stream day. Right axis: maps per played hour.
Hourly Stream Activity
How to read the activity grids
Each column is a stream day, from oldest on the left to newest on the right. Rows show the first five hours of play time, starting with the first hour at the top. These are hours on the challenge clock, not times of day; pauses are excluded.
Primes in shows relevant counter increases per played hour, including adjustments for skipped maps. Maps played shows maps cleared per played hour. Partial hours are scaled to an hourly rate. Empty squares mean less than 15 minutes of play time or no usable measurement, not zero activity. Each square carries its own value; hover or tap one for the numbers behind it.
Closest call shows the lowest Prime Buffer reached in each hour. Lower values mean the challenge came closer to ending; zero means the last map was reached. Rate colours are capped at the 95th percentile so unusual hours do not hide the rest. The Void day is shown, but its bookkeeping increases are excluded from the prime scale and median.
The bottom row of each grid holds the whole day in one square: Day total counts every hour of that day, including the ones past the fifth row, and matches the numbers in the Days table. Under Closest call it is a Day low instead - buffer levels do not add up. Day totals carry their own colour scale, so a total is never compared to an hourly rate.
A crown marks the highest square of all stream days, a skull the lowest - never the best or worst hour of a single day. Squares showing the same number all get the mark. The Void day is left out of the prime marks for the same reason it is out of the prime scale.
One column per stream day · one square per played hour. Older days newer days
Scroll sideways to see earlier days. All three grids move together; use the arrow keys when a grid is focused.
Playtime by difficulty
What the bars measure
Median playtime across all reliable measurements, by TMX rating, in its natural order instead of sorted by duration. Hover a bar for the range behind the median.
👉 Click a bar or its name to filter the map list ↑
Maps per mapper
What the columns mean
Every played map grouped by its TMX author. Types are the tags across that mapper's maps, most frequent first. Difficulty is the mean TMX rating of the rated maps, in stars. The average playtime uses reliably measured durations only; a total marked ≥ also counts the lower bound of uncertain ones. Shown by default: the 15 mappers with the most maps - sort any column, search, or expand for all.
👉 Click a mapper to filter the map list ↑
Coming up next
Two addresses for this page: the plain larsprime.edur.ninja opens the preview as you last left it, and larsprime.edur.ninja/?spoiler-protection=on opens it with spoiler protection switched on. Either address remembers the choice like a click on the switch above.
How to read this table
These maps have not been played yet - the next prime map IDs from where Lars stands right now, straight from TMX. Turn on spoiler protection to hide map details while keeping IDs, UID copying and map links available. Opening an external map link can reveal its details. Rows marked gone no longer exist, the counter races through those in seconds. Click a map ID to open it on TMX. Lars PB is a time he already has on that map, read from the Nadeo leaderboard via trackmania.io - so the map is not new to him; a dash means no time on record, a "?" that the leaderboard was too long to scan. Diff WR-AT is WR minus author time: a negative value is faster; a positive value means the WR has not beaten the author time. The percentage below is relative to the author time. The colour indicates the margin: red at 0% or slower, orange at 5% faster, green at 10% faster or more. Missing times produce a dash; a zero author time has no percentage. Summary values are medians of the individual differences and percentages.
Royal update blocks
Trackmania's Royal update landed on June 12, 2021, so maps uploaded from that day on can use its new blocks: plastic surfaces (extreme acceleration at low speed, but the infamous “plastic bounce” when hit sideways or roof-first), driveable water (“water bounce”), and animated obstacles like rotating barriers and stompers. The timeline marks the first listed prime map using the Royal mode: 30727.