Error
Offline 93.211.110.194:28015 checked 37d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestTop 58% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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- 507/550
- 422/450
- 63/250
- 67/250
- 55/100
- 169/200
Quick answers
from the figures on this pageWipe timing
What wipe timing does Error follow?
To tell the rhythm of Error, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 39 days ago.
Tags
How should you read the tags on Error?
These are the tags Error publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Error appear in Rust Metrics lists and filters?
Rust Metrics lists featuring Error: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
What position does Error hold among Rust servers?
Player hours over seven days put Error at #13,247, in the top 58% of all ranked servers.
How full does Error get?
Status for Error: offline. Last seen 37 days 9 hours ago.
Operator and location
What location is Error hosted in?
No region comes from Error. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 93.211.110.194:28015.
What Rust version is Error on?
Version check: Rust network protocol 2633 and build 164530 on Windows, run by Error. Matching protocol is required to join. Let Steam update your game.
What is the uptime on Error, and is it online?
Reading: offline. Error last answered 37 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 21 September 2026, recorded by Rust Metrics.
Rules and settings
What rules does Error enforce, and what are its settings?
Check: gather rate. The name Error does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
What map is Error on?
Check: map. Procedural, generated by the game, on Error.
How to join
How do you connect to Error?
Press F1 in Rust and enter client.connect 93.211.110.194:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.