A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
57/ 100
C−
Working its way up from the back of the class: #9,648 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
42/ 100
F
Needs to work on its frame rate: 25 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
79/ 100
B
Climbing fast: up 5,525 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 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 43% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
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.
usual gap15.6 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 2
The first 48 hours of its last wipes
Mon 12 OctSun 27 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 12 Oct, 21:32 UTC16d ago
0
–
running
0
Sun 27 Sep, 06:17 UTC31d ago
4
halved by day 2
15.6 days
1
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 won't find a region tag on US | 2x |DEVELOPEMENT|, but its name indicates North America. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 104.143.2.118:29015.
How reliable is US | 2x |DEVELOPEMENT|, and is it up?
Right now, US | 2x |DEVELOPEMENT| is online. According to its reported uptime, the last restart was about 9 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 27 September 2026.
How well does US | 2x |DEVELOPEMENT| run?
It averaged 25 server fps over the last 48 hours, with a low of 25. At its peak, it held 74,234 entities, including buildings, deployables and all else in the world. Memory use reached up to 2,014 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is US | 2x |DEVELOPEMENT| running?
You will find US | 2x |DEVELOPEMENT| on Rust network protocol 2635 and build 168909, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does US | 2x |DEVELOPEMENT| wipe, and how often?
There are too few wipes on record for US | 2x |DEVELOPEMENT| to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 16 days 2 hours.
What should you expect from wipe day on US | 2x |DEVELOPEMENT|?
Across its recent wipes, the busiest moments averaged 2 players. 0 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to 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.
Player count
Where does US | 2x |DEVELOPEMENT| sit among Rust servers?
Over the last seven days, US | 2x |DEVELOPEMENT| has #9,648 for player hours, in the top 43% of all ranked servers.
How many players does US | 2x |DEVELOPEMENT| usually have?
With 100 slots available, US | 2x |DEVELOPEMENT| currently has 0 players. It peaked at 2 and averaged 0 players over the last seven days.
Lists and filters
What do US | 2x |DEVELOPEMENT|'s tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; 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; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags US | 2x |DEVELOPEMENT| publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show US | 2x |DEVELOPEMENT|?
Rust Server Score lists that include US | 2x |DEVELOPEMENT|: 2x Rust servers, graded, Modded Rust servers, graded and North America Rust servers, graded. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.
Map and rules
Which rules does US | 2x |DEVELOPEMENT| enforce, and what are its settings?
Going by its name, US | 2x |DEVELOPEMENT| runs 2x gather. The group limit stays at the game's default of 8 players. You get survival here, 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 Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on US | 2x |DEVELOPEMENT|?
US | 2x |DEVELOPEMENT| runs a game-generated procedural map at size 3,750, seed 33333. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: SCRAPLAND.GG.
Connecting
How should you connect to US | 2x |DEVELOPEMENT|?
To connect, start Rust, press F1, and type client.connect 104.143.2.118:29015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
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.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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).