Pacific Drive Integration - Local Test
Offline 72.251.219.88:28115 checked 15d 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- 171/500
- 133/100
- 183/225
- 81/700
- 351/350
- 249/700
Quick answers
from the figures on this pageWipe timing
What wipe timing does Pacific Drive Integration - Local Test follow?
The rhythm of Pacific Drive Integration - Local Test's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 16 days 16 hours ago the current world was made.
Tags
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): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): Game build reading: 167584; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Pacific Drive Integration - Local Test?
Rust Metrics lists featuring Pacific Drive Integration - Local Test: Modded Rust servers, checked live. Reading: server list filters. It comes up under 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,212, in the top 70% of all ranked servers.
What player count does Pacific Drive Integration - Local Test carry?
Pacific Drive Integration - Local Test is not responding; status offline, last seen 15 days 3 hours ago.
Operator and location
Where does Pacific Drive Integration - Local Test sit?
No region tag on 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.88:28115.
What Rust version is Pacific Drive Integration - Local Test on?
Version check: Rust network protocol 2634 and build 167584 on Windows, run by Pacific Drive Integration - Local Test. 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 15 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 12 October 2026, recorded by Rust Metrics.
Map and rules
How is Pacific Drive Integration - Local Test configured, and what rules are in force?
Reading the name gives no gather rate for 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. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is off. That is Valve's anti-cheat.
Which map is live on Pacific Drive Integration - Local Test?
Procedural map on Pacific Drive Integration - Local Test, made by the game's generator.
How to join
How do you connect to Pacific Drive Integration - Local Test?
Press F1 in Rust and enter client.connect 72.251.219.88:28115. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.