Pacific Drive Integration - Local Test
Offline 72.251.219.62:28115 checked 12d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
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
the same kind of game, then region, group limit, rate and wipes- 209/500
- 129/100
- 187/225
- 32/200
- 196/700
- 61/1000
Quick answers
from the figures on this pageReset cycle
When does Pacific Drive Integration - Local Test wipe?
The rhythm of Pacific Drive Integration - Local Test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 14 days 19 hours ago the current world was made.
Lists and filters
How should you read the tags on Pacific Drive Integration - Local Test?
These are the tags Pacific Drive Integration - Local Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): 2 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167584 (Build): Build 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does Pacific Drive Integration - Local Test appear in Rust Metrics lists and filters?
Rust Metrics lists featuring Pacific Drive Integration - Local Test: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
What position does Pacific Drive Integration - Local Test hold among Rust servers?
Player hours over seven days put Pacific Drive Integration - Local Test at #15,195, in the top 70% of all ranked servers.
How full does Pacific Drive Integration - Local Test get?
Status for Pacific Drive Integration - Local Test: offline. Last seen 12 days 21 hours ago.
Server
What location is Pacific Drive Integration - Local Test hosted in?
No region comes from Pacific Drive Integration - Local Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 72.251.219.62:28115.
What Rust version is Pacific Drive Integration - Local Test on?
Rust network protocol 2634 and build 167584 on Windows is the build Pacific Drive Integration - Local Test runs. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on Pacific Drive Integration - Local Test, and is it online?
Reading: offline. Pacific Drive Integration - Local Test last answered 12 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 14 October 2026.
Rules and settings
What settings and rules apply on Pacific Drive Integration - Local Test?
No gather rate appears in the name: Pacific Drive Integration - Local Test. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC off, Valve's system.
Which map is live on Pacific Drive Integration - Local Test?
Check: map. Procedural, generated by the game, on Pacific Drive Integration - Local Test.
Join
How can you get onto Pacific Drive Integration - Local Test?
To join: start Rust, press F1 and type client.connect 72.251.219.62:28115. Or press Launch Rust here and Steam opens the game and connects you.