On the class lists: F (35), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak –
Rank#15,327top 69% · #1502 in NA
Last wipe18d agobiweekly schedule
Next wipe7d 1hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 40 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,327 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: 95 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 202 places this week. Nothing a good wipe can't fix.
A term to build on.
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.
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 25 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, top 81% in NA. 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 5 November, 19:00 UTC, in 7d 1h.
The force wipe · high confidence
usual gap4.2 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
Coming wipes
7d 1hThu 5 Nov, 19:00 UTCFW
9d 14hSun 8 Nov, 07:50 UTC
23d 14hSun 22 Nov, 07:50 UTC
35d 1hThu 3 Dec, 19:00 UTCFW
37d 14hSun 6 Dec, 07:50 UTC
The first 48 hours of its last wipes
Sun 11 OctSat 3 OctMon 28 Sep
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
Sun 11 Oct, 07:50 UTC18d ago
1
–
running
1
Sat 3 Oct, 03:37 UTC26d ago
1
halved by day 1
8.2 days
0
Mon 28 Sep, 21:39 UTC30d ago
1
halved by day 1
4.2 days
0
Fri 25 Sep, 21:11 UTC33d ago
0
–
3 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
In North America, according to its own listing, sits Foxx Dev, with the NA tag. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 107.175.159.174:28025.
Is Foxx Dev up, and how steady is its uptime?
The server is up: Foxx Dev is online now. The uptime it reports puts the last restart at about 22 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 25 September 2026, Rust Server Score saw it for the first time.
Does Foxx Dev perform well?
It never fell below 66 server fps in the last 48 hours, averaging 95. Buildings, deployables and everything else in the world added up to as many as 142,641 entities. Memory use reached up to 5,335 MB. When fps is low and entities climb, that is lag to players.
What Rust version is Foxx Dev on?
You will find Foxx Dev on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Foxx Dev wipe, and how often?
The prediction follows its tag, because too few of Foxx Dev's wipes are on record to confirm the schedule. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 18 days 9 hours. A fortnightly wipe schedule appears in its tags.
What should you expect from wipe day on Foxx Dev?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began. Half the peak held until the next wipe in 0% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player count
Where does Foxx Dev place in the wider field of Rust servers?
In North America, Foxx Dev is #1,502, and overall it is #15,327 on player hours over the last seven days, in the top 69% of all ranked servers.
How many players does Foxx Dev usually have?
Foxx Dev is showing 0 players right now, with 40 slots in total. A seven-day average of 0 players applies here.
Tags
How should you read the tags on Foxx Dev?
The game's browser takes its cue from the tags Foxx Dev has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): The server holds 40 slots; ts12 (Group limit): Teams cap out at 12; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): You will find it under North America in the browser. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Who is behind Foxx Dev?
3 other servers we track also use a foxxservers.com hostname, so they and Foxx Dev most likely share an operator.
Where does Foxx Dev appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Foxx Dev among them: Modded Rust servers, graded, Rust PvE servers, graded and North America Rust servers, graded. These filters bring it up on the server list: Region: North America; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Rules and settings
What settings and rules apply on Foxx Dev?
The name of Foxx Dev gives no gather rate. The limit for a group is 12 players. pve is the mode 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 Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Foxx Dev?
The game generates the procedural map on Foxx Dev at size 5,000 with seed 241644880. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Fox Island!.
Connecting
How should you connect to Foxx Dev?
Enter client.connect 107.175.159.174:28025 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 asmp40,ptrak,$r?,v2635,^b,NA,^p,gmrust,cs168909,ts12,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max playersThe server holds 40 slots.
ts12
Group limitTeams cap out at 12.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
NA
North AmericaYou will find it under North America in the browser.
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 performance (A+); population is the one to work on (F).