Error
Offline 91.51.17.140:28015 checked 27d ago
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
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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
- 142/ 200
- 285/ 300
- 249/ 275
- 781/ 800
- 107/ 200
- 111/ 250
Quick answers
Tags and filters
Where does Error appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Error are: Rust community servers, going deep. You can find it on the server list by these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on Error?
The server browser shows these tags for Error: gmrust (Game mode): Survival, as standard Rust does it; mp500 (Max players): The slot count is 500; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs164530 (Build): This server runs build 164530; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
What's the location of Error?
Error does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 91.51.17.140:28015.
How reliable is Error?
Error is down at the moment; it was last up 27 days 23 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 19 September 2026.
What Rust version is Error on?
The version on Error is Rust network protocol 2633 and build 164530, on Windows. The protocol must match to join; Steam will update your game.
Wipe info
What schedule does Error follow for wipes?
The wipes recorded for Error are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 28 days 6 hours ago.
Rules and settings
What settings and rules have been applied to Error?
The name of Error contains no gather rate. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. The server browser lists it under Community, making it a community server. The server runs Valve's anti-cheat, VAC.
Which map is active on Error?
A procedural map, generated by the game, is in play on Error.
Population
Is Error busy?
Right now Error is offline, with its last appearance 27 days 23 hours ago.
What's Error's rank among Rust servers?
Over the last seven days, Error is #13,307 by player hours, among the top – of all ranked servers.
Join info
What's the process to join Error?
Open Rust and press F1, then type client.connect 91.51.17.140:28015. Alternatively, click Launch Rust on this page to join via Steam.