Working its way up from the back of the class: #16,842 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
46/ 100
D
Slipped a little: down 1,256 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.
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. 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
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
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 what location does Rust Tournaments | TEST sit?
No region is published for Rust Tournaments | TEST. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 217.154.251.167:28015.
Is Rust Tournaments | TEST up, and how steady is its uptime?
At this moment, Rust Tournaments | TEST is offline; the last time it was seen was 28 days 21 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is Rust Tournaments | TEST on?
Rust network protocol 2632 and build 161125 on Linux is what Rust Tournaments | TEST runs. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does Rust Tournaments | TEST wipe its map?
There are too few wipes on record for Rust Tournaments | TEST to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 71 days 13 hours.
Player numbers
What position does Rust Tournaments | TEST hold in the rankings?
Over the last seven days, Rust Tournaments | TEST has #16,842 for player hours, in the top 70% of all ranked servers.
How many players does Rust Tournaments | TEST usually have?
Rust Tournaments | TEST is offline at the moment; the last time it was seen was 28 days 21 hours ago.
Tags
What is meant by the tags on Rust Tournaments | TEST?
The game's browser takes its cue from the tags Rust Tournaments | TEST has set: gmrust (Game mode): Rust survival, played by the standard rules; mp20 (Max players): Its slot count is 20; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2632 (Protocol): To get in, your game needs to be on the same version: the protocol is 2632; cs161125 (Build): The game build is 161125; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this 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.
Where does Rust Tournaments | TEST appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Rust Tournaments | TEST among them: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
Which rules does Rust Tournaments | TEST enforce, and what are its settings?
You will find no gather rate in the name of Rust Tournaments | TEST. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Rust Tournaments | TEST uses?
Rust Tournaments | TEST runs a procedural map, which the game generates.
Getting in
How should you connect to Rust Tournaments | TEST?
To connect, start Rust, press F1, and type client.connect 217.154.251.167:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2632,gmrust,cs161125,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp20
Max playersIts slot count is 20.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2632
ProtocolTo get in, your game needs to be on the same version: the protocol is 2632.
cs161125
BuildThe game build is 161125.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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).