Working its way up from the back of the class: #15,929 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
37/ 100
F
Slipped a little: down 4,154 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W···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 gap3.8 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Mon 28 SepFri 25 SepMon 21 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 28 Sep, 18:32 UTC30d ago
1
–
running
0
Fri 25 Sep, 00:36 UTC34d ago
–
–
3.7 days
0
Mon 21 Sep, 05:48 UTC38d ago
0
–
3.8 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
No region is published for Foxx Current Dev. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 107.175.159.174:28015.
How reliable is Foxx Current Dev, and is it up?
You cannot join now: Foxx Current Dev is offline, last seen 26 days 14 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 20 September 2026.
What Rust version is Foxx Current Dev on?
The server Foxx Current Dev is on Rust network protocol 2634 and build 166655 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does Foxx Current Dev reset?
No next wipe can be predicted for Foxx Current Dev, which wipes at irregular times. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 30 days 14 hours.
What should you expect from wipe day on Foxx Current Dev?
The average peak on its recent wipes was 0 players. Peak numbers came 1 hours into the latest wipe.
Player count
Where does Foxx Current Dev place in the wider field of Rust servers?
In the top 70% of all ranked servers, Foxx Current Dev sits at #15,929 for player hours over the last seven days.
What does the population on Foxx Current Dev look like?
It has been 26 days 14 hours since Foxx Current Dev was last seen, and it is offline right now.
Tags
How should you read the tags on Foxx Current Dev?
The game's browser takes its cue from the tags Foxx Current Dev has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp40 (Max players): 40 slots are available; ts12 (Group limit): A team can hold 12 players at most; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166655 (Build): This runs on build 166655; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 Foxx Current Dev appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Foxx Current Dev among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is Foxx Current Dev set up, and what rules does it keep?
Nothing in the name of Foxx Current Dev states a gather rate. You can play in groups of up to 12 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. 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.
Can you tell me which map Foxx Current Dev uses?
Foxx Current Dev runs a game-generated procedural map at size 4,500, seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Fox Island!.
Getting in
How should you connect to Foxx Current Dev?
Enter client.connect 107.175.159.174: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 asmp40,ptrak,$r?,v2634,gmrust,cs166655,ts12,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp40
Max players40 slots are available.
ts12
Group limitA team can hold 12 players at most.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166655
BuildThis runs on build 166655.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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. Even marks across the subjects, from F to F.