Station XX-15195 · no signal
Pacific Drive Integration - Local Test
Offline 72.251.219.62:28115 checked 14d ago
- Players now
- 0/ 2
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,195
- 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 pageMap and rules
Which map is running on Pacific Drive Integration - Local Test?
A procedural map runs on Pacific Drive Integration - Local Test, generated by the game.
Which settings and rules apply on Pacific Drive Integration - Local Test?
The name of Pacific Drive Integration - Local Test gives no gather rate. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched off.
Population
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 14 days 20 hours 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,195, in the top 70% of all ranked servers.
Server facts
How reliably does Pacific Drive Integration - Local Test stay online?
No contact with Pacific Drive Integration - Local Test right now, and the last recorded contact was 14 days 20 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 14 October 2026 is when Rust Server Trends first recorded it.
Where in the world is Pacific Drive Integration - Local Test hosted?
A region is not published by Pacific Drive Integration - Local Test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 72.251.219.62:28115.
Which Rust version is Pacific Drive Integration - Local Test running?
On Windows, Pacific Drive Integration - Local Test runs Rust network protocol 2634 and build 167584. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
On what timetable does Pacific Drive Integration - Local Test run its wipes?
Too few wipes of Pacific Drive Integration - Local Test are on record yet to show its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 16 days 18 hours is how long the current world has been running.
Server 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): Teams max out at 8, the default set by the game; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167584 (Build): It runs game build 167584; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Pacific Drive Integration - Local Test appear?
The Rust Server Trends lists that take in Pacific Drive Integration - Local Test are: 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.
How to join
How do you connect to Pacific Drive Integration - Local Test?
To join, enter client.connect 72.251.219.62:28115 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.