Rust PopulationField survey · Rust servers
Observing 101,018 players 11,889 servers 3,946 with someone on 400 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 15,195habitat unknownfirst seen 14 Oct 2026

Pacific Drive Integration - Local Test

Offline 72.251.219.62:28115 checked 14d ago

moddedoxide

Measurements

Players now
0/ 2
0% full
7-day average
0
peak –
Rank
#15,195
top 70%
Last wipe
16d ago
no schedule published
Next wipe
–
no wipe seen yet
Obs. 1 · sightings

Players

No hourly history yet.

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k14 Oct15 Oct17 Oct18 Oct20 Oct21 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Obs. 4 · the wipe cycle

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Field questions

Quick answers

from the figures on this page

Player counts

How does Pacific Drive Integration - Local Test rank against other Rust servers?

By player hours over the last seven days, Pacific Drive Integration - Local Test places at #15,195, within the top 70% of ranked servers.

How busy is Pacific Drive Integration - Local Test?

Pacific Drive Integration - Local Test is offline at this count; we last saw it 14 days 19 hours ago.

Lists and tags

What do the server tags on Pacific Drive Integration - Local Test mean?

What the game's server browser reads from Pacific Drive Integration - Local Test is this set of tags: gmrust (Game mode): Survival in the standard Rust style; mp2 (Max players): The server has 2 slots; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): Your game needs the same version, protocol 2634, to join; cs167584 (Build): This server runs game build 167584; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): This server has no region code; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): This server appears under Modded because plugins or settings alter the game. You will see the player count, queue and world creation time at the top of this page, because the tags carry them too.

Which Rust Population lists and filters include Pacific Drive Integration - Local Test?

Pacific Drive Integration - Local Test appears among the Rust Population lists that follow: Modded Rust servers, counted. Look for it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Wipe schedule

What is the wipe schedule on Pacific Drive Integration - Local Test?

Too few wipes are on record for Pacific Drive Integration - Local Test to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The world it runs now dates from 16 days 17 hours ago.

Map and rules

Which map does Pacific Drive Integration - Local Test run?

The map on Pacific Drive Integration - Local Test is procedural, made by the game.

What are the rules and settings on Pacific Drive Integration - Local Test?

Nothing in Pacific Drive Integration - Local Test's name says how gather works. The group limit is 8 players, which is the default. This server runs survival, raid, build and gather: the standard game. You can raid and fight other players here. The server browser files it under Modded, where plugins or settings alter the game. The plugins it runs are Oxide. VAC, Valve's anti-cheat, is not running.

Server details

Which version of Rust does Pacific Drive Integration - Local Test run?

The setup is Rust network protocol 2634 and build 167584 on Windows for Pacific Drive Integration - Local Test. Steam updates your game automatically, but you need the same protocol to join.

Is Pacific Drive Integration - Local Test online, and how reliable is it?

Currently offline, Pacific Drive Integration - Local Test was last seen 14 days 19 hours ago. Over the last 7 full days, 0 of 168 hours were online, or 0%. It was first seen by Rust Population on 14 October 2026.

Where is Pacific Drive Integration - Local Test located?

A region is not published by Pacific Drive Integration - Local Test. Rust Population does not look up where the machine stands; it shows where the server says it is. 72.251.219.62:28115 is where it lives.

Getting in

How do I join Pacific Drive Integration - Local Test?

To connect directly, open Rust's console with F1 and type client.connect 72.251.219.62:28115; or press Launch Rust on this page and Steam opens Rust and joins for you.

Key to its markings

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs167584,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp2
Max players The server has 2 slots.
ts8
Group limit 8 per team is the default limit.
v2634
Protocol Your game needs the same version, protocol 2634, to join.
cs167584
Build This server runs game build 167584.
ptrak
Networking RakNet is the network layer here, as standard for the game.
$r?
Region code This server has no region code.

Mods and access

^o
Oxide Oxide (uMod) provides the plugin framework here.
^z
Modded This server appears under Modded because plugins or settings alter the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.