RS3 · Guide

RuneMetrics Alternative: What Still Works Now RuneMetrics Has Closed

Last revised

If RuneMetrics has stopped working for you, or a tracker you used has gone quiet, it is not your account and not your settings. Jagex switched the RuneMetrics API off on 10 November 2026, for everyone. This guide explains what RuneMetrics did, what went away with it, what Jagex put in its place, and how to keep following your XP, levels, quests and drops.

The short versionYour levels, XP and ranks are still public on Jagex's HiScores, and your quests and recent activity are on Jagex's new Platform API. Look yourself up on The Codex and your profile, gains and charts are there, with nothing to sign up for and no setting to change.

What RuneMetrics was

RuneMetrics was Jagex's stats service for RuneScape 3. Behind it sat a set of web addresses that fan sites, Discord bots and tools could read. Jagex's developer documentation lists three of them:

  • The profile. A player's skills (level, XP and rank in each), their quest counts (started, completed, not started) and their latest activity: the Adventurer's Log lines for things like a boss drop or a level-up.
  • The quest list. Every quest with its status, difficulty, quest points and whether the player could start it.
  • Monthly XP. The XP a player gained in a skill, month by month.

Most RS3 trackers, The Codex included, read some or all of these. RuneMetrics also had a privacy setting: a player could set their profile to private, and the profile and activity were then hidden from these addresses.

What went away on 10 November 2026

Jagex announced the change in its weekly news post on 26 October 2026, saying the RuneMetrics API would be "fully sunset on November 10th", and its developer documentation says every address under apps.runescape.com/runemetrics/ goes offline that day. So from 10 November:

  • Anything that read RuneMetrics stopped getting answers. That is why a RuneMetrics page, a bot or a tracker can show errors, empty profiles or old numbers since then.
  • Monthly XP has no replacement. Jagex's documentation says there is "no direct replacement" for the month-by-month XP, so any tool that showed it from RuneMetrics can no longer get new months from Jagex.
  • The RuneMetrics privacy setting no longer hides anything. Jagex says the new API does not enforce the Adventurer's Log privacy options, and that those settings pages will be removed.

Nothing happened to your character, your levels or your XP. Only the way outside sites read your profile changed.

What Jagex replaced it with

Jagex launched a developer site for its new Platform API on 4 November 2026. For RuneScape 3 it has two parts that cover most of what RuneMetrics did:

  • The HiScores, Jagex's public table of levels, XP and ranks. They were always there, they were never hidden by the RuneMetrics privacy setting, and they update within a couple of seconds when a player logs out or hops worlds.
  • The Adventurer's Log module, with a player's 20 most recent events (drops, kills, level-ups and more) and their "player data": skills and the full quest list. Jagex added the player data part on 6 November 2026 and on the same day stopped requiring membership to read a player's events.

Two things to know about the new data, both from Jagex's own pages:

  • It can be a few minutes behind. Jagex caches answers for up to 10 minutes, and kills and level-ups can arrive in batches: 30 Kalphite Queen kills can show as one event, dated when the batch was added.
  • Hiding your activity is now done in game. Because the old privacy setting is not enforced, Jagex points players to the in-game settings instead: Settings, then Gameplay, then Chat & Social, then RuneMetrics Event Log, where each kind of event can be switched off. Jagex notes the change is not retroactive, so events already logged stay logged.

What still works on The Codex

The Codex reads levels, XP and ranks from Jagex's public HiScores, and it keeps its own readings of every tracked player. That is why most of it carried on through the change, and the parts that came from RuneMetrics now come from Jagex's replacement.

Looking players up

Type any RuneScape name into the search box on the homepage. The Codex reads that player's levels, XP and ranks from Jagex's public HiScores, for anyone the HiScores list. There is no login, no download and no setting to switch on.

Gains, charts and the heatmap

Once an account has been looked up, The Codex re-checks it regularly, usually within a day or two, and daily once its owner has verified it. It keeps those readings, which is what makes the rest possible: XP gained over 24 hours, 7 days and 30 days, a daily-gains heatmap, the long charts and projected dates for your next milestones. These are worked out from the site's own readings, so they carried on through the change.

That also covers most of what people used monthly XP for. The month-by-month figures Jagex kept are gone, but the XP The Codex works out from its own readings carries on from the day a player was first tracked.

Activity feed, drops and quests

The activity feed, quest lists, new drops and drop alerts, quest completions and cape milestones now come from Jagex's Platform API, as The Codex re-reads each player. Drops logged before the change are kept on the profile, grouped by boss.

Alerts

You can connect a Discord webhook to get pinged for a level 99, a 120, 200M XP, a new cape or a notable drop, for a single player or for a whole clan. Browser alerts for level-ups, 99s, 120s and 200M XP work too. Level alerts come from HiScores readings, so they never needed RuneMetrics.

Clans, groups, races and leaderboards

Look up a few members and their clan or Group Ironman group gets its own page with a combined leaderboard. Clan races read Jagex's clan member lists and name-list races read the HiScores, so neither needed RuneMetrics. The leaderboards rank every tracked player by total XP, total level and the week's gains, with a board for each account type, such as the Ironman leaderboards.

Verifying your profile

Verifying used to mean switching your RuneMetrics profile between public and private. That way went with RuneMetrics. Now you verify a character by starting a quest The Codex names, or by gaining XP in two skills it names and typing how much. Only the account's owner can do either in game, and The Codex checks it against Jagex's public data. Characters verified the old way stay verified.

What is not on The Codex any more

  • Monthly XP from Jagex, which has no replacement (see above).
  • The Adventurer's Log privacy setting. Jagex's new source does not say whether a player has hidden their log, so The Codex cannot see that setting. Players the site already knows are private, and blocked players, stay hidden.

Other trackers

The Codex is not the only RS3 tracker. Other community sites such as RuneStats and Crystal Math Labs track XP too. Each one had to make its own changes after 10 November, so check their own sites for what they support now.

Whichever you use, it helps to know where a number comes from. Levels, XP and ranks come from the HiScores and are the most dependable. Activity, drops and quests come from the Adventurer's Log module and can be up to 10 minutes behind. Anything a site shows from before it started tracking you, such as old monthly totals, came from RuneMetrics and will not grow any more.

Questions

Why is RuneMetrics not working? Jagex switched its API off for everyone on 10 November 2026. Nothing you change in your account or settings will bring it back.

Do I need to make my profile public? No. The HiScores are public for every player they list, and The Codex reads them without a sign-in. The old RuneMetrics privacy setting no longer changes anything here.

Are my old drops and charts gone? No. Drops already logged, and the readings The Codex has kept of your XP, stay where they are, and new drops are added from Jagex's Platform API.

I make my own RS3 tool. What changed for me? Our developer write-up, Moving from RuneMetrics to the Platform API, maps each old RuneMetrics address to its replacement and lists what changed in the answers.

Sources