OSRS Tracker

Features

• XP Tracker: look up any player and follow their daily XP gains, levels, boss kills, clue scrolls and more. Keep a list of your favourite players to check on your (and your friends') progress.
• Price Tracker: search any tradeable item and see its current Grand Exchange price, trends, and price and volume charts from the last day up to the last year. Tables rank items by high-alch profit and by margin after tax.
• Players online: how many people are playing right now, split by members and free-to-play and by country's worlds, and the count over the last day up to all time.
• OSRS News: the latest news on the home page, and every news post since the first in the archive at /news, by category.

How it fits together

This repository is the website. It is one of four parts:

• osrs-tracker-web (this repo): the website at osrs-tracker.net.
• osrs-tracker-api: the API that serves player, item and news data to the website.
• osrs-tracker-aws: background jobs that save a daily snapshot of every tracked player and keep the item list up to date.
• osrs-tracker-packages: the @osrs-tracker/* npm packages the other three share (models, hiscores, logging, metrics).

Live hiscores come from the official Old School RuneScape hiscores, and prices come from the OSRS Wiki prices API.

Running it locally

You need Node 26 or later.

npm ci
npm start

The site runs at localhost:4200 and uses the live API. Run it on port 4200, because the API only accepts requests from that address when running locally. If something else is using the port, ng serve offers another one: decline and stop the other process instead.

Local runs use the production API, so player lookups show up in the live "Global recent lookups".

Contributing

Before pushing, run the same checks as CI (lint, Prettier, knip, jscpd, ShellCheck and the link check if they're installed, the tests and a production build, all at once, reporting every failure):

.claude/skills/verify/verify.sh

CI builds with npm run build instead, which also regenerates the sitemaps and icons and optimises chunks, so a build that only breaks with chunk optimisation shows up in CI first (npm run build reproduces it; see below). npm run prettier fixes formatting, and npm test runs the tests in watch mode. Pushes made by Claude Code are linted first by .claude/hooks/pre-push-check.sh; your own git push isn't, so CI catches it.

npm start doesn't run the server code (page cache, pre-rendering). To test that, build and run the production server. npm run build also regenerates the site sitemap and the sitemap index (dates from git) and the icons, so run git restore public/sitemap*.xml afterwards:

npm run build
HOST=localhost PORT=4200 node dist/osrs-tracker-web/server/server.mjs

Merging to main deploys: once CI passes, the CD workflow builds and pushes the image and commits its digest to osrs-tracker-web.yaml, which Flux applies to the cluster. Conventions, the deploy and the release flow are in .claude/skills/osrs-tracker-web/SKILL.md, rollback in docs/runbook.md.

Built with

Angular with server-side rendering, Tailwind CSS and Chart.js, running on Node 26 in Docker on Kubernetes.

Development

OSRS Tracker was originally built entirely without AI assistance. Since October 2026, I've started using Claude, Anthropic's AI coding assistant, to help improve development speed and reliability.

License

Elastic License 2.0: you're welcome to read the code, learn from it, change it and run it yourself, but not to offer it to others as a hosted service, paid or free.

The font files in public/assets/fonts/ and src/server/og/fonts/ are not under the Elastic License 2.0: they are proprietary, and their terms are in public/assets/fonts/LICENSE.txt.