Offline 212.22.93.163:28014 checked 13d ago
Error Rust X2/X5 - еженедельный | UP| remove | loot
Connect
srv = rust.server("212.22.93.163:28015")
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 23h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 23h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 23h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 24 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 9 Oct, 11:18 UTC20d ago | 4 | NaN | running | 0 |
| 1 | Fri 2 Oct, 06:40 UTC27d ago | 6 | halved by day 6 | 7.2 days | 1 |
| 2 | Thu 1 Oct, 19:11 UTC FW28d ago | 6 | NaN | 0.5 days | 1 |
| 3 | Fri 25 Sep, 11:08 UTC34d ago | 2 | held half | 6.3 days | 1 |
| 4 | Fri 18 Sep, 11:09 UTC41d ago | 2 | held half | 7 days | 0 |
| 5 | Fri 18 Sep, 01:39 UTC41d ago | 2 | NaN | 0.4 days | 1 |
| 6 | Wed 16 Sep, 06:22 UTC43d ago | 2 | NaN | 1.8 days | 1 |
# 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
- 212.22.93.163:28014
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 9 Oct 2026, 11:18 UTC
- hostname
- –
- first seen
- 16 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 | Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 825 on average | 677/800 |
| 1 | Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 609 on average | 1594/1600 |
| 2 | EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 349 on average | 833/850 |
| 3 | Vitality - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 294 on average | 1068/1200 |
| 4 | EU Limitless 2x Monthly Main | No BP Wipes | x2 | EU · groups of 12+ · 2x · monthly · 280 on average | 324/345 |
| 5 | MIRAGE RUST | MONTHLY 2x | VANILLA+ | Wipe 01.10 | EU · groups of 300+ · 2x · monthly · 142 on average | 107/500 |
Quick answers
From the figures on this page.
Player counts
How does Error Rust X2/X5 - еженедельный | UP| remove | loot compare in the rankings?
Rank #15,133 on seven-day player hours for Error Rust X2/X5 - еженедельный | UP| remove | loot, within the top 70% of all ranked servers.
How full does Error Rust X2/X5 - еженедельный | UP| remove | loot run?
Offline now for Error Rust X2/X5 - еженедельный | UP| remove | loot, with the last sample 13 days 16 hours ago.
Server facts
Which Rust version is Error Rust X2/X5 - еженедельный | UP| remove | loot on?
Rust network protocol 2634 and build 167398 on Windows is what Error Rust X2/X5 - еженедельный | UP| remove | loot runs. The protocol has to match before you can join, and Steam does the updating.
Is Error Rust X2/X5 - еженедельный | UP| remove | loot up, and what does its uptime show?
Error Rust X2/X5 - еженедельный | UP| remove | loot is offline at this refresh; the last response came 13 days 16 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 16 September 2026.
Where does Error Rust X2/X5 - еженедельный | UP| remove | loot sit?
The name of Error Rust X2/X5 - еженедельный | UP| remove | loot points to Europe, even though no region tag is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 212.22.93.163:28014 is its address.
Settings and map
What rules and settings are recorded for Error Rust X2/X5 - еженедельный | UP| remove | loot?
2x gather is what the name states, and the name is Error Rust X2/X5 - еженедельный | UP| remove | loot. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has Error Rust X2/X5 - еженедельный | UP| remove | loot loaded?
Error Rust X2/X5 - еженедельный | UP| remove | loot runs a procedural map, which the game generates.
Wipe data
When does Error Rust X2/X5 - еженедельный | UP| remove | loot wipe, and how often?
Once a month Error Rust X2/X5 - еженедельный | UP| remove | loot wipes, with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 20 days 8 hours ago. The tags list wipes as monthly.
On Error Rust X2/X5 - еженедельный | UP| remove | loot, what happens on wipe day?
Recent wipes averaged 5 players at their peak. Peak population on the latest wipe came 24 hours in. Recent wipes kept the crowd above half the peak until the next wipe 67% of the time. Otherwise the crowd fell below half by day 6.
Lists and tags
Which Rust Data filters and lists contain Error Rust X2/X5 - еженедельный | UP| remove | loot?
The Rust Data lists that Error Rust X2/X5 - еженедельный | UP| remove | loot fits are: EU Rust servers, Modded Rust servers and 2x Rust servers. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
How should you read the server tags on Error Rust X2/X5 - еженедельный | UP| remove | loot?
These tags are published by Error Rust X2/X5 - еженедельный | UP| remove | loot and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join Error Rust X2/X5 - еженедельный | UP| remove | loot?
Enter client.connect 212.22.93.163:28014 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.