On the class lists: D (45), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#10,166top 46%
Last wipe22h agobiweekly schedule
Next wipe6d 20hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
54/ 100
D
Working its way up from the back of the class: #10,166 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 228 server fps on average.
Wipeskeeping the crowd after a wipe
25/ 100
F
Needs to keep more players after wipe day: 25% of wipes kept half their crowd.
Momentumrank now against a week ago
50/ 100
D
Holding steady: down 10 places this week.
A term to build on.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 best
RankRank in region
Top 46% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W··W···
·······
···F···
····W··
···W···
·······
···W
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h.
The force wipe · high confidence
usual gap6.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held25%else halves by day 1
Coming wipes
6d 20hThu 5 Nov, 19:00 UTCFW
13d 1hThu 12 Nov, 00:04 UTC
27d 1hThu 26 Nov, 00:04 UTC
34d 20hThu 3 Dec, 19:00 UTCFW
41d 1hThu 10 Dec, 00:04 UTC
The first 48 hours of its last wipes
Thu 15 OctFri 9 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 14 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 29 Oct, 00:04 UTC22h ago
–
–
running
0
Thu 15 Oct, 00:04 UTC14d ago
2
halved by day 1
14 days
0
Fri 9 Oct, 18:11 UTC20d ago
2
✓ held half
5.2 days
1
Thu 1 Oct, 18:07 UTCFW28d ago
1
halved by day 1
8 days
0
Thu 1 Oct, 05:31 UTC28d ago
1
–
0.5 days
0
Thu 17 Sep, 00:02 UTC42d ago
1
halved by day 9
14.2 days
0
Mon 14 Sep, 11:24 UTC45d 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
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does SOLO_Новосибирск | WIPE 29.10 sit?
You won't find a region tag on SOLO_Новосибирск | WIPE 29.10, but its name indicates Europe. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 212.20.40.180:28015.
How reliable is SOLO_Новосибирск | WIPE 29.10, and is it up?
Right now, SOLO_Новосибирск | WIPE 29.10 is online. About 20 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Is SOLO_Новосибирск | WIPE 29.10 smooth to play on?
It averaged 228 server fps over the last 48 hours, with a low of 212. At its peak, it held 44,667 entities, including buildings, deployables and all else in the world. Up to 2,980 MB of memory was used. Players feel lag when fps drops and entities pile up.
On what Rust version does SOLO_Новосибирск | WIPE 29.10 sit?
The server SOLO_Новосибирск | WIPE 29.10 is on Rust network protocol 2635 and build 168909 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does SOLO_Новосибирск | WIPE 29.10 reset?
Its tag sets the prediction, as the record holds too few of SOLO_Новосибирск | WIPE 29.10's wipes to confirm its schedule. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 22 hours. Its tags give a wipe schedule of every two weeks.
What happens on SOLO_Новосибирск | WIPE 29.10 when wipe day arrives?
Recent wipes have peaked at 2 players on average. 14 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 25% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Player count
Where does SOLO_Новосибирск | WIPE 29.10 sit among Rust servers?
In the top 46% of all ranked servers, SOLO_Новосибирск | WIPE 29.10 sits at #10,166 for player hours over the last seven days.
How many players does SOLO_Новосибирск | WIPE 29.10 usually have?
SOLO_Новосибирск | WIPE 29.10 is showing 0 players right now, with 50 slots in total. It peaked at 1 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 10:00 UTC, with an average of 0 players.
Tags and filters
What is meant by the tags on SOLO_Новосибирск | WIPE 29.10?
You'll see SOLO_Новосибирск | WIPE 29.10 tagged with gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^b (Biweekly): Every two weeks it wipes; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; jp0 (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show SOLO_Новосибирск | WIPE 29.10?
These Rust Server Score lists count SOLO_Новосибирск | WIPE 29.10 among them: European Rust servers, graded and Modded Rust servers, graded. 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.
Rules and settings
Which rules does SOLO_Новосибирск | WIPE 29.10 enforce, and what are its settings?
You will find no gather rate in the name of SOLO_Новосибирск | WIPE 29.10. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map SOLO_Новосибирск | WIPE 29.10 uses?
A procedural map of size 3,000 and seed 6630, generated by the game, is what SOLO_Новосибирск | WIPE 29.10 runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to SOLO_Новосибирск | WIPE 29.10?
To connect, start Rust, press F1, and type client.connect 212.20.40.180:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,jp0,$r?,v2635,^b,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max players50 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
jp0
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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.
A term to build on. Strongest in performance (A+); population is the one to work on (F).