RUST ZERG LIFEClan war room · live
No limit8 · game default
Deployment dossierOnline

SOLO_Новосибирск | WIPE 10.10

212.20.40.180:28015 checked 11m ago

biweekly wipes moddedoxide
Deploy
Zerg meter0%empty
0/50 troops
7-day average0
peak 2
Rank#6,533
top 29%
Last wipe4d ago
biweekly schedule
Next wipe · H-hour9d 3h
Fri 23 Oct, 18:11 UTC

Players

AveragePeak
00.250.50.75115:0000:0009:0018:0003:0012:00

Hourly average and peak, UTC.

Server performance

010020030040015:0000:0009:0018:0003:0012:00

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
RankRank in region
15k10k15k20k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

Top 29% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag

Next wipe Friday 23 October, 18:11 UTC, in 9d 3h. Its biweekly schedule tag · low confidence

usual gap5.3 days
between real wipes
on rhythm0%
of its recent wipes
wipe-day peak1
players, last three wipes
crowd held33%
else halves by day 5

Coming wipes

9d 3hFri 23 Oct, 18:11 UTC
22d 4hThu 5 Nov, 19:00 UTCFW
23d 3hFri 6 Nov, 18:11 UTC
37d 3hFri 20 Nov, 18:11 UTC

The first 48 hours of its last wipes

Fri 9 OctThu 1 OctThu 1 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 17 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
Zergmax 50
СЛАБЫЕ РЫЦАРИ X1|Vanilla+|NoBPWipe|02.10 EU · groups of 50+ · 1x · biweekly · 7 on average
4/200
No limit8 · game default
35+ВЗРОСЛЫЙ RUSTx2 MAIN EU · groups of 8+ · biweekly · 6 on average
2/125
No limit8 · game default
RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ EU · groups of 8+ · biweekly · 5 on average
5/200
Zergmax 10
РЕЛАКС #2 Х2|Для новичков| No Limit EU · groups of 10+ · biweekly · 3 on average
1/200
Zergmax 10
#1 [RU] РУССКИЙ КЛАССИКА R7ZONE.RU EU · groups of 10+ · biweekly · 3 on average
0/300
No limit8 · game default
▶ DRAGON RUST X1 | Уютный EU · groups of 8+ · 1x · biweekly · 3 on average
1/500

Quick answers

from the figures on this page

Map and rules

Which settings and rules apply on SOLO_Новосибирск | WIPE 10.10?

You will not find a gather rate in the name SOLO_Новосибирск | WIPE 10.10. Up to 8 players can group, which is the game's default. It runs survival, gather, build and raid: the standard game. You can fight and raid other players here. The server browser lists it under Modded: the game is changed by plugins or settings. It runs plugins: Oxide. VAC is on, Valve's anti-cheat.

Which map is active on SOLO_Новосибирск | WIPE 10.10?

A procedural map, size 3,000 with seed 50000, generated by the game, is what SOLO_Новосибирск | WIPE 10.10 runs. You can view it on RustMaps from this page, since the same size and seed give the same map.

Server population

What is the population like on SOLO_Новосибирск | WIPE 10.10?

SOLO_Новосибирск | WIPE 10.10 has 0 of its 50 slots filled right now. The seven-day average is 0 players, with a peak of 2. The busiest time in the last 48 hours was 15:00 UTC, when it averaged 1 players.

What is SOLO_Новосибирск | WIPE 10.10's ranking?

In the top 29% of ranked servers, SOLO_Новосибирск | WIPE 10.10 holds #6,533 for player hours over the last seven days.

Tags and filters

What is the meaning of the tags on SOLO_Новосибирск | WIPE 10.10?

The game's server browser reads these tags from SOLO_Новосибирск | WIPE 10.10: gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): Capacity: 50; ts8 (Group limit): This uses the standard team limit of 8; v2634 (Protocol): To join, your game must match protocol 2634; cs167398 (Build): It runs build 167398; ptrak (Networking): The network layer is RakNet, which is standard; $r? (Region code): There's no region code here; ^b (Biweekly): The server wipes on a two-week cycle; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Modded category: the game is altered by plugins or settings; jp0 (Custom tag): The owner or a plugin set this tag; it's not part of standard Rust. The tags carry its players now, its queue and the time its world was made as well, and the top of this page displays them.

Where does SOLO_Новосибирск | WIPE 10.10 appear in Rust Zerg Life lists?

EU Rust servers for clans and Modded Rust servers for clans and zergs: that is where you will find SOLO_Новосибирск | WIPE 10.10 among the Rust Zerg Life rankings. Under these filters it shows 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.

Server info

What is the uptime and reliability of SOLO_Новосибирск | WIPE 10.10?

SOLO_Новосибирск | WIPE 10.10 is up and running as you read this. The uptime figure it gives suggests it restarted around 44 hours ago. Over the last 7 full days, uptime was 95%: 159 hours up out of 168. Rust Zerg Life has been tracking it since 13 September 2026.

What is the performance like on SOLO_Новосибирск | WIPE 10.10?

Server fps held an average of 231 for the last 48 hours, with a minimum of 216. It reached a maximum of 49,373 entities, covering buildings, deployables and the rest of the world. Memory use peaked at 2,866 MB. What players experience as lag comes from low fps and a rising entity count.

Which Rust build does SOLO_Новосибирск | WIPE 10.10 use?

On Linux, SOLO_Новосибирск | WIPE 10.10 runs Rust network protocol 2634 and build 167398. The protocol must match for you to join, and Steam will update your game to that protocol.

What location does SOLO_Новосибирск | WIPE 10.10 use?

Without a region tag from SOLO_Новосибирск | WIPE 10.10, its name still points to Europe. The location shown by Rust Zerg Life is what a server says; it does not check where the machine stands. Connect to it at 212.20.40.180:28015.

Wipe days

What happens on wipe day on SOLO_Новосибирск | WIPE 10.10?

At their busiest, its recent wipes drew an average of 1 players. 17 hours after the latest wipe, the crowd peaked. The crowd kept above half that peak until the next wipe in 33% of its recent wipes. Otherwise, it slipped below half by day 5.

How often does SOLO_Новосибирск | WIPE 10.10 wipe, and on what days?

The prediction follows its tag because not enough of SOLO_Новосибирск | WIPE 10.10's wipes are on record to confirm the schedule. It is due to wipe next on Friday 23 October at 18:11 UTC. The world in play right now was made 4 days 19 hours ago. The tags hold a fortnightly wipe schedule.

Connect

What steps do I take to join SOLO_Новосибирск | WIPE 10.10?

Enter client.connect 212.20.40.180:28015 in the F1 console. Another way: use Launch Rust on this page, which opens Rust through Steam and connects you.

Server tags

what each one means

Published as mp50,ptrak,jp0,$r?,v2634,^b,gmvanilla,cs167398,ts8,^o^z

Game

gmvanilla
Game mode This is vanilla survival.
mp50
Max players Capacity: 50.
ts8
Group limit This uses the standard team limit of 8.
v2634
Protocol To join, your game must match protocol 2634.
cs167398
Build It runs build 167398.
ptrak
Networking The network layer is RakNet, which is standard.
$r?
Region code There's no region code here.

Wipe schedule

^b
Biweekly The server wipes on a two-week cycle.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded Modded category: the game is altered by plugins or settings.

Other

jp0
Custom tag The owner or a plugin set this tag; it's not part of standard Rust.

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.