Working its way up from the back of the class: #15,427 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
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 65% 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
No region is published for RT_Traning. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 95.24.106.26:28015.
How reliable is RT_Traning, and is it up?
The server is down: RT_Traning is offline now, with the last sighting 30 days 7 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 28 September 2026, Rust Server Score saw it for the first time.
Which Rust version is RT_Traning running?
You will find RT_Traning on Rust network protocol 2633 and build 163207, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does RT_Traning wipe, and how often?
RT_Traning has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 52 days 17 hours.
Population
Where does RT_Traning sit among Rust servers?
In the top 65% of all ranked servers, RT_Traning sits at #15,427 for player hours over the last seven days.
Is RT_Traning a busy server?
The last sighting of RT_Traning was 30 days 7 hours ago, and it is offline right now.
Tags and filters
What do RT_Traning's tags stand for?
The game's browser takes its cue from the tags RT_Traning has set: gmrust (Game mode): Rust survival, played by the standard rules; mp15 (Max players): The server holds 15 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163207 (Build): The game build is 163207; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does RT_Traning appear in the Rust Server Score lists and filters?
These Rust Server Score lists count RT_Traning among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
How is RT_Traning set up, and what rules does it keep?
Nothing in the name of RT_Traning states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on RT_Traning?
RT_Traning runs a procedural map, which the game generates.
Connecting
What is the way to join RT_Traning?
To connect, start Rust, press F1, and type client.connect 95.24.106.26:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp15,ptrak,$r?,v2633,gmrust,cs163207,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp15
Max playersThe server holds 15 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163207
BuildThe game build is 163207.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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.