Offline 72.251.219.88:28115 checked 15d ago
Pacific Drive Integration - Local Test
Connect
srv = rust.server("72.251.219.88:28117")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 72.251.219.88:28115
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 23:32 UTC
- hostname
- –
- first seen
- 12 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 154/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 98/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 239/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Pacific Drive Integration - Local Test rank?
Rank #15,212 on seven-day player hours for Pacific Drive Integration - Local Test, within the top 70% of all ranked servers.
How many players does Pacific Drive Integration - Local Test hold at once?
The current row shows Pacific Drive Integration - Local Test offline; the last response was 15 days 4 hours ago.
Server facts
What Rust version does Pacific Drive Integration - Local Test run?
The build is Rust network protocol 2634 and build 167584 on Windows, run by Pacific Drive Integration - Local Test. The protocol has to match before you can join, and Steam does the updating.
How reliable is Pacific Drive Integration - Local Test, and is it up?
Offline now for Pacific Drive Integration - Local Test, last seen 15 days 4 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 12 October 2026.
Where does Pacific Drive Integration - Local Test sit?
For Pacific Drive Integration - Local Test, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 72.251.219.88:28115.
Settings and map
Which settings and rules does Pacific Drive Integration - Local Test run?
No gather rate appears in the name: Pacific Drive Integration - Local Test. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. The VAC field reads off.
What is the map on Pacific Drive Integration - Local Test?
The game generates its map: procedural, on Pacific Drive Integration - Local Test.
Wipes and dates
When does Pacific Drive Integration - Local Test wipe, and how often?
Too few wipes are on record for Pacific Drive Integration - Local Test to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 16 days 17 hours ago.
Tags, lists
Which lists on Rust Data hold Pacific Drive Integration - Local Test, and which filters?
On Rust Data, Pacific Drive Integration - Local Test appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Pacific Drive Integration - Local Test?
Read by the game's server browser, the tags Pacific Drive Integration - Local Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): Slot count: 2; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167584 (Build): Recorded game build: 167584; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into Pacific Drive Integration - Local Test?
The manual route: launch Rust, F1, then client.connect 72.251.219.88:28115. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.