Live coverage · Rust server
Offline Error is not on the server list right now. The figures below are from when it was last seen, 4d ago.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
The current map
Saturday 24 October 2026, 19:43 UTC
Wipe
Thursday 8 October 2026, 18:51 UTC
Wipe
Saturday 26 September 2026, 15:27 UTC
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 average peak across its recent wipes is 1 players. 5 hours after the latest wipe, the crowd reached its peak. In 100% of recent wipes, population held above half the peak right through to the next wipe.
No next wipe can be predicted for Error, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 4 days 2 hours have passed since this world was generated.
On Rust Live Stats, Error is listed under Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week it appears on the server list.
The server browser reads gmrust (Game mode): The game mode is standard Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game changes here through plugins or settings, so it is Modded, which Error publishes. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Error is not online at the moment, having last been seen 4 days ago. Peak over the past week: 1. Average: 0 players.
Player hours over seven days put Error at #13,808, in the top 62% of all ranked servers.
Nothing in the name of Error states a gather rate. Eight players per group, which is the game's default. survival is the mode, with the standard game: gather, build, raid. Raiding and player combat are both permitted. Plugins or settings change the game, and the browser lists it as Modded. Plugins run here: Oxide. VAC is enabled: Valve's anti-cheat.
A procedural map, generated by the game, runs on Error.
Nothing on Error states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. You can reach it at 78.10.176.214:28015.
The setup on Error is Rust network protocol 2635 and build 168909 with Windows. To join, your game must use the same protocol; Steam handles the update for you.
As of now, Error is offline; the last sighting was 4 days ago. 3 of 168 hours were online in the last 7 full days, giving 2% uptime. The first sighting by Rust Live Stats was on 25 September 2026.
Enter client.connect 78.10.176.214:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.