Rust Server TrendsSeismic network · station log
Recording Stations11,637 Players32,508 Active2,805 Wipes · 3 h70 48 h

Station XX-15427 · no signal

oracle2

Offline 144.31.90.49:28025 checked 16d ago

Connect
Players now
0/ 1
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,427
top 71%
Last wipe
16d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-15427 · 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 1 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
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 Oct

Top 71% 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 549 on average
147/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
125/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
14/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 284 on average
18/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
13/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 249 on average
38/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on oracle2?

A procedural map runs on oracle2, generated by the game.

Which settings and rules apply on oracle2?

You will find no gather rate in the name of oracle2. The group limit is 8 players, the game's default. survival is the game mode, gather, build and raid in the standard game. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on oracle2?

oracle2 is not responding at this moment and is offline, last seen 16 days 3 hours ago.

How does oracle2 rank against other Rust servers?

On player hours for the past week, oracle2 sits at #15,427, which puts it inside the top 71% of every ranked server.

Server details

How reliably does oracle2 stay online?

No contact with oracle2 right now, and the last recorded contact was 16 days 3 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 October 2026.

Which region does oracle2 run from?

A region is not published by oracle2. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 144.31.90.49:28025 is the address it uses.

What build of Rust does oracle2 use?

On Windows, oracle2 runs Rust network protocol 2634 and build 167584. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

How often does oracle2 wipe, and on which days?

On record so far are too few of oracle2's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 16 days 3 hours.

Lists and tags

What do the server tags on oracle2 mean?

Tags published by oracle2 and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): The server has 1 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167584 (Build): Game build: 167584; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code. 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 oracle2 appear?

These Rust Server Trends lists include oracle2: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

How do you connect to oracle2?

You can connect by pressing F1 in Rust and typing client.connect 144.31.90.49:28025 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 mp1,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp1
Max players The server has 1 slots.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167584
Build Game build: 167584.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

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.