Station XX-15400 · no signal
[U.S]OzziGaming 1.5x | Bi-Weekly |
Offline 193.31.31.104:28026 checked 4d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,400
- 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 pageServer rules
Which map is running on [U.S]OzziGaming 1.5x | Bi-Weekly |?
Generated by the game, the map on [U.S]OzziGaming 1.5x | Bi-Weekly | is procedural, size 3,000 with seed 1. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on [U.S]OzziGaming 1.5x | Bi-Weekly |?
Going by its name, [U.S]OzziGaming 1.5x | Bi-Weekly | runs 1.5x gather. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on [U.S]OzziGaming 1.5x | Bi-Weekly | right now?
[U.S]OzziGaming 1.5x | Bi-Weekly | is not responding at this moment and is offline, last seen 4 days 17 hours ago. The population averaged 0 players over the past week.
How does [U.S]OzziGaming 1.5x | Bi-Weekly | rank against other Rust servers?
On player hours for the past week, [U.S]OzziGaming 1.5x | Bi-Weekly | sits at #15,400, which puts it inside the top 69% of every ranked server.
Server facts
How reliably does [U.S]OzziGaming 1.5x | Bi-Weekly | stay online?
[U.S]OzziGaming 1.5x | Bi-Weekly | is down at the moment; the last recorded contact was 4 days 17 hours ago. 64 of 168 hours in the last 7 full days were up time, 38% of the total. 5 October 2026 is when Rust Server Trends first recorded it.
Which region does [U.S]OzziGaming 1.5x | Bi-Weekly | run from?
No region is published by [U.S]OzziGaming 1.5x | 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:28026.
What build of Rust does [U.S]OzziGaming 1.5x | Bi-Weekly | use?
[U.S]OzziGaming 1.5x | 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 day
How often does [U.S]OzziGaming 1.5x | Bi-Weekly | wipe, and on which days?
Too few wipes of [U.S]OzziGaming 1.5x | Bi-Weekly | are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 22 days 18 hours.
Tags
What do the server tags on [U.S]OzziGaming 1.5x | Bi-Weekly | mean?
These are the tags [U.S]OzziGaming 1.5x | Bi-Weekly | publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; 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): 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 [U.S]OzziGaming 1.5x | Bi-Weekly | appear?
These Rust Server Trends lists include [U.S]OzziGaming 1.5x | Bi-Weekly |: 1.5x Rust servers and 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; Gather rate: 1.5x.
Connecting
What steps get you onto [U.S]OzziGaming 1.5x | Bi-Weekly |?
You can connect by pressing F1 in Rust and typing client.connect 193.31.31.104:28026 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.