Working its way up from the back of the class: #15,459 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
51/ 100
D
Moving up: up 391 places this week.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 23 Sep. 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 Wednesday 4 November, 07:54 UTC, in 5d 7h.
Biweekly: 14 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
TEST SERVER leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 61.105.188.194:28015 is the address to use.
How reliable is TEST SERVER, and is it up?
At this moment, TEST SERVER is offline; the last time it was seen was 36 days 7 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 23 September 2026, Rust Server Score saw it for the first time.
Which Rust version is TEST SERVER running?
You will find TEST SERVER on Rust network protocol 2633 and build 163794, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does TEST SERVER wipe its map?
The estimate for TEST SERVER's next wipe comes from biweekly: 14 days after its last wipe. Expect the next wipe on Wednesday 4 November at 07:54 UTC. The world it runs now was created 36 days 16 hours. Its tags say it wipes every two weeks.
Player count
Where does TEST SERVER sit among Rust servers?
Over the last seven days, TEST SERVER has #15,459 for player hours, in the top 71% of all ranked servers.
Is TEST SERVER a busy server?
TEST SERVER is offline at the moment; the last time it was seen was 36 days 7 hours ago.
Tags
How should you read the tags on TEST SERVER?
gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): Its slot count is 1; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): The server wipes on a two-week cycle; ^r (Roleplay): You play a role on this server; ^p (PvE): Players do not fight one another here; the world is the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags TEST SERVER publishes, and the game's server browser reads them. 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 lists and filters on Rust Server Score show TEST SERVER?
These Rust Server Score lists count TEST SERVER among them: Modded Rust servers, graded, Rust PvE servers, graded and Roleplay servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Roleplay ^r, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Rules and settings
How is TEST SERVER set up, and what rules does it keep?
The name of TEST SERVER gives no gather rate. With no change from the game default, groups take up to 8 players. It runs roleplay, jobs, towns and rules for roleplay. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
TEST SERVER runs which map?
A procedural map of size 3,500 and seed 4, generated by the game, is what TEST SERVER runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to TEST SERVER?
To connect, start Rust, press F1, and type client.connect 61.105.188.194:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2633,^b,^r,^p,gmrust,cs163794,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max playersIts slot count is 1.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Gameplay
^r
RoleplayYou play a role on this server.
^p
PvEPlayers do not fight one another here; the world is the danger.
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).