Offline 78.10.176.214:28015 checked 4d ago
Error
Connect
srv = rust.server("78.10.176.214:28016")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 best
srv.rank.plot(invert=True) # 1 is best
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 19:43 UTC4d ago | 1 | NaN | running | 0 |
| 1 | Thu 8 Oct, 18:51 UTC20d ago | 0 | NaN | 16 days | 1 |
| 2 | Sat 26 Sep, 15:27 UTC32d ago | 1 | held half | 12.1 days | 0 |
# 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 152 on average | 43/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 48/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 17/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 1/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 4/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Error rank?
Player hours over seven days put Error at #13,807, in the top 62% of the ranked set.
How full does Error run?
Error returns no live count at this refresh, having last been seen 4 days 3 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
About the server
What Rust version does Error run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Error. The protocol has to match before you can join, and Steam does the updating.
How reliable is Error, and is it online now?
The latest sample has Error offline, with a last sighting 4 days 3 hours ago. Over the last 7 full days the hours up number 3 of 168, 2%. Its earliest recorded date in Rust Data is 25 September 2026.
Where does Error sit?
There is no region published for Error. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 78.10.176.214:28015.
Settings and map
What rules and settings are recorded for Error?
You will not find a gather rate in the string Error. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Error selected?
The game generates its map: procedural, on Error.
Wipes and dates
On what schedule does Error wipe?
No next wipe can be predicted for Error, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 4 days 5 hours ago.
On Error, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 5 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Lists and tags
Where does Error appear among Rust Data lists and filters?
These Rust Data lists include Error: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on Error?
Read by the game's server browser, the tags Error publishes are: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): Slot count: 5; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into Error?
Enter client.connect 78.10.176.214:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.