Working its way up from the back of the class: #13,693 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
47/ 100
D
Slipped a little: down 811 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 63% of all ranked servers, and #577 of the quad servers (top 70%). 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.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
No hourly players around its wipes yet.
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 07:19 UTC12d ago
1
–
running
0
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 leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 193.141.60.212:28015.
How reliable is Test, and is it up?
The server is down: Test is offline now, with the last sighting 12 days 2 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 17 October 2026.
What Rust version is Test on?
The server Test is on Rust network protocol 2634 and build 167231 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Test wipe, and how often?
The record holds too few of Test's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 12 days 3 hours have passed since this world was made.
What should you expect from wipe day on Test?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Player count
Where does Test sit among Rust servers?
Over the last seven days, Test has #13,693 for player hours, in the top 63% of all ranked servers. It comes #577 among servers in the quad group.
What does the population on Test look like?
It has been 12 days 2 hours since Test was last seen, and it is offline right now.
Tags
What do Test's tags stand for?
The game's browser takes its cue from the tags Test has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts4 (Group limit): A team can hold 4 players at most; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167231 (Build): Build number: 167231; ptsw (Networking): 'sw' is the network layer here; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; rustmaps (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner. 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.
Where does Test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Test among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Quad; Last wipe: In the last 2 weeks.
Rules and settings
Which rules does Test enforce, and what are its settings?
The name of Test gives no gather rate. You can have up to 4 players in a group (quad). You get survival 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. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Getting in
What is the way to join Test?
To connect, start Rust, press F1, and type client.connect 193.141.60.212:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptsw,$r?,v2634,gmrust,cs167231,ts4,^o^z,rustmaps
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts4
Group limitA team can hold 4 players at most.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167231
BuildBuild number: 167231.
ptsw
Networking'sw' is the network layer here.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
rustmaps
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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).