Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
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 peak0players, last three wipes
The first 48 hours of its last wipes
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 17 Sep, 17:27 UTC42d ago
0
–
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
Which region is foxx test server do not join based in?
You'll find no region listed by foxx test server do not join. Rust Server Score takes the server's word for its location and does not trace the hardware. 69.39.37.233:28035 is the address to use.
How reliable is foxx test server do not join, and is it up?
At this moment, foxx test server do not join is offline; the last time it was seen was 41 days 3 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is foxx test server do not join running?
Rust network protocol 2633 and build 164530 on Linux is what foxx test server do not join runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does foxx test server do not join reset?
foxx test server do not join has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 42 days 3 hours have passed since this world was made.
What should you expect from wipe day on foxx test server do not join?
The average peak on its recent wipes was 0 players. Peak numbers came 0 hours into the latest wipe.
Population
Where does foxx test server do not join sit among Rust servers?
In the top – of all ranked servers, foxx test server do not join sits at #15,406 for player hours over the last seven days.
What does the population on foxx test server do not join look like?
It has been 41 days 3 hours since foxx test server do not join was last seen, and it is offline right now.
Tags and filters
How should you read the tags on foxx test server do not join?
gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): The server holds 10 slots; ts12 (Group limit): Teams cap out at 12; 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): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags foxx test server do not join publishes, and the game's server browser reads them. 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.
Where does foxx test server do not join appear in the Rust Server Score lists and filters?
These Rust Server Score lists count foxx test server do not join among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
What settings and rules apply on foxx test server do not join?
You will find no gather rate in the name of foxx test server do not join. The limit for a group is 12 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Connecting
How do you get onto foxx test server do not join?
To connect, start Rust, press F1, and type client.connect 69.39.37.233:28035. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2633,gmrust,cs164530,ts12,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersThe server holds 10 slots.
ts12
Group limitTeams cap out at 12.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThe game build is 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
Not enough figures yet to write a report. Check back after a few days on the list.