Station XX-15423 · no signal
[U.S]OzziGaming Vanilla | Bi-Weekly |
Offline 193.31.31.104:28032 checked 4d ago
- 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
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M –not enough readings
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, measured since 5 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on [U.S]OzziGaming Vanilla | Bi-Weekly |?
The procedural map on [U.S]OzziGaming Vanilla | Bi-Weekly | is size 3,000 with seed 1, generated 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 | Bi-Weekly |?
You will find no gather rate in the name of [U.S]OzziGaming Vanilla | Bi-Weekly |. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on [U.S]OzziGaming Vanilla | Bi-Weekly | right now?
No players are recorded on [U.S]OzziGaming Vanilla | Bi-Weekly | at this moment; it is offline, and the last sighting was 4 days 11 hours ago. The seven-day average for this server is 0 players.
How does [U.S]OzziGaming Vanilla | Bi-Weekly | rank against other Rust servers?
Over the last seven days, [U.S]OzziGaming Vanilla | Bi-Weekly | recorded enough player hours to reach #15,423 worldwide, placing it in the top 69% of all ranked servers.
Server facts
How reliably does [U.S]OzziGaming Vanilla | Bi-Weekly | stay online?
[U.S]OzziGaming Vanilla | Bi-Weekly | is down at the moment; the last recorded contact was 4 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 66, or 39% of the time. Its earliest appearance in the records of Rust Server Trends dates to 5 October 2026.
Where in the world is [U.S]OzziGaming Vanilla | Bi-Weekly | hosted?
A region is not published by [U.S]OzziGaming Vanilla | Bi-Weekly |. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 193.31.31.104:28032.
What build of Rust does [U.S]OzziGaming Vanilla | Bi-Weekly | use?
[U.S]OzziGaming Vanilla | Bi-Weekly | is running Rust network protocol 2634 and build 166652 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
How often does [U.S]OzziGaming Vanilla | Bi-Weekly | wipe, and on which days?
The rhythm of [U.S]OzziGaming Vanilla | Bi-Weekly | 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. The present world dates from 22 days 15 hours.
Lists and tags
What do the server tags on [U.S]OzziGaming Vanilla | Bi-Weekly | mean?
The game's server browser reads the tags [U.S]OzziGaming Vanilla | Bi-Weekly | publishes: gmrust (Game mode): You'll find standard Rust survival here; 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): Game build: 166652; 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): Plugins or settings alter the game, so it's listed 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 [U.S]OzziGaming Vanilla | Bi-Weekly | appear?
These Rust Server Trends lists include [U.S]OzziGaming Vanilla | Bi-Weekly |: 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
What steps get you onto [U.S]OzziGaming Vanilla | Bi-Weekly |?
Enter client.connect 193.31.31.104:28032 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
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.