On the class lists: C+ (66), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 1
Rank#6,692top 30%
Last wipe5h agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
70/ 100
B−
Holds a respectable place: #6,692 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 75 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A steady term.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 30% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·W·
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 27 Oct, 21:02 UTC5h ago
–
–
running
0
Sun 25 Oct, 12:02 UTC2d 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by Pinzgauer`s PVE Server. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 167.160.93.164:28015 is the address to use.
How dependable is Pinzgauer`s PVE Server, and is it online at the moment?
You can join now: Pinzgauer`s PVE Server is online. According to its reported uptime, the last restart was about 3 hours ago. It was up 70 of 168 hours over the last 7 full days, which is 42% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Is Pinzgauer`s PVE Server smooth to play on?
It averaged 75 server fps over the last 48 hours, with a low of 46. Up to 98,916 entities were in the world, covering buildings, deployables and the rest. Up to 2,406 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is Pinzgauer`s PVE Server on?
Rust network protocol 2635 and build 168909 on Windows is what Pinzgauer`s PVE Server runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does Pinzgauer`s PVE Server wipe its map?
Pinzgauer`s PVE Server wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 5 hours.
What should you expect from wipe day on Pinzgauer`s PVE Server?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 100% of its recent wipes.
Player numbers
What position does Pinzgauer`s PVE Server hold in the rankings?
In the top 30% of all ranked servers, Pinzgauer`s PVE Server sits at #6,692 for player hours over the last seven days.
Is Pinzgauer`s PVE Server a busy server?
Right now, 0 players are on Pinzgauer`s PVE Server, which has 100 slots. It peaked at 1 and averaged 0 players over the last seven days. Over the last 48 hours, the peak hour was 01:00 UTC, averaging 1 players.
Tags and filters
How should you read the tags on Pinzgauer`s PVE Server?
gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server are the tags Pinzgauer`s PVE Server publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature Pinzgauer`s PVE Server?
These Rust Server Score lists count Pinzgauer`s PVE Server among them: Best community servers, graded. These filters bring it up 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.
Map and rules
How is Pinzgauer`s PVE Server set up, and what rules does it keep?
You will find no gather rate in the name of Pinzgauer`s PVE Server. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
Pinzgauer`s PVE Server runs which map?
Pinzgauer`s PVE Server runs a game-generated procedural map at size 4,000, seed 453818. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How do you get onto Pinzgauer`s PVE Server?
Enter client.connect 167.160.93.164:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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.
A steady term. Strongest in performance (A+); population is the one to work on (F).