Working its way up from the back of the class: #15,333 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
20/ 100
F
Lost ground: down 9,272 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in wipe hold (A+); momentum 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.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 20 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 83% in NA, and #378 of the duo servers (top 90%). Ranked on player hours over the last seven days.
Attendance: the wipe record
10 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·W···
·W·W···
·W·W···
·W·W···
·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 Thursday 5 November, 19:00 UTC, in 7d 5h.
The force wipe · high confidence
usual gap3 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held100%of its cycles kept half the crowd
Coming wipes
7d 5hThu 5 Nov, 19:00 UTCFW
13d 10hThu 12 Nov, 00:08 UTC
20d 10hThu 19 Nov, 00:08 UTC
27d 10hThu 26 Nov, 00:08 UTC
35d 5hThu 3 Dec, 19:00 UTCFW
41d 10hThu 10 Dec, 00:08 UTC
The first 48 hours of its last wipes
Thu 15 OctTue 13 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 4, 47 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 00:08 UTC14d ago
4
–
running
0
Tue 13 Oct, 00:04 UTC16d ago
2
✓ held half
2 days
0
Thu 8 Oct, 00:05 UTC21d ago
1
✓ held half
5 days
0
Tue 6 Oct, 00:04 UTC23d ago
1
✓ held half
2 days
0
Thu 1 Oct, 00:04 UTC28d ago
0
–
5 days
0
Tue 29 Sep, 00:05 UTC30d ago
2
✓ held half
2 days
0
Thu 24 Sep, 00:05 UTC35d ago
4
halved by day 3
5 days
0
Tue 22 Sep, 00:05 UTC37d ago
5
✓ held half
2 days
0
Thu 17 Sep, 23:02 UTC41d ago
0
–
4 days
0
Thu 17 Sep, 00:04 UTC42d ago
2
–
1 days
0
Tue 15 Sep, 00:06 UTC44d ago
3
✓ held half
2 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
Which region is US | PipeSlug | 2x solo duo | small one grid | 1 Grid based in?
You'll see US | PipeSlug | 2x solo duo | small one grid | 1 Grid listed in North America, tagged NA. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 66.51.99.23:28000.
Is US | PipeSlug | 2x solo duo | small one grid | 1 Grid up, and how steady is its uptime?
The server is down: US | PipeSlug | 2x solo duo | small one grid | 1 Grid is offline now, with the last sighting 9 days 13 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does US | PipeSlug | 2x solo duo | small one grid | 1 Grid sit?
Rust network protocol 2634 and build 167781 on Linux is what US | PipeSlug | 2x solo duo | small one grid | 1 Grid runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does US | PipeSlug | 2x solo duo | small one grid | 1 Grid wipe, and how often?
Its tag sets the prediction, as the record holds too few of US | PipeSlug | 2x solo duo | small one grid | 1 Grid's wipes to confirm its schedule. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. It has been running its current world for 14 days 13 hours. The tags carry a weekly wipe schedule.
What happens on US | PipeSlug | 2x solo duo | small one grid | 1 Grid when wipe day arrives?
Recent wipes have peaked at 2 players on average. 47 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 100% of its recent wipes.
Player count
Where does US | PipeSlug | 2x solo duo | small one grid | 1 Grid place in the wider field of Rust servers?
Over the last seven days, US | PipeSlug | 2x solo duo | small one grid | 1 Grid has #15,333 for player hours, in the top 69% of all ranked servers and #1,550 in North America. It comes #378 among servers in the duo group.
What does the population on US | PipeSlug | 2x solo duo | small one grid | 1 Grid look like?
US | PipeSlug | 2x solo duo | small one grid | 1 Grid is offline at the moment; the last time it was seen was 9 days 13 hours ago.
Lists and filters
How should you read the tags on US | PipeSlug | 2x solo duo | small one grid | 1 Grid?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; ts2 (Group limit): A team can hold 2 players at most; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; 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; ^w (Weekly): Wipes come once a week; ^i (Battlefield): High rates and kits keep the PvP fast; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): In the server browser it appears under North America are the tags US | PipeSlug | 2x solo duo | small one grid | 1 Grid 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 | PipeSlug | 2x solo duo | small one grid | 1 Grid?
These Rust Server Score lists count US | PipeSlug | 2x solo duo | small one grid | 1 Grid among them: 2x Rust servers, graded, Duo servers, marked like a report, Modded Rust servers, graded, Rust battlefield servers, graded and North America Rust servers, graded. You can find it under these server-list filters: Region: North America; Type: Modded; Server tag: Weekly ^w, Battlefield ^i, Modded ^z and Oxide ^o; Group limit: Duo; Wipe schedule: Weekly; Gather rate: 2x.
Map and rules
What settings and rules apply on US | PipeSlug | 2x solo duo | small one grid | 1 Grid?
Going by its name, US | PipeSlug | 2x solo duo | small one grid | 1 Grid runs 2x gather. The cap on group size is 2 players (duo). You get battlefield here, high rates and kits, for fast PvP. 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.
US | PipeSlug | 2x solo duo | small one grid | 1 Grid runs which map?
The game generates the procedural map on US | PipeSlug | 2x solo duo | small one grid | 1 Grid at size 1,350 with seed 1337. 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: Custom Map.
Getting in
What is the way to join US | PipeSlug | 2x solo duo | small one grid | 1 Grid?
Enter client.connect 66.51.99.23:28000 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://discord.com/invite/G3BRG2ssFX.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^w,^i,NA,gmrust,cs167781,ts2,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
ts2
Group limitA team can hold 2 players at most.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
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
^w
WeeklyWipes come once a week.
Gameplay
^i
BattlefieldHigh rates and kits keep the PvP fast.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
NA
North AmericaIn the server browser it appears 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 wipe hold (A+); momentum is the one to work on (F).