Statistical profileOffline
Error
78.10.176.214:28015 checked 4d ago
Connect to this server
1. Main points
Players now
0/ 5
0% full
7-day average
0
peak 1
Rank
#13,803
top 62%
Last wipe
4d ago
no schedule published
Next wipe
–
no rhythm it keeps
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 5 slots.
- Over the last seven days it averaged 0 players, with a peak of 1.
- It ranks #13,803 of all ranked servers, the top 62%, on player hours over the last seven days.
- Its current map went up 4d ago.
2. Players
Figure 1: Players on Error
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternno rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
Usual gap
14.1 days
between real wipes
On rhythm
100%
of its recent wipes
Wipe-day peak
1
players, last three wipes
Crowd held
100%
of its cycles kept half the crowd
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 5 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 24 Oct, 19:43 UTC4d ago | 1 | – | running | 0 |
| Thu 8 Oct, 18:51 UTC20d ago | 0 | – | 16 days | 1 |
| Sat 26 Sep, 15:27 UTC32d ago | 1 | held half | 12.1 days | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of Error
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of Error
What the server publishes and what was recorded
| Address | 78.10.176.214:28015 |
|---|---|
| Region | – |
| Max players | 5 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 24 Oct 2026, 23:59 UTC |
| Hostname | – |
| First seen | 25 Sep 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 149 on average | 181 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 172 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 85 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 176 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 237 / 700 |
10. Quick answers
From the figures on this page.
Wipe schedule
When does Error wipe, and how often?
Error wipes without a fixed interval, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world was generated 4 days 15 hours ago.
How is wipe day run on Error?
Recent wipes drew an average peak of 1 players. On the latest wipe, 5 hours passed before the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Server details
What does the record show for the uptime and current status of Error?
The latest count records Error as offline, last seen 4 days 13 hours ago. 3 of 168 hours on across the last 7 full days gives an uptime of 2%. First recorded by Rust Census on 25 September 2026.
What location has been recorded for Error?
No region is published by Error. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. 78.10.176.214:28015 is its address.
On which Rust version does Error operate?
The version in use on Error is Rust network protocol 2635 and build 168909 on Windows. To join, your game has to be on the same protocol; Steam handles the update.
Player figures
What are the current player figures for Error?
At this release Error is offline, having last been seen 4 days 13 hours ago. This release records a seven-day average of 0 players and a peak of 1.
How does Error compare with other servers in the rankings?
The rank for Error is #13,803 on seven-day player hours, in the top 62% of ranked servers.
Lists and tags
Which Rust Census filters and lists cover Error?
Included in these Rust Census lists is Error: Modded Rust servers, counted. It appears 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.
The tags on Error: what do they indicate?
These are the tags Error publishes for the game's server browser to read: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): Your game must run protocol 2635 to join; cs168909 (Build): Build 168909 is installed; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): A region code has not been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings. At the top of this page you will find the tags for current players, queue and world creation time.
Map and rules
Which map has been recorded for Error?
Error runs a procedural map, which the game generates.
What settings and rules have been listed for Error?
No gather rate is recorded for Error in its name. 8 players is the group limit, the game's default. It runs survival, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings alter the game. Oxide plugins are recorded on it. The server runs VAC, Valve's anti-cheat.
How to join
What is the way to join Error?
Enter client.connect 78.10.176.214:28015 in the console, opened with F1 after starting Rust; alternatively, Launch Rust on this page opens Rust through Steam and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp5,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp5 | Max players The server holds 5 slots. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol Your game must run protocol 2635 to join. |
cs168909 | Build Build 168909 is installed. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code A region code has not been set. |
Mods and access
^o | Oxide The plugin framework in use is Oxide (uMod). |
|---|---|
^z | Modded Modded: the game is changed by plugins or settings. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.