Rust StatisticsWorking papers on every public Rust server · 93,889 players now

Test Server (CoreCLR)

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 17d ago · 81.196.215.13:28035

Abstract

We describe the public Rust server Test Server (CoreCLR), reached at 81.196.215.13:28035. It is offline at the last check, against a seven-day mean of 01. It ranks #16,820 of all servers, the top 70%. It last wiped 19d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/30% full
In the queue0no queue
Seven-day mean0peak –
Rank2#16,820top 70%
Last wipe19d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: 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.

4Rank

The server stands in the top 70% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k28 Oct31 Oct2 Nov5 Nov7 Nov10 Nov
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap0.8 daysbetween real wipes
On rhythm0%of its recent wipes
Wipe-day peak1players, last three wipes
Mon 2 NovMon 2 NovFri 30 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 5 Nov, 19:00fw15d ago – – running –
Mon 2 Nov, 16:5018d ago 1 – – 1
Mon 2 Nov, 10:4619d ago 1 – 0.3 d 1
Fri 30 Oct, 12:3122d ago 1 – 2.9 d 1
Thu 29 Oct, 08:4423d ago 1 – 1.2 d 0
Wed 28 Oct, 20:4623d ago 1 – 0.5 d 0

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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Custom map, no picture published
Figure 5: The map: discord.gg/raidsim.
Table 4: The server's published settings.
Address81.196.215.13:28035
Region–
Max players3
Group limit100 max
Wipe schedule–
Last wipe2 Nov 2026, 14:44 UTC
Hostname–
First seen28 Oct 2026
Mapdiscord.gg/raidsim
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are browse modded Rust servers [2] and servers wiping soon [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
МИНИ-КАРТА 2Х | STORM | FPS+ 21.11EU · groups of 8+ · weekly · 128 on average132/100
ShockRust | Blue | NoLimitno group limit · 110 on average288/400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11EU · groups of 16+ · weekly · 98 on average190/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11EU · groups of 16+ · monthly · 79 on average78/700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11EU · groups of 16+ · monthly · 68 on average128/1000
ShockRust | Green | MAX 4no group limit · 65 on average135/250

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is Test Server (CoreCLR) based?

A region is not published by Test Server (CoreCLR). Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 81.196.215.13:28035.

A.2How reliable is Test Server (CoreCLR), and is it currently online?

At the present moment, Test Server (CoreCLR) is offline; it was last seen 17 days 21 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. Its first appearance in Rust Statistics's records is 28 October 2026.

A.3What version of Rust is run on Test Server (CoreCLR)?

Rust network protocol 2635 and build 168909 is the version that Test Server (CoreCLR) runs, on Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4On what cycle does Test Server (CoreCLR) wipe?

Prediction of the next wipe is impossible for Test Server (CoreCLR), which wipes irregularly. Thursday 3 December at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The current world has been running for 19 days.

A.5How would you describe wipe day on Test Server (CoreCLR)?

The average busiest point of recent wipes was 1 players. The peak on the latest wipe came 0 hours after it began.

Player count

A.6What position does Test Server (CoreCLR) occupy in the ranking of Rust servers?

Ranked by player hours across seven days, Test Server (CoreCLR) holds #16,820, in the top 70% of all ranked servers.

A.7What is the population level of Test Server (CoreCLR)?

The last recorded sighting of Test Server (CoreCLR) was 17 days 21 hours ago; it is offline now.

Tags and filters

A.8What is the meaning of the tags on Test Server (CoreCLR)?

Tags from Test Server (CoreCLR), read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp3 (Max players): 3 slots are available; ts100 (Group limit): A team holds no more than 100; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can Test Server (CoreCLR) be found among the Rust Statistics lists and filters?

The Rust Statistics lists that Test Server (CoreCLR) fits are: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.10Under what rules and settings does Test Server (CoreCLR) operate?

No gather rate appears in the name of Test Server (CoreCLR). The team limit is 100 players. The mode is survival, which means the standard mode, in which you gather, build and raid. Players may raid and fight one another. Plugins or settings change the game; the browser files it under Modded. Plugins number Oxide on this server. The server has VAC on, Valve's anti-cheat.

How to join

A.11How do you connect to Test Server (CoreCLR)?

Press F1 inside Rust to open the console and enter client.connect 81.196.215.13:28035. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts100,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp3Max players. 3 slots are available.
ts100Group limit. A team holds no more than 100.
v2635Protocol. The game protocol is 2635; your client must match it to join.
cs168909Build. This server runs game build 168909.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been set.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as Modded.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.