Uma Race Planner for Umamusume Career Schedules
Build a practical race schedule before you train. Enter your target scenario, distance focus, and grade mix to estimate workload, reward value, recovery pressure, and what to test next in the race simulator.
Plan Your Uma Race Schedule
Use this race planner when you know the kind of run you want but need a quick check before committing turns. It does not replace the in-game calendar; it gives you a compact planning score so you can decide whether the schedule is light, balanced, or too demanding for your target build.
Planner Output
Adjust the fields and calculate to see whether your Uma race planner setup is light, balanced, or heavy.
Example plan
A Trackblazer-focused medium-distance run with 30 races, 9 mandatory races, 14 G1 races, 10 G2 races, and 6 G3 races will usually read as heavy. That can be worth it for reward farming, but it should be tested against your support card deck and stamina targets before you lock the route.
- Use the race load label to decide whether to cut optional races.
- Use the reward score to compare two possible schedules.
- Use the recovery estimate as a reminder to leave room for rest, poor training rolls, and bad condition events.
How to Use the Uma Race Planner
The planner is built for the moment before a career run starts. You can sketch the number of races you want, compare the grade mix, and then decide which plan deserves a full simulator test.
Choose the scenario
Pick a standard run, a race-heavy Trackblazer plan, or a lighter URA-style plan. The scenario changes how much pressure the same race count adds.
Set the distance goal
Sprint and mile plans tolerate more racing pressure than long-distance plans. Long routes need more stamina and recovery margin.
Enter race counts
Add total races, mandatory races, and the number of G1, G2, and G3 races. If grade counts exceed the total, the tool will show an error.
Compare two schedules
Run the same setup twice with different optional races. A lower load with similar reward score is usually the cleaner plan.
Uma Race Planner Signals
A good Umamusume race schedule is not just the most races possible. It balances rewards, required objectives, training turns, condition recovery, and the final race target.
| Signal | What it means | How to use it |
|---|---|---|
| Race load | A compact pressure score based on total races, mandatory races, grade mix, scenario, and distance. | Cut optional races when the result is heavy and your deck already struggles to hit target stats. |
| Reward score | A directional value for the schedule's race density and grade quality. | Use it to compare two schedules, not as an exact in-game payout formula. |
| Recovery turns | A practical estimate for how many turns you should keep available for rest, condition repair, or bad rolls. | Increase the margin for long-distance builds or race-heavy plans. |
| Build focus | The stat area most likely to constrain the plan after racing pressure is added. | Send the final build to the race simulator and stamina checks before using it competitively. |
When to Keep a Race or Train Instead
The planner is most useful when you treat each optional race as a tradeoff. A race can be worth the turn when it adds a strong grade reward, completes a scenario condition, or replaces a weak training turn. It is usually a cut candidate when it forces back-to-back racing, removes the only recovery window before a key objective, or makes the final build miss a core stat target.
Keep high-value races
Keep G1 races, scenario-relevant races, and mandatory route races when the schedule remains balanced. These races are the first ones to compare in the reward score.
Cut low-impact races
Remove lower-grade optional races first when the load becomes heavy. A slightly lower reward score is often better than losing several strong training turns.
Re-test after changes
After changing the route, run the plan through the simulator workflow again. A cleaner schedule should still support the target distance, stamina, and skill activation plan.
Limits and Edge Cases
This tool is a planning aid, not an official calendar database. Treat the output as a pre-run sanity check and combine it with your character objectives.
- The planner does not know every character-specific objective race, so keep mandatory races accurate.
- It does not predict exact fan count, item drops, or scenario event rewards.
- Race-heavy schedules can look attractive but still fail if support card training quality drops too far.
- Long-distance plans need extra stamina and recovery checks even when the reward score is strong.
- After choosing a plan, use the Uma Race Simulator to test race performance and the race bonus calculator to estimate reward pressure.