Rust Server TrendsSeismic network · station log
Recording Stations11,535 Players86,112 Active4,004 Wipes · 3 h131 48 h

Station XX-16290 · no signal

Oxide Test (CoreCLR)

Offline 81.196.215.13:28055 checked 23d ago

moddedoxide
Connect
Players now
0/ 3
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,290
top 70%
Last wipe
23d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16290 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 3 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k29 Oct30 Oct1 Nov2 Nov4 Nov5 Nov

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

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.

wipe-day peak
0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 5 Nov, 19:00 UTC FW15d ago – – – – running –
Thu 29 Oct, 09:19 UTC23d ago M0.0steady 0 – – – 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
МИНИ-КАРТА 2Х | STORM | FPS+ 18.11 EU · groups of 8+ · weekly · 128 on average
133/ 100
ShockRust | Blue | NoLimit no group limit · 110 on average
298/ 400
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT GLOBAL 20.11 EU · groups of 16+ · weekly · 98 on average
187/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 17.11 EU · groups of 16+ · monthly · 79 on average
60/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 19.11 EU · groups of 16+ · monthly · 69 on average
119/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 14.11 EU · groups of 16+ · monthly · 66 on average
11/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Oxide Test (CoreCLR)?

A procedural map runs on Oxide Test (CoreCLR), generated by the game.

Which settings and rules apply on Oxide Test (CoreCLR)?

No gather rate appears in the name of Oxide Test (CoreCLR). Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on Oxide Test (CoreCLR) right now?

No players are recorded on Oxide Test (CoreCLR) at this moment; it is offline, and the last sighting was 23 days 3 hours ago.

How does Oxide Test (CoreCLR) rank against other Rust servers?

Over the last seven days, Oxide Test (CoreCLR) recorded enough player hours to reach #16,290 worldwide, placing it in the top 70% of all ranked servers.

Server facts

How reliably does Oxide Test (CoreCLR) stay online?

Oxide Test (CoreCLR) is down at the moment; the last recorded contact was 23 days 3 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 29 October 2026 is when Rust Server Trends first recorded it.

Which region does Oxide Test (CoreCLR) run from?

Nothing about a region comes from Oxide Test (CoreCLR). The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 81.196.215.13:28055 is the address it uses.

Which Rust version is Oxide Test (CoreCLR) running?

On Windows, Oxide Test (CoreCLR) runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on Oxide Test (CoreCLR)?

On average, the busiest point of its recent wipes drew 0 players. 0 hours after the latest wipe, the crowd peaked.

On what timetable does Oxide Test (CoreCLR) run its wipes?

On record so far are too few of Oxide Test (CoreCLR)'s wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 3 December at 19:00 UTC. The present world dates from 23 days 3 hours.

Lists and tags

What do the server tags on Oxide Test (CoreCLR) mean?

Tags published by Oxide Test (CoreCLR) and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp3 (Max players): The server has 3 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it 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 Oxide Test (CoreCLR) appear?

These Rust Server Trends lists include Oxide Test (CoreCLR): Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Connecting

How do you connect to Oxide Test (CoreCLR)?

You can connect by pressing F1 in Rust and typing client.connect 81.196.215.13:28055 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp3
Max players The server has 3 slots.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded The game is changed by plugins or settings, placing it under 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.

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.