Station XX-13819 · no signal
Error
Offline 78.10.176.214:28015 checked 3d ago
- Players now
- 0/ 5
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak 1
- Rank
- #13,819
- top 62%
- Last wipe
- 3d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 5 slots
- Motion · 24 h
- M –not enough readings
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 bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 14.1 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 24 Oct, 19:43 UTC4d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 8 Oct, 18:51 UTC20d ago | M0.0▼falling | 0 | – | 16 days | 1 | |
| Sat 26 Sep, 15:27 UTC32d ago | M0.0▲rising | 1 | held half | 12.1 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageMap and rules
Which map is running on Error?
Error uses a procedural map, which the game generates.
Which settings and rules apply on Error?
You will find no gather rate in the name of Error. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on Error?
Error is not responding at this moment and is offline, last seen 3 days 21 hours ago. The seven-day average is 0 players, with a peak of 1.
How does Error rank against other Rust servers?
On player hours for the past week, Error sits at #13,819, which puts it inside the top 62% of every ranked server.
Operator and location
How reliably does Error stay online?
As recorded now, Error is not reachable, the last contact having been 3 days 21 hours ago. 3 of 168 hours in the last 7 full days were up time, 2% of the total. 25 September 2026 is when Rust Server Trends first recorded it.
Where in the world is Error hosted?
A region is not published by Error. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 78.10.176.214:28015.
Which Rust version is Error running?
Error is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Error?
1 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 5 hours after the wipe. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.
How often does Error wipe, and on which days?
There is no next wipe to predict at Error, since its wipes fall at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 3 days 22 hours is how long the current world has been running.
Lists and tags
What do the server tags on Error mean?
These are the tags Error publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp5 (Max players): The server has 5 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Error appear?
The Rust Server Trends lists that take in Error are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How to join
What steps get you onto Error?
You can connect by pressing F1 in Rust and typing client.connect 78.10.176.214:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.