Umamusume Support Card Comparison Tool
Compare up to three support-card candidates with the same race goal, then see which one deserves the next deck slot.
Compare the card that fixes your bottleneck
Choosing between support cards is easier when the decision is tied to a real runner. This Umamusume support card comparison tool lets you enter three candidates, set a race distance and training focus, and compare the same visible factors side by side.
The model is transparent rather than official. Enter the values from your card details, use the score to organize the decision, and confirm the final deck with your scenario, inheritance, skills, and race plan.
Hold the context steady
Compare candidates against one distance and one training focus so the result answers a real deck question.
See the inputs
Level, training bonus, skill value, event utility, and hint value stay visible instead of hiding behind one ranking.
Change one slot
Use the result to test a replacement, then review stamina, race bonuses, and the finished runner in the other tools.
Compare Three Support Cards
Use the Umamusume support card comparison tool to enter three candidates, then replace the sample values with the levels and effects shown in your game or a trusted card reference.
Comparison Output
Example outputThe Speed card example leads this medium-distance Speed comparison because its role matches the selected focus and its example inputs are consistently strong. The result is a shortlist signal, not an official card ranking.
Boundary check: try a level of 1 or 50 and a metric of 0 or 100 to see how strongly one extreme input changes the comparison.
Example inputs
The defaults show the workflow, not current stats for any named card. Replace every field before relying on the output.
- Medium distance with Speed as the immediate training focus.
- Three candidates entered with different roles and realistic investment levels.
- Skill, event, hint, and training values are user-supplied comparison signals.
- Use the winner as a shortlist, then confirm card details and scenario fit elsewhere.
| Rank | Candidate | Role | Score | Focus fit | Read |
|---|---|---|---|---|---|
| 1 | Speed card example | Speed | 86 | Strong | Best fit |
| 2 | Wisdom card example | Wisdom | 79 | Useful | Utility option |
| 3 | Stamina card example | Stamina | 73 | Situational | Distance option |
How to Use the Support Card Comparison Tool
Treat the comparison as a controlled experiment. Keep the target race and focus fixed, enter the same kind of information for every candidate, and only then decide which card deserves a deck slot.
1. Set the race context
Choose sprint, mile, medium, or long distance. The distance provides context for a replacement decision, but the tool does not know the exact course, scenario, aptitude, or race schedule.
2. Choose the bottleneck
Select Speed, Stamina, Power, Guts, Wisdom, or balanced coverage. A focus makes the score answer a specific question instead of producing a generic ranking.
3. Enter comparable inputs
Add a recognizable name, main role, level, training bonus estimate, skill value, event utility, and hint value for each candidate. Use the same scale and be conservative when information is uncertain.
4. Review the table, then verify
Compare score, focus fit, and the planning read together. Shortlist the best replacement, then check the card's exact effects, your inheritance, race bonuses, stamina needs, and finished runner.
What Each Comparison Field Means
The tool separates signals that are often mixed together. Strong events or skills do not automatically make a card the right replacement for today's deck.
| Field | What to enter | Why it matters |
|---|---|---|
| Role | The main training or utility type. | Shows fit for the selected focus. |
| Level | A realistic whole-number level from 1 to 50. | Measures current investment, not permanent tier. |
| Training bonus | A 0–100 estimate for training impact. | Use one scale for every candidate. |
| Skill value | How useful the skill package is here. | Only matters when skills match the plan. |
| Event utility | A 0–100 estimate for event quality. | Events can matter during the full run. |
| Hint value | How helpful hints are for this build. | Hints can change value without changing role. |
How to Read the Comparison Output
The score is a transparent heuristic built from your inputs. Use it to structure the next test, not to replace a database, tier list, or race simulator.
Focus fit
A matching role receives a stronger fit signal. Balanced coverage reduces the pressure to match one role.
Level is an investment signal
A level-50 card may win because it is ready now. Recheck equal levels before calling it stronger.
Utility needs context
Skills, events, and hints are estimates. Check activation, scenario value, and strategy before trusting a high input.
Close scores need a real test
A small gap may matter less than inheritance, scenario bonuses, card availability, or the bottleneck from your last run.
Example Support Card Decisions
These examples frame a comparison. They are prompts, not a universal tier list.
Replacing a repeated Speed slot
Keep Speed as the focus and compare realistic replacements. Look for the card that fixes the bottleneck without creating a stamina or Wisdom gap.
Choosing long-distance utility
Set Long distance and compare stamina with Friend or Wisdom. A lower score can still win if it fixes measured endurance or consistency.
Borrowed versus owned cards
Enter the level you can actually use, then repeat at equal levels to separate availability from underlying fit.
Limits, Validation, and Edge Cases
A support-card comparison is one layer of a build. The model stays manual because hidden data, scenario updates, and card interactions can change the answer.
- There is no live database of every global or JP card, limit break, event, skill, or balance change.
- The score is not an official formula, win-rate prediction, guaranteed rank, or race simulation.
- Use the same level of certainty for every candidate; the result is only as fair as the inputs.
- A tier list and this tool answer different questions. A high-tier card can still be the wrong replacement.
- If a field is unknown, use a conservative estimate and check a trusted card reference.
- For a boundary test, use level 1 or 50 and metrics 0 or 100. The page should recalculate without stale output.
A practical verification loop
Compare candidates here, review the six-card composition in the deck builder, check race bonuses and stamina, then run the finished runner through the race simulator.