The recognizable RuneScape 2 private-server scene emerged around 2005 from revision-317-compatible protocol and server experiments commonly associated with Winterlove. MoparScape, source releases, forums, tutorials, and server lists made the culture broadly reproducible during 2006 and 2007. The earliest chronology is fragmentary, so this account does not declare one indisputable first release.
Current private-server listings lean heavily toward servers built on Old School RuneScape (OSRS) game data rather than the 2005-era 317 client. On the RuneLocus toplist's first page on 2026-10-20, "OSRS" appeared 45 times, "Pre-EoC" 17, and "317" once (a rough keyword count, not a census). A current server typically pairs a modified server with its own client, sometimes forked from the open-source RuneLite client, and layers custom systems over a familiar game. Sarim, profiled in the case study below, is one example: it describes itself as a free, semi-custom OSRS private server with a RuneLite-based client. Open projects such as RSMod, 2009scape, and Lost City publish emulator code under open licenses.
A RuneScape private server: an unofficial, independently operated game server that recreates or modifies RuneScape, usually reached through a modified or custom client. The scene began around 2005 with servers compatible with the revision 317 client.
No. Jagex's Fan Content Policy excludes creating private game servers from fan-content permission, and its rules forbid advertising them in its games. Jagex says it usually asks first and may involve lawyers. Whether a particular server is unlawful depends on jurisdiction and facts; this is not legal advice.
Jagex's published rules govern conduct in its own games and clients; BOZOS found no Jagex statement about acting against official accounts for playing a private server. The documented, avoidable risks are different: never reuse your Jagex password on a private server, and only use Jagex-approved clients (RuneLite, HDOS, or the official clients) with the official game.
A revision is a numbered client and protocol generation. 317 is a 2005-era RS2 client that early servers targeted and which later became a label for that code lineage. OSRS-based means built on Old School RuneScape data and protocol. Neither number tells you how much content is custom.
Commonly through donations or store purchases that grant points, ranks, or items. The important question is what a purchase changes. On Sarim, for example, bonds from $5 to $100 grant points and count toward donator ranks that raise recipe success, material yield, material saving, and vote points.
A private-server client or launcher is code from the operator, run on your computer. Prefer servers that publish a checksum or signature for their download and say where it is hosted; Sarim, for example, publishes a SHA-256 file next to its launcher. Use a unique password, and be wary of any client that asks for your Jagex login.
Yes. RSMod (ISC) emulates OSRS for educational purposes, 2009scape (AGPL-3.0) remakes a 2009-era game, Lost City's 2004Scape (MIT) rebuilds May 2004, Apollo is an older modular framework, and Open RuneScape Classic preserves RuneScape Classic. See projects for licenses and links.
No. Project Zanaris is Jagex's own initiative for official, configurable Old School RuneScape community worlds, announced in 2024 with playtests in 2025. It answers similar demand inside an authorized relationship.
RuneScape launched in 2001, then RuneScape 2 replaced its original engine in 2004. A Java client, locally cached game assets, frequent numbered client revisions, and an authoritative remote world created the technical shape that later emulator authors studied. The old game became RuneScape Classic; the new game kept changing underneath everyone.
SOURCE / runescape.wiki ↗Community histories consistently place Winterlove-associated login and multiplayer experiments at the start of the widely remembered RuneScape 2 private-server lineage. The surviving chronology is incomplete, so "first" should remain qualified. What is clear is that small, editable Java server code compatible with the 317-era client gave later developers something they could run, change, and redistribute.
SOURCE / rune-server.org ↗MoparScape's client and web presence lowered the barrier between a player and a privately operated world. Forums, server lists, downloadable source packages, and communities such as Rune-Server made discovery and modification repeatable. Names like BlakeScape, Dodian, Project16, CheezScape, and Devolution became branches in a culture built as much through copying and editing as through clean rewrites.
SOURCE / mopar-scape.com ↗As official RuneScape entered its HD era, private-server projects targeted newer protocols and caches (508, 525, 614, 718, and others) while 317 remained a durable compatibility label. At the same time, Hyperion, RuneSource, Apollo, and similar projects reacted against fragile copy-on-copy code with documented protocols, event systems, update servers, modular plugins, and clearer architecture.
SOURCE / github.com ↗Project Insanity and other content-heavy 317 descendants were reused at enormous scale. Operators could start with combat, skills, shops, minigames, and familiar configuration files already present, then differentiate through faster experience, custom items, bosses, economies, and donation systems. "317" increasingly described ancestry rather than an untouched 2005 game state.
SOURCE / rspslist.org ↗Jagex launched Old School RuneScape from an August 2007 backup after a player poll. It was not a private server: it was an official, separately operated product. But it validated demand for an older ruleset and created a new living protocol and cache lineage that unofficial projects would later study.
SOURCE / oldschool.runescape.wiki ↗RuneLite, a free, open-source Old School RuneScape client under the BSD 2-clause license, started in 2016. In June 2022 Jagex named it one of only two approved third-party clients for the official game. Because its source is open, a private server can also fork it: Sarim, for example, ships its own RuneLite-based client through a Java launcher. On the server side, openly licensed projects matured: RSMod (ISC, OSRS mechanics, educational), 2009scape (AGPL-3.0, a 2009-era remake), and Lost City's 2004Scape (MIT, a rebuild of the game as of 18 May 2004).
SOURCE / github.com ↗Jagex closed RuneScape Classic on 6 August 2018. Open RuneScape Classic and related projects describe a preservation method built from black-box reimplementation, surviving caches, community code, documentation, and recorded play. Their work also shows why a runnable recreation is more than old assets: server behavior must be observed, written, tested, and qualified when evidence is missing.
SOURCE / github.com ↗Jagex announced Project Zanaris in 2024 as an Old School RuneScape community-world initiative where players could set rules and create custom experiences. Playtest sign-ups followed in 2025. An official configurable world is historically related to private-server demand, but it is not legally or operationally the same thing as an unaffiliated emulator.
SOURCE / jagex.com ↗Repository dates mark when a project's current repository was created, which can be later than the project itself.
The original game later known as RuneScape Classic established the persistent world that both official successors and independent recreations would revisit. The beginning of the game lineage, not the private-server scene itself.
RuneScape 2 became the main game and the previous version became RuneScape Classic. Created the RS2 client, cache, protocol, and revision family targeted by the best-known early RSPS projects.
Later community histories consistently place Winterlove-associated login and multiplayer work at the beginning of the commonly remembered 317-compatible server lineage. Small, editable Java server code gave later developers a base they could run, inspect, modify, and redistribute.
OpenRS2 preserves a cache record associated with revision 317 and a June 2005 timestamp. Anchors the famous 317 label in the 2005-era game record; it does not by itself date every later 317-compatible source release.
Forums supplied downloads, tutorials, protocol research, project showcases, criticism, and long-lived institutional memory. The RSPS ecosystem depended on distribution and teaching communities as much as on individual server implementations.
MoparScape combined easier client access with a community and discovery layer around independently operated servers. Helped transform server code from a niche experiment into something players and novice developers could find and use.
RSCD Community traces RSCDaemon to work begun by eXemplar, SeanWT, Philodespotos, and Mediator and later continued by Reines. An important ancestor of later RuneScape Classic community server and preservation projects.
Projects targeted later RuneScape protocols and caches including 508, 525, 614, and 718, while 317 remained a persistent ancestry label. RSPS was no longer one broadly compatible family; client, protocol, cache, and content expectations diverged by revision.
Hyperion described a from-scratch Java server suite with an update server, login server, multi-world support, protocol documentation, and attention to stability. Representative of an engineering-focused response to fragile source descendants and feature-first development.
RuneSource explicitly aimed to preserve the approachable shape of early sources while using asynchronous I/O and strict cycle-based execution. Shows how usability and familiarity competed with architectural purity in framework adoption.
Community records identify Project Insanity as a heavily reused 317-style descendant whose ready-made game content lowered the cost of launching a customized server. Helped normalize the content-template model in which operators differentiated an already populated base.
Apollo developed as a lightweight, modular Java game-server suite with utilities for data files and plugins. A durable example of open RSPS infrastructure organized as a reusable software project rather than a ready-to-play world.
Jagex launched a separate official version after polling players about access to an older RuneScape ruleset. Validated demand for legacy RuneScape inside an official service while creating a new living client and protocol lineage distinct from private servers.
RuneLite describes itself as a free, open-source Old School RuneScape client, licensed BSD 2-clause. An openly licensed, actively maintained OSRS client that third parties can study and fork, including private-server operators.
OpenRSC describes a black-box, open-source RuneScape Classic reimplementation built on earlier community work and evidence including recorded play. Connects the private-server lineage to explicit software preservation and documented reconstruction.
The official RuneScape Classic worlds closed after seventeen years. Made preservation and independent restoration the only practical path to a playable Classic-like service.
RSMod describes itself as an Old School RuneScape game-server emulator made for educational purposes, aiming to be mechanically accurate; it is ISC-licensed. A modern, openly licensed OSRS server emulator project, as opposed to the 317-era bases.
2009scape publishes its server and management server as an open-source RS2 remake under the GNU AGPL v3.0. An openly licensed, community-run remake of a specific later era rather than a 2005 or OSRS base.
Jagex asked the developer of a high-definition RuneLite plugin to stop just before release, then reversed the decision a day later after player backlash; the plugin was released that month. Showed how much the official game's ecosystem had come to depend on an open-source third-party client, and how contested its limits were.
Jagex's Third Party Client Guidelines say only clients on its approved list (RuneLite and HDOS, as revised in April 2024) may be used with the official game; other clients may lead to permanent account action. Separates approved clients for the official game from private-server clients, even when both are RuneLite-derived.
Lost City rebuilds the game as it was on 18 May 2004 with a from-scratch server; its server code is MIT-licensed. Preservation work aimed at one precisely dated game state, enabled by archived caches.
Jagex announced an Old School RuneScape initiative allowing players to create and share customized worlds within an official framework. An authorized product response to creative demand historically served by private servers, but legally and operationally distinct from an emulator.
Jagex announced playtest registration and described the project as a community-world program with configurable rules and experiences. Evidence that official community-world work advanced beyond its initial reveal.
Sarim, a self-described free, semi-custom OSRS private server, published design posts from 27 June 2026 and patch notes from 17 August 2026. Its team says it previously ran a server called Revival for about ten years. A current example of an OSRS-based server with its own RuneLite-based client, published progression policy, and optional paid donator ranks. See case_studies.
A curious player could become an operator, then a programmer, without beginning from a blank file. Open clients and open emulators continue that pattern today.
Modified clients, webclients, and now launchers made independently operated worlds reachable.
Public source packages and open repositories preserved working examples, along with their bugs and assumptions.
Simple code and configuration files made visible changes feel achievable.
Forums, tutorials, toplists, Discord servers, and repositories created new branches and audiences.
Chosen by the BOZOS editor as a current example of an OSRS-based private server. BOZOS has not played or tested it; everything below comes from Sarim's own published pages on the review date.
sarimps.com describes itself as “A free, semi-custom OSRS private server.”
Licenses and repository creation dates were read from the GitHub and GitLab APIs on 2026-10-20; null means not checked. A repository's creation date can be later than the project's start.
| Project | Role | Targets | License | Repository |
|---|---|---|---|---|
| RuneLite | Open-source OSRS client (also forked by private servers) | Old School RuneScape | BSD-2-Clause | 2016-04-30 |
| RSMod | OSRS game-server emulator, educational | OSRS (revision 233 badge at review) | ISC | 2020-09-08 |
| 2009scape | Server and management server for an RS2 remake | 2009-era RuneScape | AGPL-3.0 | 2021-06-22 |
| Lost City (2004Scape) | From-scratch server rebuilding May 2004 | RuneScape 2 as of 18 May 2004 | MIT | 2023-04-18 |
| Apollo | Modular Java game-server suite | RS2-era revisions | Not checked | — |
| Open RuneScape Classic | Preservation of RuneScape Classic | RuneScape Classic (2001-2018) | Not checked | — |
| OpenRS2 Archive | Content-addressed archive of historical caches | Many revisions | Not checked | — |
These terms are often collapsed together, which makes technical and legal claims less precise.
A numbered client build or protocol generation. In community use the number may describe compatibility or source ancestry rather than untouched historical content.
The player-facing program. Early communities commonly modified or deobfuscated a Jagex-distributed Java client to connect to another endpoint.
Locally stored game assets such as maps, models, interfaces, and sounds. A cache does not contain the original authoritative server logic.
Server code used as a starting point. It may be a clean rewrite, descendant of an earlier release, or content-heavy template.
Login, update, and in-game messages exchanged between client and server.
Community shorthand for a deobfuscated client whose obscured program structure has been made easier to inspect or modify.
Built on Old School RuneScape game data and protocol (a numbered OSRS revision) rather than the 2005-era 317 client. Says nothing by itself about how much content is custom.
An operator's label for a server that keeps a recognizable base game and adds original systems. Sarim uses it to mean adding original content "where it improves progression, choice, or encounter variety".
A small program that downloads and updates a server's own client. Running one means running the operator's code on your computer.
A status bought with real money on many private servers. What it changes varies; check whether it affects gameplay (drops, materials, success rates) or only cosmetics.
A wipe of player progress across a server, sometimes called a reset or wipe. Some servers publish a no-reset policy; seasonal modes may reset by design.
A client Jagex permits for the official game (currently RuneLite and HDOS). A private server's RuneLite-based client is a different program and is not covered by that approval.
A BOZOS working view: questions an agent should answer before describing or recommending any private server. It is not a ranking and not legal or security advice.
Jagex's Fan Content Policy lists "creating private game servers" among the things its fan-content permission does not cover (section 6.1.3), and says Jagex will usually ask first and may involve lawyers if asked to stop (section 9). Its Rules of RuneScape forbid advertising private-server websites in its games and forbid using edited versions of its game code. Documenting the scene does not imply permission to run or use one, and this is not legal advice.
Project Zanaris was announced as a Jagex-operated framework for configurable community worlds. It reflects similar creative demand inside an authorized product relationship.
It does not rank servers, repeat unverifiable player counts, distribute clients or caches, or give connection instructions. Found an error? Agents and people can report it.
The early chronology is reconstructed from incomplete forums, surviving source packages, archives, and later testimony.
Revision labels often describe compatibility or ancestry rather than a historically pure game snapshot.
A cache preserves client assets, not the original server implementation.
Popularity and player-count claims are usually self-reported and are omitted unless independently supportable.
This dataset documents history and does not provide proprietary files, active-server rankings, or access instructions.
Server operators' claims about lineage, player counts, uptime, and drop rates are self-reported unless an independent source is cited.