Umamusume Deck Builder
Plan a six-card support deck, check its stat coverage, and find the biggest training gap before you commit a run to the game.
Build the deck around the race you actually want to run
A support-card deck has to match the distance, target stat, scenario, and flexibility you need during training. This Umamusume deck builder gives you a quick planning pass before you choose inheritance, skills, and races.
Enter each card's role and level, choose a distance and focus, then compare the result. The score is a transparent signal based on coverage, focus alignment, levels, and variety; it is not a hidden game formula or live card database.
See the shape
See repeated types, missing stats, and over-specialization across six slots.
Test a goal
Test sprint, mile, medium, or long distance with a focused or balanced plan.
Make one change
Test one replacement at a time, then validate the finished runner in the race simulator.
Build Your Six-Card Support Deck
Enter the cards you own or are considering. Each slot is a training role rather than a named card, so the builder works for a new account, scenario draft, or quick deck comparison. Use current levels for owned cards and conservative expected levels for future cards.
Deck Planning Output
Example outputThis focused but flexible deck scores 81/100 for a medium-distance Speed goal. It covers several training needs while leaving one stat type outside the six-card plan.
- Keep the Speed focus if the target runner needs a strong velocity ceiling.
- If late-race stability matters, test a Guts card or compare the result with the stamina calculator.
- Run the finished build through the race simulator before treating the deck score as a verdict.
Example deck
The example uses two Speed cards, Stamina, Power, Wisdom, and Friend or utility. It is a starting point, not a universal recommendation.
- Medium distance with Speed as the main focus.
- Average expected card level: about 33.
- Four core stats covered; Guts is absent.
- Use the race simulator after training to check the runner and course.
How to Use the Umamusume Deck Builder
Use the builder as a comparison loop: set the race, enter six realistic roles, and change one slot when the output shows a problem.
1. Set the race context
Choose sprint, mile, medium, or long distance. Distance changes how much stamina safety, acceleration, or flexibility you may want; check the event course separately.
2. Pick the main training goal
Select the stat you expect to emphasize, or choose balanced coverage. A focus is a testable assumption, not a command to stack one type.
3. Enter all six card roles
Choose Speed, Stamina, Power, Guts, Wisdom, or Friend and add a level. Use the current level for an owned card and a conservative level for a planned or borrowed card.
4. Review, replace, and verify
Read coverage, focus match, average level, and suggestions together. Replace one weak or repeated slot, review again, then validate the runner with the other tools.
What Each Support-Card Role Adds
Cards are grouped by their main training role so the result stays useful across card pools and scenarios. This table is a decision aid, not a permanent tier ranking.
| Role | What it can contribute | What to watch |
|---|---|---|
| Speed | Supports a high Speed target and focused race plans. | Too many copies can leave Stamina, Wisdom, or another bottleneck uncovered. |
| Stamina | Supports medium- and long-distance endurance planning. | It may add little when the race is short or another source already covers stamina. |
| Power | Supports acceleration and builds that cannot rely on Speed alone. | It is not a universal fix for stamina or skill-activation problems. |
| Guts | Adds a late-race or endurance role to a deliberate specialization. | Add it for a scenario or course reason, not just for variety. |
| Wisdom | Supports skill activation and a steadier training rhythm. | It may improve consistency without fixing a missing Speed or Stamina target. |
| Friend / utility | Fills a flexible scenario or utility role. | If it solves no real constraint, test a core-stat replacement. |
How to Read the Deck Builder Output
The output is split into signals instead of one ranking. A high-level deck can still miss a stat you need, so use the numbers to choose the next test.
Deck score
This combines level, coverage, focus match, and variety into a 0–100 planning score. Compare versions with the same context; it is not an official rating or race guarantee.
Stat coverage
Coverage shows how many of the five core stat roles appear. High coverage adds flexibility; low coverage can be correct for a deliberate narrow plan.
Focus match
Focus match checks whether the selected goal appears in the deck. A high value supports the plan but does not prove the course, card skills, or scenario are right.
Average level and planning read
Average level explains part of the score, while the planning read summarizes the shape. When two decks are close, test the weakest variable instead of chasing one point.
Example Deck Decisions
Different goals can justify different compositions. Use these examples as decision prompts, not a fixed best-deck list.
Focused Speed plan
A sprint or mile runner may start with multiple Speed slots and utility. If coverage is weak, check stamina before adding another Speed card.
Medium-distance balance
A medium plan often benefits from Speed, Stamina, Power, and Wisdom. If levels are low, a simpler reliable deck may beat broad but under-leveled coverage.
Long-distance safety check
For long races, test endurance before optimizing the headline stat. Pair the review with the stamina calculator and race simulator.
Limits, Validation, and Edge Cases
A support-card deck is only one layer of an Umamusume build. This tool intentionally stays transparent and lightweight so it can help with early choices without pretending to know every hidden interaction, scenario bonus, card skill, or future balance change.
- The builder uses card roles and expected levels; it does not contain a live database of every support card, skill, event, or limit-break effect.
- The score is a comparison heuristic. It cannot predict a win rate, a guaranteed rank, a friendship event, or a particular training outcome.
- A tier-list result and a deck-builder result answer different questions. A high-tier card may still be the wrong slot for a specific distance, scenario, account, or skill plan.
- If two cards share a type but have very different events or skills, enter the role first and inspect the named card's details separately.
- When a build fails, identify whether the cause is stats, stamina, skills, aptitude, race schedule, or strategy. Change one factor at a time so the next simulator run teaches you something useful.
A practical verification loop
Draft the deck here, check the training schedule and race bonuses, review stamina for the target distance, and then run the finished stat line through the race simulator. If the runner performs poorly, return to the deck only after identifying the measured bottleneck.