Rust Server TrendsSeismic network · station log
Recording Stations11,643 Players45,616 Active3,092 Wipes · 3 h113 48 h

Station XX-16965 · no signal

Oil Trainer - Local Development

Offline 2.59.158.100:28015 checked 30d ago

moddedoxide
Connect
Players now
0/ 6
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,965
top 72%
Last wipe
30d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-16965 · 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 6 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
15k10k15k20k27 Sep28 Sep30 Sep1 Oct3 Oct4 Oct

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

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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
ShockRust | Blue | NoLimit no group limit · 162 on average
30/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average
126/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 114 on average
44/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 87 on average
31/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
9/ 200
CSL Scenery Budget Test groups of 8+ · 85 on average
0/ 500
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Oil Trainer - Local Development?

Oil Trainer - Local Development uses a procedural map, which the game generates.

Which settings and rules apply on Oil Trainer - Local Development?

The name of Oil Trainer - Local Development gives no gather rate. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on Oil Trainer - Local Development?

A reading taken now finds Oil Trainer - Local Development offline; the most recent activity was 30 days 10 hours ago.

How does Oil Trainer - Local Development rank against other Rust servers?

On player hours for the past week, Oil Trainer - Local Development sits at #16,965, which puts it inside the top 72% of every ranked server.

Server facts

How reliably does Oil Trainer - Local Development stay online?

Oil Trainer - Local Development is down at the moment; the last recorded contact was 30 days 10 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 27 September 2026 is when Rust Server Trends first recorded it.

Which region does Oil Trainer - Local Development run from?

Nothing about a region comes from Oil Trainer - Local Development. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 2.59.158.100:28015.

What build of Rust does Oil Trainer - Local Development use?

Rust network protocol 2633 and build 165217 on Windows is what Oil Trainer - Local Development runs. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

How often does Oil Trainer - Local Development wipe, and on which days?

The rhythm of Oil Trainer - Local Development cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 30 days 10 hours.

Server tags

What do the server tags on Oil Trainer - Local Development mean?

These are the tags Oil Trainer - Local Development publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp6 (Max players): Slots: 6; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): It runs game build 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $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. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Oil Trainer - Local Development appear?

The Rust Server Trends lists that take in Oil Trainer - Local Development 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.

Join the server

How do you connect to Oil Trainer - Local Development?

To join, enter client.connect 2.59.158.100:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp6,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp6
Max players Slots: 6.
ts8
Group limit Teams max out at 8, the default set by the game.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build It runs game build 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$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.