Online 212.20.40.180:28015 checked 10m ago
SOLO_Новосибирск | WIPE 29.10
Connect
srv = rust.server("212.20.40.180:28017")
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, measured since 17 Sep. 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 bestTop 42% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 17h | Thu 12 Nov, 00:04 UTC | wipe |
| 2 | 27d 17h | Thu 26 Nov, 00:04 UTC | wipe |
| 3 | 35d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 41d 17h | Thu 10 Dec, 00:04 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 14 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 29 Oct, 00:04 UTC6h ago | NaN | NaN | running | 0 |
| 1 | Thu 15 Oct, 00:04 UTC14d ago | 2 | halved by day 1 | 14 days | 0 |
| 2 | Fri 9 Oct, 18:11 UTC19d ago | 2 | held half | 5.2 days | 1 |
| 3 | Thu 1 Oct, 18:07 UTC FW27d ago | 1 | halved by day 1 | 8 days | 0 |
| 4 | Thu 1 Oct, 05:31 UTC28d ago | 1 | NaN | 0.5 days | 0 |
| 5 | Thu 17 Sep, 00:02 UTC42d ago | 1 | halved by day 9 | 14.2 days | 0 |
| 6 | Mon 14 Sep, 11:24 UTC44d ago | 3 | held half | 2.5 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
3000 · seed 6630
- map
- Procedural Map
- size
- 3000
- seed
- 6630
Server
srv.info()- address
- 212.20.40.180:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 29 Oct 2026, 00:04 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10 | EU · groups of 50+ · biweekly · 9 on average | 3/200 |
| 1 | RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ | EU · groups of 8+ · biweekly · 8 on average | 5/200 |
| 2 | [ESP][PVE] PACIFIC WORLD (WIPED 15/10/2026) | EU · groups of 16+ · biweekly · 4 on average | 0/50 |
| 3 | #1 [RU] РУССКИЙ КЛАССИКА R7ZONE.RU | EU · groups of 10+ · biweekly · 3 on average | 1/300 |
| 4 | [EU][UK][HUN] Rust Hungary PVE/PVP OFFICIAL | EU · groups of 8+ · biweekly · 2 on average | 0/50 |
| 5 | PurrRust|РУССКИЙ ДЛЯ НОВИЧКОВ|Vanilla2x|27.10 | EU · groups of 8+ · biweekly · 2 on average | 2/80 |
Quick answers
From the figures on this page.
Population
What position does SOLO_Новосибирск | WIPE 29.10 take in the server rankings?
Player hours over seven days put SOLO_Новосибирск | WIPE 29.10 at #9,259, in the top 42% of the ranked set.
How many players does SOLO_Новосибирск | WIPE 29.10 hold at once?
Current row: 0 players on SOLO_Новосибирск | WIPE 29.10, against 50 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 08:00 UTC is the busiest, at 0 players.
Server facts
What does performance look like on SOLO_Новосибирск | WIPE 29.10?
Averaged over 48 hours: 228 server fps, never under 194. Entity numbers reached 44,901, and that includes buildings, deployables and the rest. The memory field tops out at 2,980 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is SOLO_Новосибирск | WIPE 29.10 on?
Version Rust network protocol 2635 and build 168909 on Linux is reported by SOLO_Новосибирск | WIPE 29.10. The protocol has to match before you can join, and Steam does the updating.
Is SOLO_Новосибирск | WIPE 29.10 up, and what does its uptime show?
Online is the state at the latest refresh for SOLO_Новосибирск | WIPE 29.10. The uptime it reports puts the last restart about 4 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. Rust Data logged it first on 13 September 2026.
Where does SOLO_Новосибирск | WIPE 29.10 sit?
The name of SOLO_Новосибирск | WIPE 29.10 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.20.40.180:28015 is its address.
Map and rules
Which settings and rules does SOLO_Новосибирск | WIPE 29.10 run?
The name SOLO_Новосибирск | WIPE 29.10 carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has SOLO_Новосибирск | WIPE 29.10 selected?
Size 3,000, seed 6630: the procedural map on SOLO_Новосибирск | WIPE 29.10, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
On what schedule does SOLO_Новосибирск | WIPE 29.10 wipe?
The tag sets the prediction: SOLO_Новосибирск | WIPE 29.10 has too few wipes on record to confirm its schedule. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 6 hours ago, and that is the one in play. The tags list a two-weekly wipe cycle.
What is wipe day on SOLO_Новосибирск | WIPE 29.10 like?
Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 14 hours in. Recent wipes kept the crowd above half the peak until the next wipe 25% of the time. In the wipes where it did not hold, half was lost by day 1.
Tags, lists
Which Rust Data filters and lists contain SOLO_Новосибирск | WIPE 29.10?
The Rust Data lists that SOLO_Новосибирск | WIPE 29.10 fits are: EU Rust servers and Modded Rust servers. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.
How should you read the server tags on SOLO_Новосибирск | WIPE 29.10?
These tags are published by SOLO_Новосибирск | WIPE 29.10 and read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): The cycle is fourteen days; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game; jp0 (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into SOLO_Новосибирск | WIPE 29.10?
Enter client.connect 212.20.40.180:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.