On the class lists: C (62), with population over 48 hours and no performance mark.
Players now5/ 757% full
7-day average4peak 25
Rank#1,478top 7% · #224 in NA
Last wipe2d agoweekly schedule
Next wipe4d 3hMon 2 Nov, 19:57 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
6/ 100
F
A quiet classroom so far: 4 of 75 on average. Plenty of space to grow.
Standingrank on player hours
93/ 100
A
Well up the rankings: #1,478 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
50/ 100
D
Slows down under load at times: 30 server fps on average.
Wipeskeeping the crowd after a wipe
60/ 100
C
Keeps a fair share of its players through a wipe: 60% of wipes kept half their crowd.
Momentumrank now against a week ago
54/ 100
D
Moving up: up 117 places this week.
A fair term, with more to come.
Strongest in uptime (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.
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 7% of all ranked servers, top 12% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
8 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
W······
W··F···
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 Monday 2 November, 19:57 UTC, in 4d 3h.
Every Monday at 19:57 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak17players, last three wipes
crowd held60%else halves by day 3
Coming wipes
4d 3hMon 2 Nov, 19:57 UTC
7d 2hThu 5 Nov, 19:00 UTCFW
11d 3hMon 9 Nov, 19:57 UTC
18d 3hMon 16 Nov, 19:57 UTC
25d 3hMon 23 Nov, 19:57 UTC
32d 3hMon 30 Nov, 19:57 UTC
35d 2hThu 3 Dec, 19:00 UTCFW
39d 3hMon 7 Dec, 19:57 UTC
The first 48 hours of its last wipes
Mon 26 OctMon 19 OctMon 12 Oct
Players each hour, from the hour of the wipe. The latest peaked at 25, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 19:57 UTC2d ago
25
–
running
5
Mon 19 Oct, 19:57 UTC9d ago
18
halved by day 3
7 days
3
Mon 12 Oct, 19:57 UTC16d ago
9
✓ held half
7 days
2
Mon 5 Oct, 19:57 UTC23d ago
6
✓ held half
7 days
0
Thu 1 Oct, 17:59 UTCFW27d ago
9
halved by day 3
4.1 days
3
Mon 28 Sep, 19:57 UTC30d ago
8
✓ held half
2.9 days
1
Mon 21 Sep, 19:57 UTC37d ago
14
halved by day 1
7 days
1
Mon 14 Sep, 19:57 UTC44d ago
10
✓ held half
7 days
2
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
Which region is [NA] Winterust - 2x Mondays based in?
You'll see [NA] Winterust - 2x Mondays listed in North America, tagged NA. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 94.231.215.8:28015.
How reliable is [NA] Winterust - 2x Mondays, and is it up?
You can join now: [NA] Winterust - 2x Mondays is online. The uptime it reports puts the last restart at about 7 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Is [NA] Winterust - 2x Mondays smooth to play on?
It averaged 30 server fps over the last 48 hours, with a low of 30. At its peak, it held 74,770 entities, including buildings, deployables and all else in the world. Memory use reached up to 4,276 MB. Players feel lag when fps drops and entities pile up.
What Rust version is [NA] Winterust - 2x Mondays on?
You will find [NA] Winterust - 2x Mondays on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does [NA] Winterust - 2x Mondays wipe, and how often?
The wipe rhythm on [NA] Winterust - 2x Mondays is every Monday at 19:57 UTC. It is due to wipe next on Monday 2 November at 19:57 UTC. The world it runs now was created 2 days 20 hours. Its tags state that it wipes weekly.
What happens on [NA] Winterust - 2x Mondays when wipe day arrives?
Across its recent wipes, the busiest moments averaged 17 players. The crowd on the latest wipe was largest 5 hours after it began. Above half the peak until the next wipe: that was the pattern in 60% of its recent wipes. The crowd dropped below half by day 3 in the wipes where it did not hold.
Population
Where does [NA] Winterust - 2x Mondays sit among Rust servers?
In North America, [NA] Winterust - 2x Mondays is #224, and overall it is #1,478 on player hours over the last seven days, in the top 7% of all ranked servers.
What does the population on [NA] Winterust - 2x Mondays look like?
With 75 slots available, [NA] Winterust - 2x Mondays currently has 5 players. The seven-day average is 4 players, with a peak of 25. Over the last 48 hours, the peak hour was 20:00 UTC, averaging 14 players.
Tags
What do [NA] Winterust - 2x Mondays's tags stand for?
The game's browser takes its cue from the tags [NA] Winterust - 2x Mondays has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp75 (Max players): Its slot count is 75; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): It wipes weekly; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; NA (North America): The server browser lists it under North America; oxidation (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which person or group runs [NA] Winterust - 2x Mondays?
A winterust.net hostname is published by [NA] Winterust - 2x Mondays and by 7 other tracked servers, which suggests one operator.
Which lists and filters on Rust Server Score show [NA] Winterust - 2x Mondays?
Rust Server Score lists that include [NA] Winterust - 2x Mondays: 2x Rust servers, graded, Modded Rust servers, graded and North America Rust servers, graded. It shows under the following filters on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 3 days; Gather rate: 2x.
Map and rules
What settings and rules apply on [NA] Winterust - 2x Mondays?
[NA] Winterust - 2x Mondays sets gather at 2x, as its name suggests. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in 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. The server runs Valve's anti-cheat, VAC.
Which map is in play on [NA] Winterust - 2x Mondays?
A procedural map of size 4,500 and seed 2445, generated by the game, is what [NA] Winterust - 2x Mondays runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: The Official Home of Ser Winter.
How to join
How should you connect to [NA] Winterust - 2x Mondays?
Enter client.connect 94.231.215.8:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://winterust.net/.
Server tags
what each one means
Published asmp75,ptrak,$r?,v2635,^w,NA,gmrust,cs168909,ts8,^o^z,oxidation
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp75
Max playersIts slot count is 75.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
NA
North AmericaThe server browser lists it under North America.
Other
oxidation
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 fair term, with more to come. Strongest in uptime (A+); population is the one to work on (F).