This server publishes no banner
Exhibit no. 15,353Acc. 2026.15353
[U.S]OzziGaming Vanilla | Bi-Weekly |
Rust server · in the archive since 5 October 2026
Offline 193.31.31.104:28032 checked 5d ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
The record of each wipe
No wipe seen yet.
Peak: the most players in the first 48 hours. 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.
The rhythm
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Tags and filters
What do the server tags on [U.S]OzziGaming Vanilla | Bi-Weekly | mean?
You can see the tags [U.S]OzziGaming Vanilla | Bi-Weekly | publishes, read by the game's server browser: gmrust (Game mode): This server runs standard Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The default cap of 8 per team applies here; v2634 (Protocol): Your game must run protocol 2634 to join; cs166652 (Build): This server runs game build 166652; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings. The tags also carry the current player count, the queue and the world's creation time, shown at the top of this page.
Which Rust Server History lists and filters include [U.S]OzziGaming Vanilla | Bi-Weekly |?
These Rust Server History lists include [U.S]OzziGaming Vanilla | Bi-Weekly |: Modded Rust servers: the record. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server record
Which version of Rust does [U.S]OzziGaming Vanilla | Bi-Weekly | run?
The recorded build for [U.S]OzziGaming Vanilla | Bi-Weekly | is Rust network protocol 2634 and build 166652 on Linux. Steam updates your game for you; joining needs the same protocol.
Is [U.S]OzziGaming Vanilla | Bi-Weekly | online, and how reliable is it?
The record shows [U.S]OzziGaming Vanilla | Bi-Weekly | offline at this moment, last seen 5 days 8 hours ago. 42 of 168 hours, or 25% of the time, over the last 7 full days. 5 October 2026 is when Rust Server History first saw it.
Where is [U.S]OzziGaming Vanilla | Bi-Weekly | located?
You will find no region published by [U.S]OzziGaming Vanilla | Bi-Weekly |. The location on Rust Server History is what a server says, not a lookup of where the machine stands. You can reach it at 193.31.31.104:28032.
Wipe record
What is the wipe schedule on [U.S]OzziGaming Vanilla | Bi-Weekly |?
The rhythm of [U.S]OzziGaming Vanilla | Bi-Weekly | cannot be told yet, as too few of its wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, when every Rust server wipes. 23 days 11 hours ago its current world was made.
Population
How does [U.S]OzziGaming Vanilla | Bi-Weekly | rank against other Rust servers?
Over seven days of player hours, [U.S]OzziGaming Vanilla | Bi-Weekly | ranks #15,353, inside the top 69% of all ranked servers.
How busy is [U.S]OzziGaming Vanilla | Bi-Weekly |?
No current count exists for [U.S]OzziGaming Vanilla | Bi-Weekly |; it was last seen 5 days 8 hours ago. An average of 0 players is recorded across the last seven days.
Rules and settings
What are the rules and settings on [U.S]OzziGaming Vanilla | Bi-Weekly |?
The name of [U.S]OzziGaming Vanilla | Bi-Weekly | carries no gather rate. The limit of 8 players per group is the game's default. Recorded as survival, with this note: gathering, building and raiding: the standard game. PvP and raiding are enabled. Plugins or settings alter the game here, and the browser lists the server under Modded. Plugins in use: Oxide. The anti-cheat VAC from Valve is active.
Which map does [U.S]OzziGaming Vanilla | Bi-Weekly | run?
A procedural map of size 3,000 with seed 1 is what [U.S]OzziGaming Vanilla | Bi-Weekly | runs, generated by the game. One size and seed produce one map, which RustMaps can show you from this page.
How to join
How do I join [U.S]OzziGaming Vanilla | Bi-Weekly |?
Entering client.connect 193.31.31.104:28032 in the console (F1) connects you to this server. The Launch Rust button on this page does the same: it opens the game via Steam and connects on your behalf.
The label explained
Server tags
What each tag this server publishes means.
Published as mp100,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
mp100
ts8
v2634
cs166652
ptrak
$r?
Mods and access
^o
^z
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.