Station XX-16820 · no signal
Test Server (CoreCLR)
Offline 81.196.215.13:28035 checked 17d ago
- Players now
- 0/ 3
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,820
- top 70%
- Last wipe
- 18d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 3 slots
- Motion · 24 h
- M –not enough readings
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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 0.8 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | running | – |
| Mon 2 Nov, 16:50 UTC18d ago | M0.0■steady | 1 | – | – | 1 | |
| Mon 2 Nov, 10:46 UTC19d ago | M0.0■steady | 1 | – | 0.3 days | 1 | |
| Fri 30 Oct, 12:31 UTC22d ago | M0.0■steady | 1 | – | 2.9 days | 1 | |
| Thu 29 Oct, 08:44 UTC23d ago | M0.0▲rising | 1 | – | 1.2 days | 0 | |
| Wed 28 Oct, 20:46 UTC23d ago | M0.0▲rising | 1 | – | 0.5 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which settings and rules apply on Test Server (CoreCLR)?
The name of Test Server (CoreCLR) gives no gather rate. 100 players is the most a group can hold. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on Test Server (CoreCLR)?
No players are recorded on Test Server (CoreCLR) at this moment; it is offline, and the last sighting was 17 days 19 hours ago.
How does Test Server (CoreCLR) rank against other Rust servers?
On player hours for the past week, Test Server (CoreCLR) sits at #16,820, which puts it inside the top 70% of every ranked server.
Operator and location
How reliably does Test Server (CoreCLR) stay online?
As recorded now, Test Server (CoreCLR) is not reachable, the last contact having been 17 days 19 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 28 October 2026.
Which region does Test Server (CoreCLR) run from?
Nothing about a region comes from Test Server (CoreCLR). Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 81.196.215.13:28035.
Which Rust version is Test Server (CoreCLR) running?
Test Server (CoreCLR) is running Rust network protocol 2635 and build 168909 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on Test Server (CoreCLR)?
The recent wipes averaged a busiest count of 1 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does Test Server (CoreCLR) run its wipes?
No next wipe can be predicted for Test Server (CoreCLR), which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 3 December at 19:00 UTC. 18 days 22 hours is how long the current world has been running.
Tags
What do the server tags on Test Server (CoreCLR) mean?
The game's server browser reads the tags Test Server (CoreCLR) publishes: gmrust (Game mode): You'll find standard Rust survival here; mp3 (Max players): 3 slots are available; ts100 (Group limit): The team limit is 100; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Test Server (CoreCLR) appear?
The Rust Server Trends lists that take in Test Server (CoreCLR) are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto Test Server (CoreCLR)?
Enter client.connect 81.196.215.13:28035 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.