A12/ 200 players
Modded#6,533
SOLO_Новосибирск | WIPE 10.10
Online 212.20.40.180:28015 checked 9m ago
biweekly wipes
moddedoxide
players now0of 50 slots
7-day average0peak 2
rank#6,533top 29%
last wipe · restocked4d agobiweekly schedule
next wipe · restock9d 4hFri 23 Oct, 18:11 UTC
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 bestRankRank in region
Top 29% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Friday 23 October, 18:11 UTC, in 9d 4h. Its biweekly schedule tag · low confidence
5.3 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
1wipe-day peakplayers, last three wipes
33%crowd heldelse halves by day 5
Coming wipes
- 9d 4hFri 23 Oct, 18:11 UTC
- 22d 4hThu 5 Nov, 19:00 UTCFW
- 23d 4hFri 6 Nov, 18:11 UTC
- 37d 4hFri 20 Nov, 18:11 UTC
The first 48 hours of its last wipes
Fri 9 OctThu 1 OctThu 1 Oct
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 UTC4d ago | 2 | – | running | 1 |
| Thu 1 Oct, 18:07 UTC FW12d 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.
Also on the shelf
Similar servers
The same kind of game, then region, group limit, rate and wipes.
A21/ 125 players
A35/ 200 players
B11/ 200 players
B21/ 300 players
B31/ 500 players
On the back of the pack
Quick answers
From the figures on this page.
Tags & lists
Can you explain the tags on SOLO_Новосибирск | WIPE 10.10?
Here are the tags SOLO_Новосибирск | WIPE 10.10 lists, which the game's browser uses: gmvanilla (Game mode): Vanilla survival mode; mp50 (Max players): The cap is 50; ts8 (Group limit): 8 to a team, as the game ships it; v2634 (Protocol): Protocol 2634: your game must match to get in; cs167398 (Build): It runs on build 167398; ptrak (Networking): Network runs on RakNet, the game's standard; $r? (Region code): Region code not set; ^b (Biweekly): Two-week wipe cycle; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): It sits in Modded: plugins or settings make the difference; jp0 (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. Tags also carry its current players, its queue and when the world was made, all up top on this page.
Where does SOLO_Новосибирск | WIPE 10.10 appear in the lists and filters on Rust Vending Machine?
These Rust Vending Machine lists include SOLO_Новосибирск | WIPE 10.10: EU Rust servers in stock 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.
Map and rules
Which map is currently on SOLO_Новосибирск | WIPE 10.10?
The map on SOLO_Новосибирск | WIPE 10.10 is procedural, size 3,000 with seed 50000, generated by the game. The map is the same for a given size and seed, so RustMaps can show it from this page.
What rules does SOLO_Новосибирск | WIPE 10.10 enforce, and what settings does it run?
The name of SOLO_Новосибирск | WIPE 10.10 gives no gather rate. Groups can reach 8 players, which is the default. This server runs survival, gather, build, raid: the standard game. You can fight and raid other players. Plugins or settings change the game, so it is listed under Modded. The plugins it runs number Oxide. VAC is on.
Server details
What location is SOLO_Новосибирск | WIPE 10.10 in?
No region tag comes from SOLO_Новосибирск | WIPE 10.10, but the name suggests Europe. A server's stated location is what Rust Vending Machine shows; the actual machine location is not looked up. Find it at this address: 212.20.40.180:28015.
How reliable is SOLO_Новосибирск | WIPE 10.10, and is it online now?
You can grab SOLO_Новосибирск | WIPE 10.10: it is online as we speak. The uptime counter points to a restart about 44 hours ago. 159 of 168 hours online over the last 7 full days, or 95% uptime. It came to Rust Vending Machine's notice on 13 September 2026.
Is SOLO_Новосибирск | WIPE 10.10 lag-free?
Over the last 48 hours the average server fps was 231, with a low of 216. At its peak it held 49,373 entities, counting buildings, deployables and all else in the world. At most it drew 2,866 MB of memory. Lag, as players feel it, is low fps plus a growing entity count.
What Rust version does SOLO_Новосибирск | WIPE 10.10 run?
On Linux, SOLO_Новосибирск | WIPE 10.10 is running Rust network protocol 2634 and build 167398. The protocol has to line up on your side to join, and Steam does the updating.
Population
Where does SOLO_Новосибирск | WIPE 10.10 sit in the rankings?
The last seven days of player hours place SOLO_Новосибирск | WIPE 10.10 at #6,533, in the top 29% of all ranked servers.
Is SOLO_Новосибирск | WIPE 10.10 busy at the moment?
Right now 50 slots in SOLO_Новосибирск | WIPE 10.10 hold 0 players. The seven-day average stands at 0 players, peaking at 2. The last 48 hours peaked at 15:00 UTC, when it averaged 1 players.
Wipe info
When does SOLO_Новосибирск | WIPE 10.10 wipe?
Too few wipes of SOLO_Новосибирск | WIPE 10.10 are recorded to confirm its schedule, so its tag decides the prediction. Friday 23 October at 18:11 UTC is when its next wipe falls due. 4 days 18 hours ago it made the world it is using now. A wipe every two weeks is published in its tags.
What can you expect on SOLO_Новосибирск | WIPE 10.10 when wipe day comes?
The average busiest point of its recent wipes was 1 players. On the latest wipe, 17 hours after it began, the crowd peaked. Until the next wipe, in 33% of recent wipes, the crowd remained above half that peak. The crowd fell under half by day 5 in the wipes that did not hold.
How to join
What is the way to join SOLO_Новосибирск | WIPE 10.10?
In the Rust console (F1), type client.connect 212.20.40.180:28015. You can also press Launch Rust on this page, which opens Steam and connects.
Server tags
what each one meansPublished as mp50,ptrak,jp0,$r?,v2634,^b,gmvanilla,cs167398,ts8,^o^z
Game
gmvanilla
Game mode Vanilla survival mode.
mp50
Max players The cap is 50.
ts8
Group limit 8 to a team, as the game ships it.
v2634
Protocol Protocol 2634: your game must match to get in.
cs167398
Build It runs on build 167398.
ptrak
Networking Network runs on RakNet, the game's standard.
$r?
Region code Region code not set.
Wipe schedule
^b
Biweekly Two-week wipe cycle.
Mods and access
^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded It sits in Modded: plugins or settings make the difference.
Other
jp0
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.
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.