Oxide Test (CoreCLR)
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 23d ago · 81.196.215.13:28055
Abstract
We describe the public Rust server Oxide Test (CoreCLR), reached at 81.196.215.13:28055. It is offline at the last check, against a seven-day mean of 01. It ranks #16,290 of all servers, the top 70%. It last wiped 23d ago.
Keywordsmodded oxide
1Summary statistics
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.
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).
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.
5Wipes
5.1Schedule: too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 0 | players, last three wipes |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Thu 5 Nov, 19:00fw15d ago | – | – | running | – |
| Thu 29 Oct, 09:1923d ago | 0 | – | – | 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
| Address | 81.196.215.13:28055 |
|---|---|
| Region | – |
| Max players | 3 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 29 Oct 2026, 09:19 UTC |
| Hostname | – |
| First seen | 29 Oct 2026 |
| Map | Procedural Map |
| 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 modded server list with rates [2] and upcoming Rust wipes [3].
| Server | Players |
|---|---|
| МИНИ-КАРТА 2Х | STORM | FPS+ 21.11EU · groups of 8+ · weekly · 128 on average | 132/100 |
| ShockRust | Blue | NoLimitno group limit · 110 on average | 288/400 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11EU · groups of 16+ · weekly · 98 on average | 190/225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11EU · groups of 16+ · monthly · 79 on average | 78/700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11EU · groups of 16+ · monthly · 68 on average | 128/1000 |
| ShockRust | Green | MAX 4no group limit · 65 on average | 135/250 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1In which location is Oxide Test (CoreCLR) based?
There is no region published for Oxide Test (CoreCLR). The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 81.196.215.13:28055 is its address.
A.2How reliable is Oxide Test (CoreCLR), and is it currently online?
Oxide Test (CoreCLR) is currently offline, with the last sighting 23 days 5 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. Its first appearance in Rust Statistics's records is 29 October 2026.
A.3What is the Rust version for Oxide Test (CoreCLR)?
Oxide Test (CoreCLR) is running Rust network protocol 2635 and build 168909 on the Windows operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe schedule
A.4What schedule does Oxide Test (CoreCLR) follow for wipes?
There are not yet enough recorded wipes for Oxide Test (CoreCLR) to reveal its rhythm. Thursday 3 December at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The world currently in use was created 23 days 5 hours ago.
A.5What characterises wipe day on Oxide Test (CoreCLR)?
Recent wipes saw an average peak of 0 players. The peak on the latest wipe came 0 hours after it began.
Population
A.6What is the rank of Oxide Test (CoreCLR) among Rust servers?
The seven-day player-hours ranking puts Oxide Test (CoreCLR) at #16,290, within the top 70% of ranked servers.
A.7How would you characterise the player activity on Oxide Test (CoreCLR)?
The last recorded sighting of Oxide Test (CoreCLR) was 23 days 5 hours ago; it is offline now.
Tags and filters
A.8What do the tags associated with Oxide Test (CoreCLR) signify?
gmrust (Game mode): This is survival as standard Rust plays; mp3 (Max players): 3 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags Oxide Test (CoreCLR) publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.
A.9Where can Oxide Test (CoreCLR) be found among the Rust Statistics lists and filters?
Modded Rust servers are the Rust Statistics lists that Oxide Test (CoreCLR) fits. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules, settings, map
A.10What are the settings and rules that govern Oxide Test (CoreCLR)?
No gather rate appears in the name of Oxide Test (CoreCLR). No cap is given beyond the game's default of 8 players per group. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. Plugins or settings change the game; the browser files it under Modded. The plugin count is Oxide. The server has VAC on, Valve's anti-cheat.
A.11What is the map for Oxide Test (CoreCLR)?
On Oxide Test (CoreCLR) the terrain is procedural, built by the game itself.
How to join
A.12What steps are required to join Oxide Test (CoreCLR)?
Enter client.connect 81.196.215.13:28055 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.
Appendix BServer tags
What each of the server's tags means. Published as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. This is survival as standard Rust plays. |
mp3 | Max players. 3 slots are available. |
ts8 | Group limit. 8 per team, the value the game sets by default. |
v2635 | Protocol. Joining requires the same game version: protocol 2635. |
cs168909 | Build. Build 168909 is the one running. |
ptrak | Networking. Networking runs on RakNet, the game's standard layer. |
$r? | Region code. The region code is unset. |
| Mods and access | |
^o | Oxide. Plugins are handled by Oxide (uMod). |
^z | Modded. Modded listing: plugins or settings modify the game. |
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]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded server list with rates. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.