On the class lists: C+ (65), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 1
Rank#8,245top 37% · #2110 in EU
Last wipe20d agoweekly schedule
Next wipe20hThu 29 Oct, 20:38 UTC
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
63/ 100
C
Working its way up from the back of the class: #8,245 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
67/ 100
C+
Keeps a fair share of its players through a wipe: 67% of wipes kept half their crowd.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in wipe hold (C+); 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 37% of all ranked servers, top 72% in EU, and #424 of the trio servers (top 68%). Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
···W··W
···W···
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 29 October, 20:38 UTC, in 20h.
Its weekly schedule tag · low confidence
usual gap4.2 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held67%else halves by day 1
Coming wipes
20hThu 29 Oct, 20:38 UTC
7d 18hThu 5 Nov, 19:00 UTCFW
14d 20hThu 12 Nov, 20:38 UTC
21d 20hThu 19 Nov, 20:38 UTC
28d 20hThu 26 Nov, 20:38 UTC
35d 18hThu 3 Dec, 19:00 UTCFW
42d 20hThu 10 Dec, 20:38 UTC
The first 48 hours of its last wipes
Thu 8 OctSun 4 OctThu 1 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 8 Oct, 20:38 UTC20d ago
0
–
running
0
Sun 4 Oct, 14:54 UTC24d ago
2
✓ held half
4.2 days
0
Thu 1 Oct, 15:02 UTC27d ago
1
halved by day 1
3 days
0
Thu 24 Sep, 13:06 UTC34d ago
2
✓ held half
7.1 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
The EU tag on FoxRust X5 | MAX 3 puts it in Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 188.187.122.94:28015.
How reliable is FoxRust X5 | MAX 3, and is it up?
The server is down: FoxRust X5 | MAX 3 is offline now, with the last sighting 3 days 2 hours ago. It was up 23 of 168 hours over the last 7 full days, which is 14% of the time. It was first seen by Rust Server Score on 19 September 2026.
Which Rust version is FoxRust X5 | MAX 3 running?
Rust network protocol 2635 and build 168909 on Windows is what FoxRust X5 | MAX 3 runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does FoxRust X5 | MAX 3 wipe, and how often?
The prediction follows its tag, because too few of FoxRust X5 | MAX 3's wipes are on record to confirm the schedule. It is due to wipe next on Thursday 29 October at 20:38 UTC. It has been running its current world for 20 days 3 hours. Wipes are scheduled weekly, according to its tags.
What happens on FoxRust X5 | MAX 3 when wipe day arrives?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 67% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Population
Where does FoxRust X5 | MAX 3 sit among Rust servers?
Over the last seven days, FoxRust X5 | MAX 3 has #8,245 for player hours, in the top 37% of all ranked servers and #2,110 in Europe. It comes #424 among servers in the trio group.
What does the population on FoxRust X5 | MAX 3 look like?
The last sighting of FoxRust X5 | MAX 3 was 3 days 2 hours ago, and it is offline right now. The seven-day average is 0 players, with a peak of 1.
Tags and filters
What is meant by the tags on FoxRust X5 | MAX 3?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; ts3 (Group limit): Teams cap out at 3; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^w (Weekly): Wipes come once a week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EU (Europe): In the server browser it appears under Europe are the tags FoxRust X5 | MAX 3 publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature FoxRust X5 | MAX 3?
These Rust Server Score lists count FoxRust X5 | MAX 3 among them: 5x Rust servers, graded, European Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Gather rate: 5x.
Map and rules
How is FoxRust X5 | MAX 3 set up, and what rules does it keep?
FoxRust X5 | MAX 3 sets gather at 5x, as its name suggests. You can have up to 3 players in a group (trio). It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map FoxRust X5 | MAX 3 uses?
The game generates the procedural map on FoxRust X5 | MAX 3 at size 2,800 with seed 444123. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to FoxRust X5 | MAX 3?
Enter client.connect 188.187.122.94: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,^w,EU,gmrust,cs168909,ts3,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersThe server holds 100 slots.
ts3
Group limitTeams cap out at 3.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
EU
EuropeIn the server browser it appears under Europe.
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 term to build on. Strongest in wipe hold (C+); population is the one to work on (F).