Working its way up from the back of the class: #15,498 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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
43/ 100
F
Slipped a little: down 2,278 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); 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
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
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 21 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 68% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 21 Sep, 15:13 UTC36d ago
1
–
running
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 FOXDALE Rust. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 194.78.234.18:28015 is the address to use.
Is FOXDALE Rust up, and how steady is its uptime?
You cannot join now: FOXDALE Rust is offline, last seen 36 days 2 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 21 September 2026, Rust Server Score saw it for the first time.
What Rust version is FOXDALE Rust on?
You will find FOXDALE Rust on Rust network protocol 2633 and build 164530, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does FOXDALE Rust reset?
The record holds too few of FOXDALE Rust'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. 36 days 17 hours have passed since this world was made.
What should you expect from wipe day on FOXDALE Rust?
Recent wipes have peaked at 1 players on average. Peak numbers came 2 hours into the latest wipe.
Player numbers
Where does FOXDALE Rust place in the wider field of Rust servers?
In the top 68% of all ranked servers, FOXDALE Rust sits at #15,498 for player hours over the last seven days.
How many players does FOXDALE Rust usually have?
The last sighting of FOXDALE Rust was 36 days 2 hours ago, and it is offline right now.
Tags
What do FOXDALE Rust's tags stand for?
The game's browser takes its cue from the tags FOXDALE Rust has set: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): The game build is 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^p (PvE): This is player against world: players do not fight each other; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does FOXDALE Rust appear in the Rust Server Score lists and filters?
Rust Server Score lists that include FOXDALE Rust: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.
Rules and settings
How is FOXDALE Rust set up, and what rules does it keep?
Nothing in the name of FOXDALE Rust states a gather rate. The default of 8 players applies as the group cap. You get pve here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map FOXDALE Rust uses?
FOXDALE Rust runs a game-generated procedural map at size 3,500, seed 24681012. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to FOXDALE Rust?
Enter client.connect 194.78.234.18: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 asmp10,ptrak,$r?,v2633,^z,^y,^p,gmrust,cs164530,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThe game build is 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonThe plugin framework in use is Carbon.
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 momentum (F); standing is the one to work on (F).