Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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 13.09 sit?
You won't find a region tag on SOLO_Новосибирск | WIPE 13.09, but its name indicates Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 212.20.40.180:28015.
How reliable is SOLO_Новосибирск | WIPE 13.09, and is it up?
You cannot join now: SOLO_Новосибирск | WIPE 13.09 is offline, last seen 44 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 14 September 2026.
Which Rust version is SOLO_Новосибирск | WIPE 13.09 running?
Rust network protocol 2633 and build 163794 on Linux is what SOLO_Новосибирск | WIPE 13.09 runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
On what schedule does SOLO_Новосибирск | WIPE 13.09 reset?
SOLO_Новосибирск | WIPE 13.09 has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 44 days 19 hours have passed since this world was made.
Population
Where does SOLO_Новосибирск | WIPE 13.09 sit among Rust servers?
In the top – of all ranked servers, SOLO_Новосибирск | WIPE 13.09 sits at #15,049 for player hours over the last seven days.
How many players does SOLO_Новосибирск | WIPE 13.09 usually have?
The last sighting of SOLO_Новосибирск | WIPE 13.09 was 44 days 12 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on SOLO_Новосибирск | WIPE 13.09?
You'll see SOLO_Новосибирск | WIPE 13.09 tagged with gmrust (Game mode): Survival in the standard Rust style; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; jp0 (Custom tag): The owner or a plugin created this tag, so it is not standard Rust in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does SOLO_Новосибирск | WIPE 13.09 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count SOLO_Новосибирск | WIPE 13.09 among them: European Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does SOLO_Новосибирск | WIPE 13.09 enforce, and what are its settings?
Nothing in the name of SOLO_Новосибирск | WIPE 13.09 states a gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map SOLO_Новосибирск | WIPE 13.09 uses?
The game generates a procedural map for SOLO_Новосибирск | WIPE 13.09.
Connecting
How should you connect to SOLO_Новосибирск | WIPE 13.09?
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 asmp500,ptrak,jp0,$r?,v2633,gmrust,cs163794,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp500
Max playersThe server holds 500 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Other
jp0
Custom tagThe owner or a plugin created this tag, so it is not 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.
Not enough figures yet to write a report. Check back after a few days on the list.