Error
Offline 91.51.17.140:28015 checked 38d 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 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- 500/250
- 328/325
- 34/250
- 36/250
- 165/200
- 74/100
Quick answers
from the figures on this pageWipe timing
How often does Error wipe, and when?
The rhythm of Error's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 38 days 13 hours ago.
Tags
Which tags does Error carry, and what do they mean?
Tags published by Error, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Error?
These Rust Metrics lists carry Error: Rust community servers: live readings. These filters bring it up on the server list: 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?
Ranking for Error: #13,307 on seven-day player hours, top – of all ranked servers.
How full does Error get?
Reading for Error: offline at this moment; last seen 38 days 6 hours ago.
Server
What location is Error hosted in?
Reading: location. Error gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 91.51.17.140:28015.
What Rust version is Error on?
Rust network protocol 2633 and build 164530 on Windows is the build Error runs. To get in, your game needs the same protocol; Steam applies the update.
Is Error up, and how often does it stay up?
Check: connection. Error is offline at this moment. Last contact was 38 days 6 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 19 September 2026.
Rules and settings
What settings and rules apply on Error?
No gather rate appears in the name: Error. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Error?
Procedural map on Error, made by the game's generator.
How to join
How do you connect to Error?
Press F1 in Rust and enter client.connect 91.51.17.140:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.