What WikiRacing Has in Common With Speedrunning Culture

Published on 2026-09-20

By Chris

Independent developer of WikiRacing. About

Watch enough speedrunning streams and you start noticing a pattern: someone finishes a 20-year-old platformer in nine minutes, the chat goes wild over four seconds shaved off a personal best, and somewhere in the corner of the screen a leaderboard quietly updates. None of that vocabulary is unique to video games. Most of it also describes what happens on WikiRacing's own pair leaderboards every day.

I didn't set out to build a speedrunning tool. WikiRacing started as a way to race a friend from one Wikipedia article to another. But the closer this thing got to a full leaderboard-and-personal-best system, the more it started borrowing the shape of a much older hobby.

What "speedrunning" actually means

For anyone who's never spent an evening on Twitch's speedrunning tab: a speedrun is a full playthrough of a game done as fast as possible, usually toward a specific, agreed-upon goal ("Any%" means beat the game by any means necessary, "100%" means collect everything along the way). Communities built entire sites like speedrun.com around verifying and ranking these runs, category by category, game by game. The appeal isn't really about the game being replayed. It's about a fixed, known system getting pushed to its absolute limit, one shaved second at a time.

That last part is the piece WikiRacing actually inherited, whether or not that was ever the plan.

The pair leaderboard is a personal-best board with a different game attached

Every start-to-end pair in WikiRacing has its own leaderboard, ranked by clicks first and time second, and only a player's single best attempt on that exact pair ever counts. That's speedrun.com's category-and-personal-best structure with a Wikipedia article standing in for a game. Beat your own record on Bread to Wheat and nothing else moves. Beat someone else's stored run and you show up on a board a stranger will eventually see and try to beat back. Three podium finishes automatically become a tracked "Records" stat on a profile, the same quiet trophy case a speedrunner's own profile page keeps.

The campaign is the closest thing to a fixed, memorizable route

Real speedrunning has "the route": a specific, rehearsed sequence of inputs a runner has drilled dozens of times, discovered collectively by a community picking a game apart over years. WikiRacing's 300-level campaign is the one mode built around something similar. Every player eventually races the exact same pair at level 1 (Bread to Wheat), and a player who's done it before genuinely does have a route memorized, the same wheat-related paragraph, the same one or two links, learned the first time and reused every time after.

What speedrunning can't quite give you, though, is a route that changes underneath you without warning. A game's code doesn't get edited by volunteers overnight. A Wikipedia article does. The path a player memorized for a campaign level six months ago might not be the fastest path today, or might not exist at all if an editor restructured the article since. That's a strange, honest wrinkle: WikiRacing's "game" is a living document, not a fixed ROM, so a route can quietly go stale in a way no NES cartridge ever will.

Themed challenges are categories, the daily is a seeded race

Science, History, Pop Culture, Gaming, Streamers: WikiRacing's five themed pools work like speedrunning categories. They're not different games, just different constraints layered onto the same underlying system, and each one gets its own separate leaderboard so a Science-category time never gets compared against a History one. The daily challenge does something a lot of competitive games have also landed on independently: a single shared pair, the same for every player, resetting at 00:00 UTC. It's the same logic behind a seeded daily puzzle or a synchronized race lobby, minus the lobby. Everyone gets exactly the same start and target, so nobody can claim a lucky pair made their time.

Replays are VODs, minus the commentary

The part of speedrunning culture that never quite translates into words is how much of it happens through watching, not playing. A serious runner studies other people's videos frame by frame looking for a faster trick. WikiRacing's replay feature is a smaller, quieter version of the exact same habit: a numbered step list of someone else's actual path, jumpable to any point, sitting right there on the activity feed for anyone to open. I've caught myself doing this more than once, clicking into a stranger's replay after a fast time showed up on a pair leaderboard, not to copy it exactly but just to see which hub article they hit that I'd walked straight past.

That's the honest difference between the two hobbies, if there is one. A speedrun VOD is a performance, edited and narrated for an audience. A WikiRacing replay is closer to a receipt: here's exactly what happened, decide for yourself if it's interesting.

Even the badge names speak the language

One of WikiRacing's twelve badges is called Speedrunner. Sub-2-second, one-click wins get you there, and the fact that name got picked at all says something about which culture this whole system quietly grew out of. Lightning, Sniper, and Perfectionist sit alongside it, all four rewarding a single blisteringly fast game rather than a long career. Then there's a separate ladder entirely: On Fire, Veteran, Centurion, tracking raw volume instead, 10, 50, 100 games finished, closer to an hours-played achievement than a speed one. Champion, tied to crossing 1,500 ELO, is the only badge that can actually be lost again if a rating slips back below the line, the one honest nod to the fact that a record and a rank aren't quite the same claim.

Racing a friend live is the closest thing to a race category

Some speedrunning communities run actual synchronized races, two or more runners starting the same game at the same signal, first to the credits wins. WikiRacing's casual multiplayer mode is built on that same shape at a much smaller scale: a shared room, a start signal broadcast to everyone at once, and a live HUD showing exactly how far ahead or behind you are while it's still happening. Ranked duels tighten that further into the strict 1v1 version, the one where only the outcome, not the specific route either player took, ends up mattering enough to move a rating.

The part that doesn't map cleanly

Where the comparison genuinely breaks down is glitches. A huge share of real speedrunning culture is built around finding and exploiting bugs the developers never intended, clipping through walls, skipping cutscenes, breaking the game on purpose to go faster. WikiRacing has nothing equivalent, and can't, really: the "rules" are just Wikipedia's own internal-link structure, and there's no wall to clip through, only articles that are or aren't connected. The closest thing to a discovered trick is a hub article nobody thought to check, and even that isn't a bug. It's just Wikipedia being Wikipedia, dense with connections in places you wouldn't expect.

Maybe that's the actual throughline. Both hobbies are really about the same instinct: take a big, fixed, slightly indifferent system, whether it's a 30-year-old game's code or a 6-million-article encyclopedia, and find the shortest, weirdest, most satisfying way through it. One just happens to update its own rulebook while you're not looking.

WikiRacing →