StatusLive Servers online11,791 Players67,584 Populated3,634 Wiped · 3 h129 Interval5 min Date28 OCT 2026

DWG RG-S6596Server sheetchecked 9m ago

Pinzgauer`s PVE Server

Online 167.160.93.164:28015 checked 9m ago

Connect
Players now 0/ 100 0% full
7-day average0peak 1
Rank#6,596top 30%
Last wipe1d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeakWipe
00.250.50.75122:0007:0016:0001:0010:0020:00Wiped Tue 27 Oct, 21:02 UTCWIPE

Hourly average and peak, UTC.

Fig. 1Players on Pinzgauer`s PVE Server
Fig. 2

Server performance

Server fpsWipe
05010015020022:0007:0016:0001:0010:0020: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep23 Sep26 Sep28 Sep25 Oct28 Oct

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

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

no rhythm it keeps

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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 21:02 UTC1d ago – – running 0
Sun 25 Oct, 12:02 UTC3d ago 1 held half 2.4 days 0
Sun 25 Oct, 02:07 UTC3d ago 1 – 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 554 on average
501 / 575
02
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average
309 / 400
03
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 295 on average
41 / 250
04
Rustoria.co - EU MainEU · groups of 16+ · weekly · 294 on average
36 / 250
05
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 273 on average
85 / 150
06
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 252 on average
109 / 200
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

How reliable is Pinzgauer`s PVE Server, and is it online now?

Pinzgauer`s PVE Server is up at this moment. Counted from its reported uptime, the last restart was about 10 hours ago. 70 of 168 hours up over the last 7 full days, which is 42% of the time. First seen by Rust Graphs on 13 September 2026.

What does the recorded performance of Pinzgauer`s PVE Server show?

77 server fps on average over the last 48 hours, and never under 56. Counted at its highest: 99,071 entities, buildings, deployables and the rest of the world included. 2,406 MB is the memory peak. Players feel low fps and a climbing entity count as lag.

What location is recorded for Pinzgauer`s PVE Server?

A region is not published by Pinzgauer`s PVE Server. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 167.160.93.164:28015.

What Rust version is recorded for Pinzgauer`s PVE Server?

On Windows, Pinzgauer`s PVE Server runs Rust network protocol 2635 and build 168909. The same protocol is required for joining, and Steam updates your game to it.

Population

What does the population history show for Pinzgauer`s PVE Server?

0 of 100 slots on Pinzgauer`s PVE Server are taken at the latest refresh. Averaged across seven days, the player count is 0, with a peak of 1. Over the last 48 hours the busiest hour was 01:00 UTC, at an average of 1 players.

What rank has been recorded for Pinzgauer`s PVE Server?

Over the last seven days, Pinzgauer`s PVE Server records #6,596 for player hours: the top 30% of all ranked servers.

Wipe data

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

At their busiest, its recent wipes drew 1 players on average. 0 hours after the latest wipe, the crowd peaked. Up to the next wipe, the crowd in 100% of its recent wipes stayed above half that peak.

On Pinzgauer`s PVE Server, when do wipes occur?

No next wipe can be predicted for Pinzgauer`s PVE Server: its wipes fall at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. 24 hours ago the current world was made.

Settings

Which rules and settings are recorded for Pinzgauer`s PVE Server?

No gather rate is stated in the name of Pinzgauer`s PVE Server. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. It appears under Community in the server browser. VAC is on: that is Valve's anti-cheat.

On which map is Pinzgauer`s PVE Server played?

Pinzgauer`s PVE Server runs a procedural map of size 4,000 with seed 453818, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.

Lists and filters

Where does Pinzgauer`s PVE Server appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry Pinzgauer`s PVE Server are: Rust community servers, plotted. On the server list, these filters bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

On Pinzgauer`s PVE Server, what is meant by each tag?

gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): 100 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded are the tags Pinzgauer`s PVE Server publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

How to join

How is Pinzgauer`s PVE Server joined?

Connect with client.connect 167.160.93.164:28015: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp100
Max players 100 player slots.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

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.

KeyTag string decoded