Rust Data

rustdata.spaceservers167.160.93.164:28017.ipynb

Run all rust-data · live

‹ All servers

Online 167.160.93.164:28015 checked 9m ago

Pinzgauer`s PVE Server

Connect

srv = rust.server("167.160.93.164:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/100 # 1% full
7-day average 0 # peak 1
rank #7,214 # top 33%
last wipe 1h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75123:0008:0017:0003:0012:0021:00Wiped Tue 27 Oct, 21:02 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
025507510023:0008:0017:0003:0012:0021:00Wiped Tue 27 Oct, 21:02 UTCWIPE

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, measured since 17 Sep. 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 best
RankRank in region
15k10k15k20k20 Sep23 Sep25 Sep28 Sep30 Sep27 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sun 25 OctSun 25 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 21:02 UTC1h ago NaN NaN running 0
1 Sun 25 Oct, 12:02 UTC2d ago 1 held half 2.4 days 0
2 Sun 25 Oct, 02:07 UTC2d ago 1 NaN 0.4 days 0

# 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

4000 · seed 453818
Map of Pinzgauer`s PVE Server
map
Procedural Map
size
4000
seed
453818
Open on RustMaps

Server

srv.info()
address
167.160.93.164:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
27 Oct 2026, 21:02 UTC
hostname
–
first seen
13 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 511 on average577/625
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 340 on average32/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 337 on average73/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 316 on average290/325
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average114/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 261 on average120/150

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Pinzgauer`s PVE Server rank?

Player hours over seven days put Pinzgauer`s PVE Server at #7,214, in the top 33% of the ranked set.

What population does Pinzgauer`s PVE Server carry?

The sample now reads 1 players for Pinzgauer`s PVE Server, out of 100 slots. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 01:00 UTC, averaging 1 players.

Server facts

What does performance look like on Pinzgauer`s PVE Server?

The 48-hour average is 75 server fps, with a low of 46. Buildings, deployables and all else in the world took the count as high as 94,340 entities. A high of 2,406 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on Pinzgauer`s PVE Server?

Rust network protocol 2635 and build 168909 on Windows is what Pinzgauer`s PVE Server runs. Joining needs the same protocol on your game; Steam handles the update.

Is Pinzgauer`s PVE Server up, and what does its uptime show?

The current sample puts Pinzgauer`s PVE Server online. A restart about 9 minutes ago is what its reported uptime implies. Uptime of 27% across the last 7 full days: 46 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is Pinzgauer`s PVE Server hosted?

No region is published by Pinzgauer`s PVE Server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 167.160.93.164:28015 is its address.

Map and rules

Which rules apply on Pinzgauer`s PVE Server, and what settings?

No gather rate appears in the name: Pinzgauer`s PVE Server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has Pinzgauer`s PVE Server selected?

Pinzgauer`s PVE Server runs a procedural map of size 4,000 with seed 453818, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipe schedule

When does Pinzgauer`s PVE Server wipe, and how often?

No next wipe can be predicted for Pinzgauer`s PVE Server, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 1 hours ago, and that is the one in play.

What is wipe day on Pinzgauer`s PVE Server like?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

Tags and filters

Which lists on Rust Data hold Pinzgauer`s PVE Server, and which filters?

The Rust Data lists that Pinzgauer`s PVE Server fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 24 hours.

Which meanings do the tags on Pinzgauer`s PVE Server hold?

Read by the game's server browser, the tags Pinzgauer`s PVE Server publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

How to join

How can I connect to Pinzgauer`s PVE Server?

The manual route: launch Rust, F1, then client.connect 167.160.93.164:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players Slot count: 100.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

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.

Rust Data 63,914 players 11,774 servers online