Umamusume Skill Point Calculator
Estimate the skill points available for a career, check what remains after planned purchases, and keep a reserve for the skills your race plan still needs.
Plan Your Skill Point Budget
Choose a scenario, enter the points you expect to earn, add a conservative bonus estimate, and record your planned purchases. The calculator combines those values into a transparent budget so you can see the remaining points and whether your reserve is still protected. It is a planning model, not a claim about hidden game formulas.
Estimated Skill Budget
Adjust the fields to compare a skill plan before you purchase another skill.
Example Skill Plan
A Grand Live run with 950 earned points, 120 justified bonus points, 620 planned spending, and a 300-point reserve starts with a visible budget instead of guesswork. The output tells you whether the next purchase is safe or would consume the buffer needed for a late race skill.
- Use planned spending for skills that fit the target distance and strategy, not every skill that looks useful.
- Raise the reserve when the race plan depends on a late unlock, a gold skill, or uncertain activation conditions.
- After budgeting, test the complete build in the Uma Race Simulator and compare activation timing, placement spread, and win rate.
How to Use the Umamusume Skill Point Calculator
Use the calculator when a build feels short on skill points or when you need to choose between an immediate upgrade and a late-race reserve. The result is easiest to trust when every number has a clear source.
1. Choose the closest scenario
Select Classic, Grand Live, Unity Cup, or a custom estimate. The scenario adds a small baseline only; it does not replace the points you actually track in game.
2. Enter earned points
Record the points already visible in your run or your best evidence-based total at the target turn. If you are planning ahead, use a conservative forecast instead of the highest possible reward.
3. Separate real bonuses
Add event, scenario, or inheritance bonuses only when you can explain why they will arrive. Keeping this field separate makes an optimistic plan easier to spot and revise.
4. List planned purchases
Add the cost of the skills you are likely to buy for this race. Include essential green skills, recovery, acceleration, and strategy tools only when they belong to the same build.
5. Protect the reserve
Set a reserve for late choices. A plan that leaves exactly zero may look efficient, but it cannot adapt when a race condition, skill hint, or activation test changes your priorities.
What the Skill Point Budget Measures
The output is deliberately simple so you can compare two plans without pretending that it knows every future reward or hidden cost. Available points are the scenario baseline plus earned and justified bonus points. Remaining points subtract planned spending. The reserve comparison then turns the number into a decision.
| Input or signal | What it means | Planning use |
|---|---|---|
| Scenario baseline | A small starting estimate for the selected career route. | Use it as a consistent comparison anchor, never as proof of an exact in-game payout. |
| Earned skill points | Points already earned or forecast from training and races. | This is the main number to update after meaningful progress in a run. |
| Bonus points | A separate allowance for events, scenario rewards, or other explainable bonuses. | Keep uncertain rewards visible instead of hiding them inside the earned total. |
| Planned spending | The cost of the skills currently assigned to the build. | Compare a must-have list with an optional list before committing to a purchase. |
| Remaining and reserve | What is left after spending and whether it meets your protected buffer. | A negative result means the plan must change; a healthy reserve leaves room for late decisions. |
Transparent estimate
Skill costs, rewards, and activation value can differ by scenario, update, and race goal. Treat this page as a ledger for decisions. It is safer to undercount uncertain points and overstate the reserve than to build a plan that works only under perfect rewards.
When This Tool Helps
Skill point questions usually arrive at a decision boundary. These examples show how to use the same fields for different planning moments without turning the calculator into a tier list or a full race simulator.
Late-race purchase
A build is close to its target race, but one acceleration skill is still unaffordable. Compare the cost with the reserve and see whether a lower-priority green skill should wait.
Scenario comparison
Run the same planned purchases against Classic and Grand Live assumptions. The difference shows how sensitive the build is to the reward route rather than hiding it in one total.
Conservative forecast
Enter the points you can already justify, keep uncertain bonuses at zero, and add them later if they arrive. This reduces the chance of spending future points twice.
Team preparation
For a Champions Meeting team, give each runner a separate reserve. A single shared total can hide that one member has no points left for a required recovery or acceleration skill.
Limits and Edge Cases
The calculator is a budgeting aid. It does not read your account, identify skill prices automatically, or predict whether a skill will activate in a particular race. Use it to make assumptions explicit before you test a build.
- The scenario baseline is a comparison aid, not an official reward table. Replace it with your own tracked value when you have better evidence.
- Do not count the same event, race, or inheritance reward in both earned points and bonus points.
- A negative remaining value means planned spending exceeds the visible budget. Remove optional skills or lower the forecast before buying anything.
- A positive balance does not prove that a skill is worth its cost. Check distance, running style, course conditions, and activation timing separately.
- A reserve can become too large if it prevents essential skills from being purchased. Compare the reserve with the risk of the next race instead of following one fixed number.
- Balance changes and scenario updates may alter costs or rewards. Recalculate after a major game update or when your target race changes.
Reference Sources
The calculator is intentionally transparent. These references provide broader game context when you need to verify a skill description, race plan, or simulator result outside the budget ledger.
- Umalator Global simulator - Use a complete race simulation after the point budget is stable.
- Umamusume Pretty Derby on Steam - Official game and platform context; it does not publish a hidden skill-point formula.
- Uma Musume community mechanics reference - Community reference for checking skill and race terminology before making a plan.
Skill Spending Decision Checklist
Use the result as a pause point before buying the next skill. The best plan is the one that survives a changed race condition, not the one that reaches a zero balance fastest.
| Result | What it suggests | Next action |
|---|---|---|
| Remaining is negative | The purchase list costs more than the current budget. | Remove optional skills, lower uncertain rewards, or choose a cheaper route before spending. |
| Remaining is below reserve | The build can buy the listed skills but has little room for a late change. | Keep the essential skills, delay flexible upgrades, and recheck after the next reward. |
| Remaining meets reserve | The plan has room for the next decision and a protected buffer. | Validate the exact skill list against distance, style, course and activation conditions. |
| Spend ratio is very high | Most points are committed, so a small new cost changes the whole plan. | Compare a lean version with the full list in the race simulator before locking the build. |