On the class lists: C− (59), with population over 48 hours and no performance mark.
Players now0/ ?
7-day average0peak –
Rank#15,423top 69%
Last wipe25d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
unmarked
–
No weekly average to mark yet.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,423 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: 107 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
49/ 100
D
Slipped a little: down 250 places this week. Nothing a good wipe can't fix.
A steady term.
Strongest in performance (A+); standing 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 2 Oct. 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, and #529 of the trio servers (top 84%). Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 18:53 UTC25d ago
1
–
running
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
You'll find no region listed by RS|2x|Staging. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 94.130.131.25:28012.
Is RS|2x|Staging up, and how steady is its uptime?
Right now, RS|2x|Staging is online. According to its reported uptime, the last restart was about 20 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Is RS|2x|Staging smooth to play on?
It averaged 107 server fps over the last 48 hours, with a low of 73. Up to 72,471 entities were in the world, covering buildings, deployables and the rest. Up to 2,971 MB of memory was used. When fps is low and entities climb, that is lag to players.
On what Rust version does RS|2x|Staging sit?
The server RS|2x|Staging is on Rust network protocol 2634 and build 166655 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does RS|2x|Staging reset?
The record holds too few of RS|2x|Staging's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 25 days 10 hours have passed since this world was made.
What should you expect from wipe day on RS|2x|Staging?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 1 hours into the latest wipe.
Player numbers
Where does RS|2x|Staging place in the wider field of Rust servers?
Over the last seven days, RS|2x|Staging has #15,423 for player hours, in the top 69% of all ranked servers. In the trio group, it ranks #529.
What does the population on RS|2x|Staging look like?
The current population of RS|2x|Staging is 0 players. A seven-day average of 0 players applies here.
Tags and filters
What is meant by the tags on RS|2x|Staging?
gmvanilla (Game mode): You play vanilla survival here; mp0 (Max players): 0 slots are available; ts3 (Group limit): Teams cap out at 3; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166655 (Build): This runs on build 166655; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here are the tags RS|2x|Staging publishes, and the game's server browser reads them. 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 RS|2x|Staging?
Rust Server Score lists that include RS|2x|Staging: 2x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: Trio; Gather rate: 2x.
Rules and settings
How is RS|2x|Staging set up, and what rules does it keep?
The name of RS|2x|Staging points to a 2x gather rate. The cap on group size is 3 players (trio). It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map RS|2x|Staging uses?
RS|2x|Staging runs a game-generated procedural map at size 3,500, seed 471471404. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: RS-Maps.
Getting in
How should you connect to RS|2x|Staging?
To connect, start Rust, press F1, and type client.connect 94.130.131.25:28012. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2634,gmvanilla,cs166655,ts3,^z,^y
Game
gmvanilla
Game modeYou play vanilla survival here.
mp0
Max players0 slots are available.
ts3
Group limitTeams cap out at 3.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166655
BuildThis runs on build 166655.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonCarbon provides the plugin framework here.
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+); standing is the one to work on (F).