Working its way up from the back of the class: #16,363 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
48/ 100
D
Slipped a little: down 579 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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
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.
No daily history yet.
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 71% of all ranked servers. 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 Thursday 5 November, 19:00 UTC, in 7d 18h.
The force 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
TEST SERVER leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 187.40.227.37:28215.
How dependable is TEST SERVER, and is it online at the moment?
You cannot join now: TEST SERVER is offline, last seen 33 days 10 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 25 September 2026.
Which Rust version is TEST SERVER running?
You will find TEST SERVER on Rust network protocol 2633 and build 164530, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does TEST SERVER reset?
the force wipe gives the basis for estimating TEST SERVER's next wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 52 days 16 hours have passed since this world was made. The tags show a monthly wipe schedule.
Population
Where does TEST SERVER sit among Rust servers?
Over the last seven days, TEST SERVER has #16,363 for player hours, in the top 71% of all ranked servers.
Is TEST SERVER a busy server?
The last sighting of TEST SERVER was 33 days 10 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on TEST SERVER?
You'll see TEST SERVER tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): This runs on build 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^s (Softcore): You keep some inventory when you die, as Facepunch's easier mode allows; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. 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 TEST SERVER?
Rust Server Score lists that include TEST SERVER: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: PvE and Softcore; Server tag: Monthly ^m, Softcore ^s, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
What settings and rules apply on TEST SERVER?
The name of TEST SERVER gives no gather rate. The default of 8 players applies as the group cap. You get softcore here, Facepunch's easier setting, with part of your loot kept. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
TEST SERVER runs which map?
The game generates a procedural map for TEST SERVER.
How to join
How should you connect to TEST SERVER?
Enter client.connect 187.40.227.37:28215 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 asmp20,ptrak,$r?,v2633,^m,^s,^p,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max playersThe server holds 20 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^s
SoftcoreYou keep some inventory when you die, as Facepunch's easier mode allows.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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. Strongest in momentum (D); standing is the one to work on (F).