On the class lists: F (36), with population over 48 hours and no performance mark.
Players now1/ 502% full
7-day average0peak 1
Rank#15,155top 68%
Last wipe1h agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
32/ 100
F
Working its way up from the back of the class: #15,155 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: 97 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
14/ 100
F
Lost ground: down 10,954 places this week. A strong wipe could turn it round.
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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 14 Oct. 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.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 28 Oct, 22:59 UTC1h ago
–
–
running
1
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
Rust TestServer leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 211.106.63.210:28015.
Is Rust TestServer up, and how steady is its uptime?
Right now, Rust TestServer is online. About 6 minutes ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 144 of 168 hours, or 86% of the time. On 14 October 2026, Rust Server Score saw it for the first time.
Does Rust TestServer perform well?
The average over the last 48 hours was 97 server fps, and it never went below 60. Up to 188,809 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 8,408 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is Rust TestServer running?
You will find Rust TestServer on Rust network protocol 2635 and build 167781, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does Rust TestServer wipe, and how often?
Rust TestServer has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 1 hours.
Population
Where does Rust TestServer place in the wider field of Rust servers?
In the top 68% of all ranked servers, Rust TestServer sits at #15,155 for player hours over the last seven days.
What does the population on Rust TestServer look like?
Rust TestServer is showing 1 players right now, with 50 slots in total. Averaging 0 players over seven days, it peaked at 1. The busiest time in the last 48 hours was 23:00 UTC, with an average of 1 players.
Tags
What is meant by the tags on Rust TestServer?
You'll see Rust TestServer tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs167781 (Build): This runs on build 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here in the browser, which picks them up from the server. 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.
Which lists and filters on Rust Server Score show Rust TestServer?
These Rust Server Score lists count Rust TestServer among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Map and rules
Which rules does Rust TestServer enforce, and what are its settings?
The name of Rust TestServer gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Rust TestServer?
A procedural map of size 4,250 and seed 856364890, generated by the game, is what Rust TestServer runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto Rust TestServer?
To connect, start Rust, press F1, and type client.connect 211.106.63.210:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
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).