LiveLive coverage · EU
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 6 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% of all ranked servers, top 87% in EU. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 6d 16h. The force wipe
This server has not put up a new map since the desk started watching it.
Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
The next wipe on Rusty Harpers is an estimate, drawn from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. 23 days 6 hours have passed since this world was generated. A monthly wipe schedule is published in its tags.
The Rust Live Stats lists that include Rusty Harpers are EU Rust servers, live, Live Rust community servers and Vanilla Rust servers, live. These filters on the server list bring it up: Region: Europe; Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Monthly ^m and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Monthly.
These are the tags Rusty Harpers makes public: gmrust (Game mode): Survival here follows standard Rust; mp100 (Max players): The slot count is 100; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here; ^m (Monthly): A single monthly wipe, set by Facepunch's force wipe; ^v (Vanilla): The rates, kits and rules are unchanged from what Facepunch ships; EU (Europe): In the server browser it sits under Europe. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Rusty Harpers is carrying 0 players at the moment, with 100 slots in total. Averaged over seven days: 0 players.
Seven-day player hours place Rusty Harpers at #15,269 overall, in the top 69% of ranked servers and #2,529 in Europe.
Nothing in the name of Rusty Harpers states a gather rate. Eight players per group, which is the game's default. survival applies here, the standard game: gather, build, raid. Fighting and raiding between players are allowed. The server browser lists it under Community. Vanilla is its own label: the rates, kits and rules are unchanged from what Facepunch ships. Anti-cheat: VAC from Valve is enabled.
Rusty Harpers runs a game-generated procedural map: size 4,250, seed 1337. RustMaps shows it from this page, since equal size and seed give an equal map.
Its EU tag places Rusty Harpers in Europe. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. You can reach it at 80.203.14.178:27019.
Server fps averaged 83 over the last 48 hours, with a low of 55. Buildings, deployables and everything else in the world added up to a maximum of 104,244 entities. The highest memory usage was 5,190 MB. A climbing entity count and low fps are felt as lag by players.
The setup on Rusty Harpers is Rust network protocol 2634 and build 167781 with Linux. To join, your game must use the same protocol; Steam handles the update for you.
Rusty Harpers is up and running at this moment. The uptime it reports puts the last restart at about 11 days 6 hours ago. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. On 6 October 2026, Rust Live Stats saw it for the first time.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 80.203.14.178:27019.