On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,270top 69% · #1491 in NA
Last wipe27d agobiweekly schedule
Next wipe21hSat 31 Oct, 03:01 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 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,270 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
9/ 100
F
Needs to work on its frame rate: 5 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
50/ 100
D
Holding steady: down 91 places this week.
A term to build on.
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 3 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, top 80% in NA, and #505 of the trio servers (top 81%). Ranked on player hours over the last seven days.
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
Next wipe Saturday 31 October, 03:01 UTC, in 21h.
Biweekly: 14 days after its last 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
Which region is [US] Reventless 2X | Solo/Duo/Trio | based in?
You'll see [US] Reventless 2X | Solo/Duo/Trio | listed in North America, tagged NA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 66.51.96.87:28010 is the address to use.
How reliable is [US] Reventless 2X | Solo/Duo/Trio |, and is it up?
The server is up: [US] Reventless 2X | Solo/Duo/Trio | is online now. About 7 days 11 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 3 October 2026.
Is [US] Reventless 2X | Solo/Duo/Trio | smooth to play on?
It never fell below 5 server fps in the last 48 hours, averaging 5. At its peak, it held 28,451 entities, including buildings, deployables and all else in the world. Up to 2,051 MB of memory was used. When fps is low and entities climb, that is lag to players.
On what Rust version does [US] Reventless 2X | Solo/Duo/Trio | sit?
The server [US] Reventless 2X | Solo/Duo/Trio | is on Rust network protocol 2634 and build 167781 under Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does [US] Reventless 2X | Solo/Duo/Trio | reset?
The next wipe on [US] Reventless 2X | Solo/Duo/Trio | is a projection from biweekly: 14 days after its last wipe. Expect the next wipe on Saturday 31 October at 03:01 UTC. It has been running its current world for 27 days 2 hours. A fortnightly wipe schedule appears in its tags.
Player numbers
Where does [US] Reventless 2X | Solo/Duo/Trio | place in the wider field of Rust servers?
Over the last seven days, [US] Reventless 2X | Solo/Duo/Trio | has #15,270 for player hours, in the top 69% of all ranked servers and #1,491 in North America. It comes #505 among servers in the trio group.
Is [US] Reventless 2X | Solo/Duo/Trio | a busy server?
With 50 slots available, [US] Reventless 2X | Solo/Duo/Trio | currently has 0 players. Over the past seven days, the average player count was 0.
Lists and filters
What do [US] Reventless 2X | Solo/Duo/Trio |'s tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts3 (Group limit): Teams cap out at 3; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^j (Battle royale): Gather loot and battle while the zone tightens; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): The server browser lists it under North America are the tags [US] Reventless 2X | Solo/Duo/Trio | 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.
Where does [US] Reventless 2X | Solo/Duo/Trio | appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [US] Reventless 2X | Solo/Duo/Trio | 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: Biweekly ^b, Battle royale ^j, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Every two weeks; Gather rate: 2x.
Rules and settings
What settings and rules apply on [US] Reventless 2X | Solo/Duo/Trio |?
The name of [US] Reventless 2X | Solo/Duo/Trio | points to a 2x gather rate. The cap on group size is 3 players (trio). minigames & battle royale is the mode here, parkour, arenas, battle royale and Bedwars. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
[US] Reventless 2X | Solo/Duo/Trio | runs which map?
[US] Reventless 2X | Solo/Duo/Trio | runs a game-generated procedural map at size 2,000, seed 1. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto [US] Reventless 2X | Solo/Duo/Trio |?
To connect, start Rust, press F1, and type client.connect 66.51.96.87:28010. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^b,^j,NA,gmrust,cs167781,ts3,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts3
Group limitTeams cap out at 3.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Gameplay
^j
Battle royaleGather loot and battle while the zone tightens.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
NA
North AmericaThe server browser lists it under North America.
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 uptime (A+); population is the one to work on (F).