On the class lists: F (32), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,414top 69% · #1546 in NA
Last wipe10d agoweekly schedule
Next wipe3d 17hSat 31 Oct, 19:39 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,414 on player hours.
Uptimehours on the list, last 48
62/ 100
C
Missed a few lessons: on the list 30 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 209 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
37/ 100
F
Slipped a little: down 3,980 places this week. Nothing a good wipe can't fix.
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
No five-minute samples in the last two hours.
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 69% of all ranked servers, top 82% in NA, and #529 of the trio servers (top 84%). Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
···W···
···F···
···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 Saturday 31 October, 19:39 UTC, in 3d 17h.
Its weekly schedule tag · low confidence
usual gap7 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak0players, last three wipes
Coming wipes
3d 17hSat 31 Oct, 19:39 UTC
8d 17hThu 5 Nov, 19:00 UTCFW
10d 17hSat 7 Nov, 19:39 UTC
17d 17hSat 14 Nov, 19:39 UTC
24d 17hSat 21 Nov, 19:39 UTC
31d 17hSat 28 Nov, 19:39 UTC
36d 17hThu 3 Dec, 19:00 UTCFW
38d 17hSat 5 Dec, 19:39 UTC
The first 48 hours of its last wipes
Sat 17 OctThu 8 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 9 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 19:39 UTC10d ago
1
–
running
0
Thu 8 Oct, 18:35 UTC19d ago
0
–
9 days
0
Thu 1 Oct, 18:35 UTCFW26d ago
0
–
7 days
0
Thu 24 Sep, 18:35 UTC33d ago
0
–
7 days
0
Thu 17 Sep, 18:35 UTC40d ago
0
–
7 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
Where in the world is [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W?
In North America, according to its own listing, sits [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W, with the NA tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 31.56.20.102:28015.
Is [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W up, and how steady is its uptime?
The server is down: [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W is offline now, with the last sighting 18 hours ago. About 4 days 11 hours ago, it restarted, based on the uptime it reports. It was up 90% of the time over the last 7 full days, 152 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Does [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W perform well?
It averaged 209 server fps over the last 48 hours, with a low of 147. At its peak, it held 69,241 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,907 MB. Players feel lag when fps drops and entities pile up.
Which Rust version is [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W running?
You will find [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W on Rust network protocol 2634 and build 167781, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W wipe its map?
The prediction follows its tag, because too few of [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W's wipes are on record to confirm the schedule. Saturday 31 October at 19:39 UTC is the date set for its next wipe. The world it runs now was created 10 days 6 hours. Its tags state that it wipes weekly.
What should you expect from wipe day on [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W?
The average peak on its recent wipes was 0 players. 9 hours after the latest wipe began, the crowd hit its peak.
Population
Where does [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W place in the wider field of Rust servers?
Over the last seven days, [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W has #15,414 for player hours, in the top 69% of all ranked servers and #1,546 in North America. It comes #529 among servers in the trio group.
What does the population on [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W look like?
The last sighting of [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W was 18 hours ago, and it is offline right now. A seven-day average of 0 players applies here.
Lists and filters
How should you read the tags on [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W?
You'll see [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): 100 slots are available; ts3 (Group limit): A team can hold 3 players at most; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^w (Weekly): A wipe happens every week; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon; NA (North America): You will find it under North America in the browser 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 Rust Server Score filters and lists feature [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W?
These Rust Server Score lists count [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W among them: 2x Rust servers, graded, Modded Rust servers, graded, Rust servers with a trio group limit and North America Rust servers, graded. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 2 weeks; Gather rate: 2x.
Rules and settings
Which rules does [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W enforce, and what are its settings?
The name of [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W points to a 2x gather rate. You can have up to 3 players in a group (trio). survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W?
A procedural map of size 3,500 and seed 632248558, generated by the game, is what [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
What is the way to join [US] SECOND SHIFT 2X | SOLO/DUO/TRIO | WEEKLY | NO P2W?
To connect, start Rust, press F1, and type client.connect 31.56.20.102:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://playsecondshift.com.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^z,^y,^w,NA,gmrust,cs167781,ts3
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max players100 slots are available.
ts3
Group limitA team can hold 3 players at most.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonPlugin framework: Carbon.
Region
NA
North AmericaYou will find it under North America in the browser.
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).