Working its way up from the back of the class: #15,212 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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
21/ 100
F
Lost ground: down 8,736 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
In what location does Pacific Drive Integration - Local Test sit?
No region is published for Pacific Drive Integration - Local Test. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 72.251.219.88:28115.
How dependable is Pacific Drive Integration - Local Test, and is it online at the moment?
At this moment, Pacific Drive Integration - Local Test is offline; the last time it was seen was 13 days 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 12 October 2026.
On what Rust version does Pacific Drive Integration - Local Test sit?
Rust network protocol 2634 and build 167584 on Windows is what Pacific Drive Integration - Local Test runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does Pacific Drive Integration - Local Test wipe, and how often?
Pacific Drive Integration - Local Test has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 14 days 19 hours.
Population
Where does Pacific Drive Integration - Local Test sit among Rust servers?
In the top 70% of all ranked servers, Pacific Drive Integration - Local Test sits at #15,212 for player hours over the last seven days.
What does the population on Pacific Drive Integration - Local Test look like?
It has been 13 days 6 hours since Pacific Drive Integration - Local Test was last seen, and it is offline right now.
Tags
What do Pacific Drive Integration - Local Test's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): Its slot count is 2; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167584 (Build): This runs on build 167584; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags Pacific Drive Integration - Local Test publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Pacific Drive Integration - Local Test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Pacific Drive Integration - Local Test among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Pacific Drive Integration - Local Test?
The name of Pacific Drive Integration - Local Test gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server does not run VAC, Valve's anti-cheat.
Pacific Drive Integration - Local Test runs which map?
A procedural map, generated by the game, is what Pacific Drive Integration - Local Test runs.
Getting in
How do you get onto Pacific Drive Integration - Local Test?
To connect, start Rust, press F1, and type client.connect 72.251.219.88:28115. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp2,ptrak,$r?,v2634,gmrust,cs167584,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp2
Max playersIts slot count is 2.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167584
BuildThis runs on build 167584.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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. Even marks across the subjects, from F to F.