Pacific Drive Integration - Local Test
Offline 72.251.219.62:28115 checked 3d ago
Players
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 72% 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
- 17/ 100
- 296/ 400
- 189/ 225
- 134/ 100
- 389/ 1000
- 35/ 700
Quick answers
Tags and filters
Where does Pacific Drive Integration - Local Test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Pacific Drive Integration - Local Test: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the tags on Pacific Drive Integration - Local Test?
The server browser shows these tags for Pacific Drive Integration - Local Test: gmrust (Game mode): This is the standard Rust survival experience; mp2 (Max players): It holds 2 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167584 (Build): This server runs build 167584; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What location is Pacific Drive Integration - Local Test in?
Pacific Drive Integration - Local Test does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 72.251.219.62:28115.
Is Pacific Drive Integration - Local Test up, and how often does it stay online?
Right now Pacific Drive Integration - Local Test is offline, having last been seen 3 days 13 hours ago. It was up 0% of the time over the last full 3 days, 0 of 72 hours. The first sighting by Rust Going Deep was on 14 October 2026.
What Rust version is Pacific Drive Integration - Local Test on?
Rust network protocol 2634 and build 167584 is what Pacific Drive Integration - Local Test runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
When does Pacific Drive Integration - Local Test wipe?
Too few wipes are on record for Pacific Drive Integration - Local Test to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 5 days 11 hours ago.
Map and rules
What settings and rules have been applied to Pacific Drive Integration - Local Test?
Its name does not state a gather rate for Pacific Drive Integration - Local Test. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. VAC is off: Valve's anti-cheat is not active.
What's the map on Pacific Drive Integration - Local Test?
A procedural map, generated by the game, is in play on Pacific Drive Integration - Local Test.
Player count
Is Pacific Drive Integration - Local Test busy?
Right now Pacific Drive Integration - Local Test is offline, with its last appearance 3 days 13 hours ago. Across the last seven days, the typical count has been 0 players.
Where does Pacific Drive Integration - Local Test sit in the rankings?
Over the last seven days, Pacific Drive Integration - Local Test is #15,807 by player hours, among the top 72% of all ranked servers.
How to join
What's the process to join Pacific Drive Integration - Local Test?
Open Rust and press F1, then type client.connect 72.251.219.62:28115. Alternatively, click Launch Rust on this page to join via Steam.