Error
Offline 91.51.17.140:28015 checked 38d ago
- Wipedunder 6 hours
- Fillingthe first day
- Peakthe first days
- Settledlater on
- Due againnext wipe close
Players, performance and rank
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
every wipe as a delivery, newest first- No wipe seen yet.
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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
- Rusty Moose |EU Mondays| 234 / 250
- Rustoria.co - EU Main 14 / 250
- Rusty Moose |EU Main| 17 / 250
- Rustoria.co - EU East Long 142 / 200
- Rustoria.co - EU East Medium 46 / 200
- Rustafied.com - EU Friday 40 / 100
Quick answers
From the figures on this page.
Population
What is the ranking of Error against other Rust servers?
A seven-day player-hours count places Error at #13,307: the top – of every ranked server.
What is the current population on Error?
The last sighting of Error was 38 days 1 hours ago; it is offline right now.
Map and rules
Which map is active on Error?
The map on Error is procedural, produced by the game.
What settings and rules should you know for Error?
No gather rate appears in the name of Error. Up to 8 players can join a group, the default for the game. It runs survival, gather and build and raid: the standard game. You can raid and fight other players. It appears in the server browser under Community, being a community server. VAC, the anti-cheat from Valve, is active.
About the server
What is the location of Error?
No region is published by Error. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. You will find it at 91.51.17.140:28015.
How reliable is Error, and is it currently online?
Error is offline at the moment, with the last sighting 38 days 1 hours ago. It was up 0 of 168 hours over the last 7 full days, 0% of the time. It was first seen by Rust Wipe Tracker on 19 September 2026.
What Rust version is Error using?
Rust network protocol 2633 and build 164530 on Windows is what Error runs. The same protocol is required to join, and Steam takes care of updating it.
Map resets
On what schedule does Error reset its map?
To tell its rhythm we would need more of Error's wipes on record; there are too few yet. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. 38 days 8 hours have passed since this world was made.
Server tags
Where does Error appear in Rust Wipe Tracker lists and filters?
The Rust Wipe Tracker lists that include Error are: Rust community servers, unmodded. These are the filters that bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on Error?
gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): Slot count: 500; ts8 (Group limit): 8 per team, which is the default; v2633 (Protocol): Join only if your game runs protocol 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): The region code is unset are the tags Error publishes, and the server browser takes them as read. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.
How to join
What is the process to join Error?
Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 91.51.17.140:28015.