Working its way up from the back of the class: #15,180 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
30/ 100
F
Lost ground: down 6,156 places this week. A strong wipe could turn it round.
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.
AveragePeak
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
Top 70% of all ranked servers, top 88% in EU, and #525 of the trio servers (top 84%). Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Wednesday 4 November, 10:00 UTC, in 6d 9h.
Weekly: 7 days after its last wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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 Europe, according to its own listing, sits testserver, with the EU tag. Rust Server Score takes the server's word for its location and does not trace the hardware. 95.24.237.78:28015 is the address to use.
How reliable is testserver, and is it up?
The server is down: testserver is offline now, with the last sighting 12 days 4 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 15 October 2026.
What Rust version is testserver on?
You will find testserver on Rust network protocol 2634 and build 167781, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does testserver wipe, and how often?
weekly: 7 days after its last wipe gives the basis for estimating testserver's next wipe. Wednesday 4 November at 10:00 UTC is the date set for its next wipe. 14 days 14 hours have passed since this world was made. Wipes are scheduled weekly, according to its tags.
Player count
Where does testserver place in the wider field of Rust servers?
Over the last seven days, testserver has #15,180 for player hours, in the top 70% of all ranked servers and #2,599 in Europe. In the trio group, it ranks #525.
What does the population on testserver look like?
It has been 12 days 4 hours since testserver was last seen, and it is offline right now.
Tags and filters
How should you read the tags on testserver?
You'll see testserver tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp200 (Max players): 200 slots are available; ts3 (Group limit): No team may go above 3; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^w (Weekly): A wipe happens every week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; EU (Europe): You will find it under Europe in the browser 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 Rust Server Score filters and lists feature testserver?
These Rust Server Score lists count testserver among them: European Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly.
Rules and settings
Which rules does testserver enforce, and what are its settings?
You will find no gather rate in the name of testserver. You can have up to 3 players in a group (trio). survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Getting in
How do you get onto testserver?
To connect, start Rust, press F1, and type client.connect 95.24.237.78:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,^w,EU,gmrust,cs167781,ts3,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp200
Max players200 slots are available.
ts3
Group limitNo team may go above 3.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Region
EU
EuropeYou will find it under Europe 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. Even marks across the subjects, from F to F.