Working its way up from the back of the class: #15,330 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
26/ 100
F
Lost ground: down 7,329 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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
No region is published for core_training. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 107.13.210.75:28025.
How dependable is core_training, and is it online at the moment?
At this moment, core_training is offline; the last time it was seen was 10 days 10 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 16 October 2026.
On what Rust version does core_training sit?
The server core_training is on Rust network protocol 2223 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does core_training wipe its map?
core_training has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 17 days 11 hours.
Player count
Where does core_training place in the wider field of Rust servers?
In the top 70% of all ranked servers, core_training sits at #15,330 for player hours over the last seven days.
What does the population on core_training look like?
It has been 10 days 10 hours since core_training was last seen, and it is offline right now.
Lists and filters
How should you read the tags on core_training?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; v2223 (Protocol): The game protocol is 2223, so your game must match that version to join; ptrak (Networking): The network layer is RakNet, standard for the game; hd9562fd7 (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one; stok (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one are the tags core_training publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does core_training appear in the Rust Server Score lists and filters?
These Rust Server Score lists count core_training 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.
Rules and settings
How is core_training set up, and what rules does it keep?
You will find no gather rate in the name of core_training. It publishes no limit on group size. You get survival here, 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.
How to join
What is the way to join core_training?
To connect, start Rust, press F1, and type client.connect 107.13.210.75:28025. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,v2223,hd9562fd7,stok,gmrust
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
v2223
ProtocolThe game protocol is 2223, so your game must match that version to join.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
Other
hd9562fd7
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
stok
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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. Even marks across the subjects, from F to F.