Rust Server TrendsSeismic network · station log
Recording Stations11,601 Players32,197 Active2,849 Wipes · 3 h67 48 h

Station XX-15423 · no signal

[U.S]OzziGaming Vanilla Solo | Weekly |

Offline 193.31.31.104:28015 checked 4d ago

moddedoxide
Connect
Players now
0/ 100
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,423
top 69%
Last wipe
22d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15423 · 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 100 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, measured since 5 Oct. 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
15k10k15k20k5 Oct10 Oct14 Oct19 Oct23 Oct28 Oct

Top 69% 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

01234+0h+9h+19h+28h+38h+47h

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
Mon 5 Oct, 14:23 UTC22d ago M0.0steady 0 – running 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
ShockRust | Blue | NoLimit no group limit · 158 on average
54/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average
131/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 114 on average
41/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 88 on average
30/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average
4/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 83 on average
13/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on [U.S]OzziGaming Vanilla Solo | Weekly |?

[U.S]OzziGaming Vanilla Solo | Weekly | runs a procedural map of size 5,000 with seed 3225711, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on [U.S]OzziGaming Vanilla Solo | Weekly |?

You will find no gather rate in the name of [U.S]OzziGaming Vanilla Solo | Weekly |. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.

Population

How many players are recorded on [U.S]OzziGaming Vanilla Solo | Weekly | right now?

No players are recorded on [U.S]OzziGaming Vanilla Solo | Weekly | at this moment; it is offline, and the last sighting was 4 days 5 hours ago. The seven-day average for this server is 0 players.

How does [U.S]OzziGaming Vanilla Solo | Weekly | rank against other Rust servers?

The last seven days of player hours place [U.S]OzziGaming Vanilla Solo | Weekly | at #15,423, in the top 69% of all ranked servers.

Operator and location

How reliably does [U.S]OzziGaming Vanilla Solo | Weekly | stay online?

No contact with [U.S]OzziGaming Vanilla Solo | Weekly | right now, and the last recorded contact was 4 days 5 hours ago. 72 of 168 hours in the last 7 full days were up time, 43% of the total. On 5 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does [U.S]OzziGaming Vanilla Solo | Weekly | run from?

A region is not published by [U.S]OzziGaming Vanilla Solo | Weekly |. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 193.31.31.104:28015.

Which Rust version is [U.S]OzziGaming Vanilla Solo | Weekly | running?

[U.S]OzziGaming Vanilla Solo | Weekly | is running Rust network protocol 2634 and build 166652 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe schedule

What does wipe day look like on [U.S]OzziGaming Vanilla Solo | Weekly |?

On average, the busiest point of its recent wipes drew 0 players. The peak on the most recent wipe came 0 hours after the wipe.

On what timetable does [U.S]OzziGaming Vanilla Solo | Weekly | run its wipes?

On record so far are too few of [U.S]OzziGaming Vanilla Solo | Weekly |'s wipes to tell its rhythm. 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 22 days 14 hours.

Server tags

What do the server tags on [U.S]OzziGaming Vanilla Solo | Weekly | mean?

These are the tags [U.S]OzziGaming Vanilla Solo | Weekly | publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): The server has 100 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed 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 [U.S]OzziGaming Vanilla Solo | Weekly | appear?

You will find [U.S]OzziGaming Vanilla Solo | Weekly | on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up 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 [U.S]OzziGaming Vanilla Solo | Weekly |?

To join, enter client.connect 193.31.31.104: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. For the website, go to https://ozzigaming.com.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp100
Max players The server has 100 slots.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166652
Build The game build is 166652.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed 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.