On the class lists: C− (56), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak 1
Rank#6,420top 29%
No wipesresets7 new worlds this week: a reset every few hours, not a wipe schedule
Next wipe–resets, no wipes
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
71/ 100
B−
Holds a respectable place: #6,420 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: 207 server fps on average.
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.
A steady term.
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.
AveragePeak
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 22 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 29% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
a new world every few hours
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W·W·
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
World resets
a new world every few hours; none of these counts as a wipe
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 22:10 UTC4d ago
–
–
–
0
Sat 24 Oct, 21:42 UTC4d ago
–
–
–
0
Sat 24 Oct, 20:48 UTC4d ago
–
–
–
0
Sat 24 Oct, 20:35 UTC4d ago
–
–
–
0
Sat 24 Oct, 19:19 UTC4d ago
–
–
–
0
Thu 22 Oct, 13:46 UTC6d ago
–
–
–
1
Thu 22 Oct, 13:03 UTC6d ago
1
✓ held half
2.3 days
1
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for A.Server.Test. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 202.36.95.176:23236.
How reliable is A.Server.Test, and is it up?
You can join now: A.Server.Test is online. About 1 minutes ago, it restarted, based on the uptime it reports. It was up 83% of the time over the last 6 full days, 120 of 144 hours. On 22 October 2026, Rust Server Score saw it for the first time.
How well does A.Server.Test run?
It averaged 207 server fps over the last 48 hours, with a low of 124. At its peak, it held 48,516 entities, including buildings, deployables and all else in the world. At its highest, it used 3,454 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does A.Server.Test sit?
The server A.Server.Test is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does A.Server.Test reset?
No resets count as wipes on A.Server.Test, because the world is remade every few hours and no schedule is kept.
Population
Where does A.Server.Test place in the wider field of Rust servers?
In the top 29% of all ranked servers, A.Server.Test sits at #6,420 for player hours over the last seven days.
What does the population on A.Server.Test look like?
Right now, 0 players are on A.Server.Test, which has 40 slots. It peaked at 1 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 15:00 UTC, with an average of 1 players.
Tags
How should you read the tags on A.Server.Test?
The game's browser takes its cue from the tags A.Server.Test has set: gmrust (Game mode): Survival in the standard Rust style; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: 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.
Which Rust Server Score filters and lists feature A.Server.Test?
Rust Server Score lists that include A.Server.Test: 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; Last wipe: In the last week.
Server rules
How is A.Server.Test set up, and what rules does it keep?
The name of A.Server.Test gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather, build and raid, as in 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. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map A.Server.Test uses?
The game generates the procedural map on A.Server.Test at size 2,500 with seed 45000. A matching size and seed produce the same map, viewable on RustMaps from this page. The name of the map reads: Custom Map.
How to join
How should you connect to A.Server.Test?
Enter client.connect 202.36.95.176:23236 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,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: 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 steady term. Strongest in performance (A+); population is the one to work on (F).