Station XX-15212 · no signal
Pacific Drive Integration - Local Test
Offline 72.251.219.88:28115 checked 15d ago
- Players now
- 0/ 2
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,212
- top 70%
- Last wipe
- 16d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 2 slots
- Motion · 24 h
- M –not enough readings
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 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Pacific Drive Integration - Local Test?
Pacific Drive Integration - Local Test uses a procedural map, which the game generates.
Which settings and rules apply on Pacific Drive Integration - Local Test?
No gather rate appears in the name of Pacific Drive Integration - Local Test. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. The server has VAC off, Valve's anti-cheat.
Player counts
What is the current population on Pacific Drive Integration - Local Test?
Pacific Drive Integration - Local Test is not responding at this moment and is offline, last seen 15 days ago.
How does Pacific Drive Integration - Local Test rank against other Rust servers?
The last seven days of player hours place Pacific Drive Integration - Local Test at #15,212, in the top 70% of all ranked servers.
Server facts
How reliably does Pacific Drive Integration - Local Test stay online?
Pacific Drive Integration - Local Test is down at the moment; the last recorded contact was 15 days ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 12 October 2026 is when Rust Server Trends first recorded it.
Which region does Pacific Drive Integration - Local Test run from?
Nothing about a region comes from Pacific Drive Integration - Local Test. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 72.251.219.88:28115.
What build of Rust does Pacific Drive Integration - Local Test use?
Pacific Drive Integration - Local Test is running Rust network protocol 2634 and build 167584 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
How often does Pacific Drive Integration - Local Test wipe, and on which days?
On record so far are too few of Pacific Drive Integration - Local Test's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 16 days 13 hours.
Tags
What do the server tags on Pacific Drive Integration - Local Test mean?
These are the tags Pacific Drive Integration - Local Test publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp2 (Max players): The server has 2 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167584 (Build): Game build: 167584; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Pacific Drive Integration - Local Test appear?
You will find Pacific Drive Integration - Local Test on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
What steps get you onto Pacific Drive Integration - Local Test?
Enter client.connect 72.251.219.88:28115 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.