Oxide Test (CoreCLR)
Key statistics
the figures behind the quote- Players now
- 0/ 3 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #16,290 top 70%
- Rank · 7d ago
- #15,262 ▼1028 places down
- Last wipe
- 14d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 29 Oct 2026 no hostname published
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
too few wipes seen yet- wipe-day peak
- 0 players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW6d ago | – | – | running | – |
| Thu 29 Oct, 09:19 UTC14d 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. 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| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | STEEL RUST /ДЛЯ НОВИЧКОВ /EU Main 11.11EU · groups of 24+ · monthly · 140 on average | 54/100 | ▼−373−87.4% | |
| 2 | 666 RUST /ДЛЯ НОВИЧКОВ /ПИТЕРСКИЙ 11.11EU · groups of 16+ · monthly · 136 on average | 49/750 | ▼−224−82.0% | |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 11.11EU · groups of 16+ · monthly · 129 on average | 199/1000 | ▼−126−38.8% | |
| 4 | МИНИ-КАРТА 2Х | STORM | FPS+ 11.11EU · groups of 8+ · weekly · 127 on average | 132/100 | ▲+3+2.4% | |
| 5 | ShockRust | Blue | NoLimitno group limit · 121 on average | 145/400 | ▼−49−25.4% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 12.11EU · groups of 16+ · monthly · 118 on average | 367/1000 | ▲+317+640.2% |
Quick answers
from the figures on this pageServer Rules
How is Oxide Test (CoreCLR) configured in terms of rules and settings?
The name of Oxide Test (CoreCLR) carries no gather rate. Groups can contain a maximum of 8 players, the default for the game. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. Modded is its category in the server browser; plugins or settings modify the game. Plugin count: Oxide. The server has VAC, Valve's anti-cheat, switched on.
What is the current map on Oxide Test (CoreCLR)?
A procedural map runs on Oxide Test (CoreCLR), created by the game.
Activity
What position does Oxide Test (CoreCLR) hold in the server rankings?
For the last seven days, Oxide Test (CoreCLR) holds rank #16,290 on player hours, in the top 70% of all ranked servers.
What is the population on Oxide Test (CoreCLR)?
Right now, Oxide Test (CoreCLR) is offline; the last sighting was 14 days 6 hours ago.
Wipe Cycle
What happens on wipe day at Oxide Test (CoreCLR)?
The average peak across its recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
When does Oxide Test (CoreCLR) schedule its wipes?
The record holds too few of Oxide Test (CoreCLR)'s wipes to establish its rhythm. The monthly force wipe applies to every Rust server. The next one falls on Thursday 3 December at 19:00 UTC. Its world now is 14 days 6 hours old.
Server Details
What is the location of Oxide Test (CoreCLR)?
For Oxide Test (CoreCLR), no region is published. Rust Analytics reports the location a server claims, not the machine's actual location. 81.196.215.13:28055 is its address.
What Rust version is Oxide Test (CoreCLR) running?
The build is Rust network protocol 2635 and build 168909 on Windows, running on Oxide Test (CoreCLR). The protocol has to match for you to join, and Steam applies that update.
Is Oxide Test (CoreCLR) up, and how consistent is its uptime?
No response from Oxide Test (CoreCLR). It was last seen 14 days 6 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. 29 October 2026 is when Rust Analytics first saw it.
Server Tags
How should you interpret the tags on Oxide Test (CoreCLR)?
These tags are published by Oxide Test (CoreCLR) and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp3 (Max players): Slot count: 3; ts8 (Group limit): At the game default, teams hold up to 8; v2635 (Protocol): To join, your game needs protocol 2635; cs168909 (Build): Build 168909; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework Oxide (uMod) is in use; ^z (Modded): The Modded listing applies: plugins or settings change play. Also in the tags and at the top of this page: current players, queue and world creation time.
Where does Oxide Test (CoreCLR) show up in Rust Analytics lists and filters?
On Rust Analytics, Oxide Test (CoreCLR) matches these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Joining the Server
How can I connect to Oxide Test (CoreCLR)?
Type client.connect 81.196.215.13:28055 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
mp3
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^o
^z
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.