How to calculate XP between OSRS levels correctly

OSRS levels are not evenly spaced

A level number is a milestone on a cumulative experience curve, not a fixed-size block. Moving from level 20 to 21 requires far less XP than moving from 90 to 91. Subtracting level numbers therefore says nothing useful about the remaining work. You need the cumulative XP attached to each level.

The maintained experience reference publishes both the table and the underlying summation formula. A calculator can reproduce the exact integer thresholds by applying the same floor operations. This is deterministic: the same target level produces the same threshold. LootPath uses that distinction to label level-to-XP as exact rather than estimated.

Subtract cumulative XP, not levels

If you begin exactly at the threshold for level A and want level B, the exact remaining XP is cumulative XP at B minus cumulative XP at A. If you already have progress inside the starting level, use your current XP instead of the threshold. Ignoring partial progress overstates the remaining requirement, especially near the next level.

A level-only planner is still useful for broad routes because it creates a stable baseline, but a precise session plan should accept current XP. Hiscores can provide public XP for ranked skills, while the in-game skill interface is the final source for the account in front of you. Do not send login credentials to obtain a number that the public interface or client already exposes.

• Level-based route: XP(target level) − XP(start level).
• Account-specific route: XP(target level) − current account XP.
• If the result is zero or negative, the target is already reached.

Convert remaining XP into complete actions

For a method with a fixed XP reward, divide remaining XP by XP per action and round up. The upward rounding is essential because most actions cannot be completed fractionally. If one action gives multiple XP drops or can fail, define what counts as an action before trusting the result.

Inputs per action then turn the count into a shopping list. Multiply complete actions by bones, logs, potions or other materials used each time. If the method produces outputs, show them separately rather than silently subtracting optimistic sale revenue. Waste, failure and leftover materials should be visible planning assumptions.

Why exact XP does not create exact training time

Estimated hours equal remaining XP divided by an XP-per-hour assumption. The arithmetic is simple, but the rate is personal and contextual. Banking, travel, attention, tick consistency, gear, world conditions, failure rate and breaks all change the outcome. A published maximum is rarely the correct rate for an ordinary session.

Use a measured personal rate whenever possible. Train for a representative sample, note XP gained and active minutes, then calculate your own pace. For AFK methods, decide whether the denominator is logged-in time or actively managed time. The choice can change a comparison without changing a single XP drop.

Add cost only after the method and quantity are defined

Cost is not a property of the target level; it is a property of the chosen method and current market. Multiply complete actions by the real input quantity and acquisition price, then subtract conservative output value if the outputs are actually sellable. Apply Grand Exchange tax to taxable sales and include fees, charges or consumables.

A cheap method can take longer, and a fast method can lock more capital. Compare time, net cost and attention together. The best route for a two-hour weekday session may differ from the best route for an unattended weekend grind. LootPath presents methods as scenarios so the player can change one assumption and see the trade-off.

Turn a distant target into milestone XP blocks

A route from 70 to 99 can feel abstract because most of the cumulative XP sits in later levels. Break it into level milestones, unlocks or affordable material batches. Each milestone should have an XP amount, estimated actions, time range and a reason it matters. This creates natural points to remeasure pace and price.

Recalculate after a method unlock, gear change or major price movement. Do not preserve an old estimate merely because the target level has not changed. The exact XP remaining falls predictably; everything around it can change. A good planner keeps the fixed core stable and refreshes the assumptions around it.

A reliable level-to-session workflow

Choose the skill, enter current level or current XP and select a target. Confirm the exact XP difference. Compare two or three methods using realistic XP per action or your own measured XP per hour. Calculate complete actions and conservative input cost. Finally, split the route into a session-sized milestone.

After the session, replace the assumed pace with the observed pace and record unusual downtime. This feedback loop is more valuable than searching endlessly for a universal “best” rate. The formula tells you how far remains; the measurement tells you how your account will actually travel that distance.