core_training
Offline 107.13.210.75:28025 checked 39m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 36% of all ranked servers. Ranked on player hours over the last seven days.
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
the same kind of game, then region, group limit, rate and wipes
- 183/ 225
- 332/ 425
- 239/ 250
- 132/ 200
- 134/ 200
- 186/ 250
Quick answers
Tags and filters
Where does core_training appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include core_training: Rust community servers, going deep. The server list shows it under Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 2 weeks.
How should you read the tags on core_training?
The server browser shows these tags for core_training: gmrust (Game mode): Survival, as standard Rust does it; mp50 (Max players): There are 50 slots on this server; v2223 (Protocol): To join, your game has to be on protocol 2223; ptrak (Networking): The network layer is RakNet, Rust's default; hd9562fd7 (Custom tag): It's a custom tag, set by the owner or a plugin, not a standard one; stok (Custom tag): It's a custom tag, set by the owner or a plugin, not a standard one. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
What location is core_training in?
core_training does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 107.13.210.75:28025.
How reliable is core_training?
Right now core_training is offline, having last been seen 39 minutes ago. It stayed up for 24 of the 24 hours in the last 1 full day, giving 100% uptime. Rust Going Deep has had it on record since 16 October 2026.
What Rust version is core_training on?
On Windows, core_training runs Rust network protocol 2223. The protocol must match to join; Steam will update your game.
Wipe info
What schedule does core_training follow for wipes?
Too few wipes are on record for core_training to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 7 days 2 hours is how long ago this world came into being.
Settings and map
Which rules and settings is core_training running?
No gather rate appears in the name of core_training. The group limit is not published. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser lists it under Community, making it a community server. VAC is on: Valve's anti-cheat is active.
Player stats
What's the population like on core_training?
Right now core_training is offline, with its last appearance 39 minutes ago. For the past week, players averaged 0 with a high of 2. At 23:00 UTC in the last 48 hours, the average reached its highest: 2 players.
What position does core_training hold in the server rankings?
Over the last seven days, core_training is #7,999 by player hours, among the top 36% of all ranked servers.
How to join
What's the process to join core_training?
Open Rust and press F1, then type client.connect 107.13.210.75:28025. Alternatively, click Launch Rust on this page to join via Steam.