SOLO_Новосибирск | WIPE 10.10
Key statistics
the figures behind the quote- Players now
- 0/ 50 0% full
- Change · 24h
- ▪+0 no reading a day ago
- 7-day average
- 0 peak 2
- Rank
- #6,330 top 29%
- Rank · 7d ago
- #9,341 ▲3011 places up
- Last wipe
- 5d ago biweekly schedule
- Next wipe
- 8d 20h Fri 23 Oct, 18:11 UTC
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 25 player hours, last seven days
- Map
- 3000 Procedural Map · seed 50000
- First seen
- 13 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 1 players.
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 29% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tag- usual gap
- 5.3 days between real wipes
- on rhythm
- 0% of its recent wipes
- wipe-day peak
- 1 players, last three wipes
- crowd held
- 33% else halves by day 5
Coming wipes
- 8d 20hFri 23 Oct, 18:11 UTC
- 21d 21hThu 5 Nov, 19:00 UTCFW
- 22d 20hFri 6 Nov, 18:11 UTC
- 36d 20hFri 20 Nov, 18:11 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 17 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 9 Oct, 18:11 UTC5d ago | 2 | – | running | 1 |
| Thu 1 Oct, 18:07 UTC FW13d ago | 1 | halved by day 1 | 8 days | 0 |
| Thu 1 Oct, 05:31 UTC13d ago | 1 | – | 0.5 days | 0 |
| Thu 17 Sep, 00:02 UTC27d ago | 1 | halved by day 9 | 14.2 days | 0 |
| Mon 14 Sep, 11:24 UTC30d 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | СЛАБЫЕ РЫЦАРИ X1|Vanilla+|NoBPWipe|02.10EU · groups of 50+ · 1x · biweekly · 7 on average | 1/200 | ▪+0+0.0% | |
| 2 | RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮEU · groups of 8+ · biweekly · 5 on average | 2/200 | ▪+0+0.0% | |
| 3 | 35+ВЗРОСЛЫЙ RUSTx2 MAINEU · groups of 8+ · biweekly · 5 on average | 2/125 | ▲+1+100.0% | |
| 4 | РЕЛАКС #2 Х2|Для новичков| No LimitEU · groups of 10+ · biweekly · 3 on average | 1/200 | ▼−1−40.0% | |
| 5 | #1 [RU] РУССКИЙ КЛАССИКА R7ZONE.RUEU · groups of 10+ · biweekly · 3 on average | 0/300 | ▪+0 | |
| 6 | ▶ DRAGON RUST X1 | УютныйEU · groups of 8+ · 1x · biweekly · 2 on average | 2/500 | ▲+1+100.0% |
Quick answers
from the figures on this pageServer Rules
How is SOLO_Новосибирск | WIPE 10.10 configured in terms of rules and settings?
No gather rate appears in the name of SOLO_Новосибирск | WIPE 10.10. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are in use. VAC, Valve's anti-cheat, is enabled.
Which map is played on SOLO_Новосибирск | WIPE 10.10?
SOLO_Новосибирск | WIPE 10.10 uses a procedural map of size 3,000 with seed 50000, generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page.
Population
What position does SOLO_Новосибирск | WIPE 10.10 hold in the server rankings?
In the top 29% of all ranked servers, SOLO_Новосибирск | WIPE 10.10 is #6,330 on player hours over the last seven days.
How full is SOLO_Новосибирск | WIPE 10.10?
0 of 50 slots on SOLO_Новосибирск | WIPE 10.10 are filled right now. The mean over the last seven days is 0 players, reaching 2 at its highest. Over the last 48 hours, the peak hour was 15:00 UTC, averaging 1 players.
Wipe Frequency
What can you expect on wipe day for SOLO_Новосибирск | WIPE 10.10?
Recent wipes at this server drew an average peak of 1 players. 17 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 33% of the time. The crowd fell below half by day 5 when it did not hold.
When does SOLO_Новосибирск | WIPE 10.10 schedule its wipes?
The prediction follows the tag because too few of SOLO_Новосибирск | WIPE 10.10's wipes are on record to confirm its schedule. The date of its next wipe is Friday 23 October at 18:11 UTC. 5 days 2 hours ago the current world was created. The tags show wipes every two weeks.
Server Details
What is the location of SOLO_Новосибирск | WIPE 10.10?
Its name points to Europe, but SOLO_Новосибирск | WIPE 10.10 publishes no region tag. Rust Analytics reports the location a server claims, not the machine's actual location. 212.20.40.180:28015 is its address.
What is the performance like on SOLO_Новосибирск | WIPE 10.10?
Server fps over the last 48 hours: 230 on average, 216 at the lowest. The entity count reached 49,386, covering buildings, deployables and all else in the world. The memory ceiling reached 3,122 MB. Low fps and growing entities are the source of felt lag.
What Rust version is SOLO_Новосибирск | WIPE 10.10 running?
The version in use at SOLO_Новосибирск | WIPE 10.10: Rust network protocol 2634 and build 167398, on Linux. Joining requires the same protocol on your game, which Steam updates.
What is the uptime and reliability of SOLO_Новосибирск | WIPE 10.10?
Online at this moment: SOLO_Новосибирск | WIPE 10.10. Its own uptime figure dates the last restart to roughly 2 days 4 hours ago. 95% is its uptime for the last 7 full days, 159 of 168 hours. First sighting by Rust Analytics: 13 September 2026.
Server Tags
How should you interpret the tags on SOLO_Новосибирск | WIPE 10.10?
The game's server browser reads gmvanilla (Game mode): The vanilla survival ruleset; mp50 (Max players): Capacity: 50 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs167398 (Build): It runs build 167398; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): No region code has been set; ^b (Biweekly): Two-week wipe cycle; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Modded listing: the game is changed by plugins or settings; jp0 (Custom tag): The owner or a plugin added this; it is not part of the standard Rust tag set, which SOLO_Новосибирск | WIPE 10.10 publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Where does SOLO_Новосибирск | WIPE 10.10 show up in Rust Analytics lists and filters?
On Rust Analytics, SOLO_Новосибирск | WIPE 10.10 matches these lists: Rust servers: Europe 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 week.
How to Join
What is the process to join SOLO_Новосибирск | WIPE 10.10?
The console route: start Rust, press F1, enter client.connect 212.20.40.180:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp50,ptrak,jp0,$r?,v2634,^b,gmvanilla,cs167398,ts8,^o^z
Game
gmvanilla
mp50
ts8
v2634
cs167398
ptrak
$r?
Wipe schedule
^b
Mods and access
^o
^z
Other
jp0
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.