Umalator is the tool most serious Uma Musume: Pretty Derby players end up using sooner or later, usually right after losing a Champions Meeting race they were sure they’d win. It’s a free, community built race simulator that lets you compare two Uma builds head to head before you commit resources to either one. This guide walks through what Umalator actually is, which version to use, how to run a simulation, how to read the results without getting confused by the graphs, and where the tool’s predictions can quietly mislead you.
Quick answer: Umalator is a free, community developed Uma Musume: Pretty Derby race simulator that lets players test character builds, stats, and skills under specific race conditions. It’s useful for comparing builds and checking mechanics, but its results shouldn’t be treated as a guarantee, because real races include positioning, multiple opponents, and other variables the simulator can’t perfectly reproduce.
What Is Umalator?
Umalator is an unofficial, fan made simulation tool built for Uma Musume: Pretty Derby. It isn’t published or endorsed by Cygames. It was built by community developers, most notably a contributor known as alpha123, with an actively maintained fork by Kachi Dev that many global players now treat as a go to reference. The tool takes two Uma builds, meaning their stats, skills, and aptitudes, and simulates a race between them to show which one performs better under a given set of conditions.
You may also see people refer to it as the Umalator app, but that’s a bit of a misnomer worth clearing up early. It’s better understood as a web based simulator you run in a browser rather than an official downloadable Uma Musume mobile application.
What Can Umalator Actually Do?
At its core, Umalator answers one question: if I run these two builds against each other on this track, which one wins more often, and why? It does this through a handful of connected features.
Race simulation. You input two builds, a track, and a distance, and the tool runs the matchup repeatedly to produce best, worst, and average finish outcomes rather than a single result.
Skill activation mapping. Umalator shows where along the track specific skills are likely to trigger, which is far more useful than just knowing a skill exists on a card.
Stamina and spurt analysis. The tool checks whether a build has enough stamina and guts to sustain its last spurt phase without running out of steam before the finish line.
Build comparison across scenarios. Rather than guessing whether a stat reallocation helps, you can test it directly and see the delta in outcomes.
Umalator Global: Which Version Should You Use?
This is where a lot of new users get stuck, and it’s worth sorting out before you touch a single stat field.
Umalator isn’t one single website. There are multiple actively maintained versions, and they don’t always behave identically because they pull from different snapshots of game data.
Umalator Global generally refers to a version built around the global release of Uma Musume, as opposed to the original Japanese server data. Since global and JP servers can differ in available skills, characters, and balance, running your build through a version tuned for the wrong server can quietly give you a misleading comparison.
Umalator GitHub is where the open source development actually happens, spread across a few community repositories and GitHub Pages projects rather than one central hub. The alpha123 fork provides the core simulator and its technical changelog, and that changelog is the most reliable way to confirm whether a given build fix or skill correction has actually landed yet. Kachi Dev’s fork is another important branch aimed specifically at global players and adds extra race analysis tooling on top of the base simulator.
Umalator V2 and older forks show up in search results because the tool has been reorganized more than once over time, and old bookmarks sometimes point to versions that are no longer actively maintained.
Moomoolator, hosted separately, is a current web based implementation that builds on the same community simulator work, crediting the original authors and the VFalator team, and it currently adds its own controls such as spot struggle simulation, lane movement, dueling, and wit checks.
The practical takeaway: before you trust a result, check that the version you’re using reflects the current game data for your server. A simulator running on stale skill or stat data will quietly give you wrong answers that look perfectly confident.
Umalator Global vs Moomoolator vs Other Forks
| Version | Best for | Main advantage |
|---|---|---|
| Umalator Global (alpha123) | Global players wanting the core simulator | Direct changelog, closest to the original tool |
| Kachi Dev fork | Global players who want deeper race analysis | Extra analysis tooling layered on the base simulator |
| Moomoolator | Players who want more granular race controls | Adds spot struggle, lane movement, dueling, and wit checks |
None of these is universally “the best.” They’re different implementations of the same underlying idea, and which one suits you depends on whether you want a straightforward comparison tool or deeper race mechanics control.
How to Use Umalator
Once you’re on a maintained version, the actual workflow is fairly linear.
- Pick your first Uma build. Enter the character’s base stats: speed, stamina, power, guts, and wisdom, along with distance and surface aptitude.
- Select the race and track. Distance and track type change which stats and skills matter most, so this isn’t a step to rush through.
- Add skills to the build. Include the actual skills on the card you’re testing, not a theoretical ideal loadout.
- Repeat steps one through three for the second build. Umalator is fundamentally a comparison tool, so you need two builds to get a meaningful result.
- Run the simulation. The tool will process the matchup and return a spread of outcomes rather than one number.
- Compare the results. Look at best, worst, and average finish times, not just whichever build won once.
- Adjust and re run. Small tweaks to skill choice or stat allocation can shift results more than people expect, so treat this as iterative rather than one and done.
Example: testing two Uma builds. Suppose you’re deciding between two Pace Chaser builds for a 2,000m turf race. Keep the track, distance, aptitude, and running style identical, and change only the skills you’re testing. Run both builds through the simulator and compare the average result, skill activation timing, and stamina outcome. That gives you a much cleaner comparison than changing five variables at once and trying to guess which one moved the needle.
How to Read Umalator Results
This is the part that trips people up most, and it’s also a question that comes up repeatedly in the Uma Musume community.
Umalator doesn’t just spit out a winner. It gives you a distribution: the average distance gap between the two Umas across many simulated attempts, along with how frequently different outcomes occurred. A build that wins by a mile in its single best simulated run but loses more often than not across the full spread isn’t actually the stronger build. Consistency across the distribution matters more than one flashy result.
The graph most people struggle with plots position or speed over the course of the race, letting you see exactly where one build pulled ahead, where a skill fired, and where a build’s stamina started to fade during the last spurt. Read it left to right as a timeline of the race rather than a single static score. If it’s still not clicking, browsing the build and mechanics discussion threads on UmamusumeGame is a good way to see the same confusion, and the explanations, that a lot of other players have already worked through.
If you’re looking for Umalator Reddit discussions, community threads can also help you compare simulator results with what players are seeing in actual room matches.
How to Use the Umalator Skill Table
The simulator includes a dedicated skill table, and it’s easy to skim past without realizing how much it actually tells you. The table breaks skills down by category, and understanding the categories matters more than sorting by a raw ranking number.
- Running style: skills are grouped by whether they suit Front Runner, Pace Chaser, Late Surger, or End Closer strategies
- Distance: filters for Sprint, Mile, Medium, and Long races, since a skill that’s excellent at 1,200m can be nearly useless at 2,400m
- Surface: Turf and Dirt skills often don’t transfer cleanly between the two
- Timing: early race, mid race, late race, and last spurt skills each solve a different problem
The most important thing to understand about the skill table is that a high ranked skill isn’t automatically a good pick for your build. A skill’s rank reflects its raw power under ideal conditions, not whether its activation condition will actually trigger given your running style, position, and the specific race you’re preparing for.
Umalator Stamina Calculator: What It Tells You
Stamina is where a lot of otherwise solid builds quietly fail, and the simulator’s stamina calculator is built specifically to catch that before it happens in a real race. It factors in your stamina and guts stats, any recovery skills on the build, remaining HP through the race, and your spurt rate to estimate whether the build can sustain a full last spurt rather than fading before the finish line.
A few things worth knowing before you lean on it:
- Stamina requirements shift significantly by distance and running style, so a number that works for a Mile build won’t necessarily hold up at Long distance
- Recovery skills change the calculation meaningfully, so testing with and without them shows you how dependent a build actually is on drawing that skill
- Don’t blindly copy another player’s stamina number from a guide or a community post. Their build’s skill set, running style, and target race may be different enough that the number doesn’t transfer cleanly to yours
Is Umalator Accurate?
Genuinely useful, but not a perfect mirror of an actual race, and it’s worth being upfront about that rather than overselling the tool.
Umalator is generally reliable for comparing builds and testing race mechanics in isolation, but its results shouldn’t be treated as a guarantee of what will happen in a live race. The simulator’s own documentation lists explicit caveats around skills that depend on nearby Umas, blocked conditions, skill cooldowns, and Front Runner speed up behavior, all of which are simplified compared to how a real race plays out. Community discussion on Reddit reflects the same conclusion: players generally recommend using Umalator alongside actual room matches and a solid understanding of skill activation conditions, rather than treating its rankings as absolute.
What Umalator Doesn’t Simulate Perfectly
It’s worth listing these plainly rather than burying them inside the accuracy section, because they’re the specific gap between a simulated result and what actually happens in a live race.
- Nine horse race dynamics. Umalator traditionally simulates a simplified head to head matchup, not a full field.
- Positioning and blocking. Getting boxed in behind a wall of horses is a real race factor the simulator doesn’t fully capture.
- Proximity based skill conditions. Skills that depend on where other Umas are positioned are generally assumed to trigger at the earliest mathematically possible window, which a messy real race lobby may never actually provide.
- Skill cooldowns. Some cooldown interactions are simplified relative to live game behavior.
- Front Runner speed up behavior. This is explicitly flagged in the simulator’s own documentation as an area where the model diverges from live races.
- Room composition and RNG. Who else is in the race, and how the race randomness plays out, isn’t something a two Uma comparison tool can predict.
Common Umalator Mistakes to Avoid
A handful of habits separate people who get real value out of the tool from people who get quietly misled by it.
- Running simulations on outdated game or skill data without realizing a fork hasn’t been updated recently
- Choosing a track or distance that doesn’t match the actual race you’re preparing for
- Ignoring distance or surface aptitude penalties because the raw stat numbers looked good
- Treating every skill as equally reliable regardless of how positional its activation condition is
- Looking only at the single best simulated result instead of the full spread of outcomes
- Underestimating stamina requirements because a build looked fine in a shorter test race
- Assuming a two Uma simulation perfectly reproduces what happens in a nine Uma Champions Meeting field
Using Umalator for Champions Meeting
Champions Meeting is where most competitive players lean on Umalator hardest, and it’s also where the tool’s limitations matter most. Umalator Champions Meeting testing is especially useful when you want to compare stamina, skills, and different build variations before spending more training resources. Use it to narrow down build direction: confirm a stamina floor for the distance, compare two skill loadouts on the same stat base, and check whether a strategy change actually improves consistency rather than just producing one lucky best case run. Once you’ve narrowed things down mathematically, it’s worth mentally adjusting for the fact that a real field has eight other Umas in it, and that positional skills won’t always get the clean activation window the simulator assumes.
If you’re the kind of player who enjoys testing systems and comparing outcomes before committing resources, you might also enjoy working through a Dokkan Battle team planning tool, which scratches a similar itch for a different gacha game.
Frequently Asked Questions
What is Umalator?
Umalator is a free, unofficial, community built race simulator for Uma Musume: Pretty Derby that lets players compare two character builds head to head before committing training resources to either one.
Is Umalator free?
Yes. It’s a community project, not an official paid tool, and there’s no cost to use the web based versions.
What is Umalator Global?
Umalator Global generally refers to a version of the tool built around global server game data, as opposed to the original Japanese server data the tool was first built for, and it’s worth confirming you’re on a version tuned for your actual server before trusting a result.
How do I use Umalator?
Enter a Uma’s stats, skills, and aptitudes for two builds, choose a track and distance, and run the simulation to compare the outcomes across multiple attempts rather than a single race.
Where can I find Umalator GitHub?
The open source development is spread across a few community repositories and GitHub Pages projects, most notably the alpha123 fork, which maintains the core simulator and changelog, and Kachi Dev’s fork, which adds extra tooling for global players.
Is Umalator accurate?
It’s reliable for one on one stat and skill comparisons, but it simplifies several real race dynamics like positioning, blocking, and Front Runner speed up behavior, so it works best as a build comparison tool rather than a guaranteed race predictor.
How do I read Umalator results?
Look at the full spread of outcomes, meaning the average distance gap and frequency of different results, rather than focusing only on the single best simulated run.
Can Umalator simulate Champions Meeting races?
It can help you prepare for Champions Meeting by comparing builds and testing stamina and skill viability, though it doesn’t fully reproduce the nine horse field dynamics of an actual Champions Meeting race.
What is the difference between Umalator and Moomoolator?
Moomoolator is a current web based implementation that builds on the same underlying community simulator work, crediting the original authors and the VFalator team, and it adds its own additional race analysis controls on top of the base simulator concept.
Why do Umalator results sometimes differ from an actual race?
Because real races involve multiple competitors, positioning, and lobby specific behavior that a simplified head to head simulation can’t fully account for, and because a given fork may be running on data that hasn’t been updated to match the latest game changes.
Final Thought
Umalator earns its popularity because it turns a guessing game into something closer to a spreadsheet decision, and that’s genuinely valuable when you’re deciding which Uma to invest scarce training resources into. The mistake is treating its output as gospel. It’s a comparison tool built on simplified math, not a perfect simulator of a nine horse race with all its positioning chaos. Used the way it’s meant to be used, as one input alongside your own race sense and knowledge of how Champions Meeting fields actually behave, Umalator is one of the best free resources available to Uma Musume players, and the players who get the most out of it are the ones who treat it as exactly that: useful, but not infallible.
If Umalator has you thinking about what else is worth your time on mobile, our roundup of the best mobile games is a decent next stop.
