On the class lists: C− (56), with population over 48 hours and no performance mark.
Players now17/ 2008% full
7-day average41peak 202
Rank#394top 2%
Last wipe4d agoweekly schedule
Next wipe2d 14hFri 30 Oct, 08:55 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
21/ 100
F
A quiet classroom so far: 41 of 200 on average. Plenty of space to grow.
Standingrank on player hours
98/ 100
A+
Well up the rankings: #394 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 126 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
71/ 100
B−
Climbing fast: up 162 places this week.
A steady term.
Strongest in performance (A+); wipes are 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.
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 best
RankRank in region
Top 2% 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··
····W··
····W··
····W··
····W··
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Friday 30 October, 08:55 UTC, in 2d 14h.
Every Friday at 08:55 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak172players, last three wipes
crowd held0%else halves by day 2
Coming wipes
2d 14hFri 30 Oct, 08:55 UTC
9d 0hThu 5 Nov, 19:00 UTCFW
9d 14hFri 6 Nov, 08:55 UTC
16d 14hFri 13 Nov, 08:55 UTC
23d 14hFri 20 Nov, 08:55 UTC
30d 14hFri 27 Nov, 08:55 UTC
37d 0hThu 3 Dec, 19:00 UTCFW
37d 14hFri 4 Dec, 08:55 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 202, 9 hours in, with 20 in the queue.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 08:55 UTC4d ago
202+20 queue
–
running
9
Fri 16 Oct, 08:56 UTC11d ago
144+34 queue
halved by day 3
7 days
7
Fri 9 Oct, 08:59 UTC18d ago
170
halved by day 3
7 days
1
Fri 2 Oct, 08:55 UTC25d ago
105
halved by day 2
7 days
2
Fri 25 Sep, 08:55 UTC32d ago
224+15 queue
halved by day 2
7 days
4
Fri 18 Sep, 08:55 UTC39d ago
407+62 queue
halved by day 2
7 days
5
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
EU · groups of 300+ · 2x · weekly · 125 on average
56 / 150
Quick answers
from the figures on this page
Server facts
Which region is Новосибирск | Main 2x based in?
No region tag appears for Новосибирск | Main 2x, but the name suggests Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 80.242.59.73:35001.
Is Новосибирск | Main 2x up, and how steady is its uptime?
You can join now: Новосибирск | Main 2x is online. According to its reported uptime, the last restart was about 16 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does Новосибирск | Main 2x perform well?
It never fell below 121 server fps in the last 48 hours, averaging 126. At its peak, it held 138,308 entities, including buildings, deployables and all else in the world. At its highest, it used 5,349 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does Новосибирск | Main 2x sit?
You will find Новосибирск | Main 2x on Rust network protocol 2635 and build 168909, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does Новосибирск | Main 2x reset?
The wipe rhythm on Новосибирск | Main 2x is every Friday at 08:55 UTC. It is due to wipe next on Friday 30 October at 08:55 UTC. The world it runs now was created 4 days 9 hours. The tags carry a weekly wipe schedule.
What happens on Новосибирск | Main 2x when wipe day arrives?
The average peak on its recent wipes was 172 players. 9 hours after the latest wipe began the crowd peaked, and 20 more were in the queue. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 2 in the wipes where it did not hold.
Population
What position does Новосибирск | Main 2x hold in the rankings?
In the top 2% of all ranked servers, Новосибирск | Main 2x sits at #394 for player hours over the last seven days.
What does the population on Новосибирск | Main 2x look like?
With 200 slots available, Новосибирск | Main 2x currently has 17 players. The seven-day average is 41 players, with a peak of 202. Over the last 48 hours, the peak hour was 19:00 UTC, averaging 62 players.
Lists and filters
What is meant by the tags on Новосибирск | Main 2x?
You'll see Новосибирск | Main 2x tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp200 (Max players): 200 slots are available; ts64 (Group limit): No team may go above 64; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^w (Weekly): A wipe happens every week; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^t (Tutorial on): Facepunch's tutorial gives new players a starting point here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; rustmaps (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. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Who is behind Новосибирск | Main 2x?
A rustnitro.ru hostname is published by Новосибирск | Main 2x and by 4 other tracked servers, which suggests one operator.
Which lists and filters on Rust Server Score show Новосибирск | Main 2x?
These Rust Server Score lists count Новосибирск | Main 2x among them: Rust tutorial servers, graded, 2x Rust servers, graded, European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Tutorial on ^t, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x; Players now: At least 10; Average players: 25+ on average.
Map and rules
How is Новосибирск | Main 2x set up, and what rules does it keep?
Новосибирск | Main 2x sets gather at 2x, as its name suggests. You can play in groups of up to 64 players. survival is the mode here, gather and build and raid: 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. The plugin count runs to Oxide. Vanilla is what it calls itself: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Новосибирск | Main 2x uses?
The map on Новосибирск | Main 2x is custom at size 3,850, and because the file is published you can download it from this page.
Getting in
How should you connect to Новосибирск | Main 2x?
To connect, start Rust, press F1, and type client.connect 80.242.59.73:35001. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://nitro.gamestores.app.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2635,^w,^v,^t,gmrust,cs168909,ts64,^o^z,rustmaps
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp200
Max players200 slots are available.
ts64
Group limitNo team may go above 64.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Gameplay
^t
Tutorial onFacepunch's tutorial gives new players a starting point here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
rustmaps
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.
A steady term. Strongest in performance (A+); wipes are the one to work on (F).