On the class lists: C− (58), with population over 48 hours and no performance mark.
Players now0/ ?
7-day average0peak –
Rank#15,318top 69%
Last wipe56d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
unmarked
–
No weekly average to mark yet.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,318 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
85/ 100
A−
Mostly smooth: 51 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 193 places this week. Nothing a good wipe can't fix.
A steady term.
Strongest in uptime (A); standing 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Facepunch AUX3. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 79.137.98.20:28017.
Is Facepunch AUX3 up, and how steady is its uptime?
Right now, Facepunch AUX3 is online. According to its reported uptime, the last restart was about 22 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does Facepunch AUX3 perform well?
The average over the last 48 hours was 51 server fps, and it never went below 39. At its peak, it held 183,721 entities, including buildings, deployables and all else in the world. Memory use reached up to 9,239 MB. Players feel lag when fps drops and entities pile up.
On what Rust version does Facepunch AUX3 sit?
Rust network protocol 2633 and build 164117 on Windows is what Facepunch AUX3 runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Facepunch AUX3 wipe, and how often?
The record holds too few of Facepunch AUX3's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 56 days.
Population
What position does Facepunch AUX3 hold in the rankings?
In the top 69% of all ranked servers, Facepunch AUX3 sits at #15,318 for player hours over the last seven days.
How many players does Facepunch AUX3 usually have?
Facepunch AUX3 has 0 players at the moment. A seven-day average of 0 players applies here.
Tags
What do Facepunch AUX3's tags stand for?
The game's browser takes its cue from the tags Facepunch AUX3 has set: official (official): Run by Facepunch or one of its partners: the servers in Rust's Official tab. Rust does not publish this, so it is kept by hand; gmrust (Game mode): Rust survival, played by the standard rules; mp0 (Max players): The server holds 0 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs164117 (Build): This runs on build 164117; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set. 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.
Who is behind Facepunch AUX3?
The same operator most likely runs Facepunch AUX3 and the 124 other servers we track that also publish a playrust.com hostname.
Which lists and filters on Rust Server Score show Facepunch AUX3?
Rust Server Score lists that include Facepunch AUX3: Official Rust servers, graded. These filters bring it up on the server list: Type: No plugins at all; Group limit: 5 or more; Boxes: Official only.
Map and rules
What settings and rules apply on Facepunch AUX3?
The name of Facepunch AUX3 gives no gather rate. 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. Rust lists it in the Official tab in game. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Facepunch AUX3?
The game generates the procedural map on Facepunch AUX3 at size 5,000 with seed 4756856. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
What is the way to join Facepunch AUX3?
To connect, start Rust, press F1, and type client.connect 79.137.98.20:28017. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2633,gmrust,cs164117,ts8
Run by Facepunch or one of its partners: the servers in Rust's Official tab. Rust does not publish this, so it is kept by hand.
Game
gmrust
Game modeRust survival, played by the standard rules.
mp0
Max playersThe server holds 0 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs164117
BuildThis runs on build 164117.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been 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.
A steady term. Strongest in uptime (A); standing is the one to work on (F).