Working its way up from the back of the class: #15,986 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
53/ 100
D
Moving up: up 853 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Peak
Crowd
Lasted
Players before
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
EU · groups of 300+ · 2x · weekly · 313 on average
62 / 1000
Quick answers
from the figures on this page
Server facts
In what location does [U.S]OzziGaming 2x | Bi-Weekly | sit?
No region is published for [U.S]OzziGaming 2x | Bi-Weekly |. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 193.31.31.104:28056 is the address to use.
How dependable is [U.S]OzziGaming 2x | Bi-Weekly |, and is it online at the moment?
The server is down: [U.S]OzziGaming 2x | Bi-Weekly | is offline now, with the last sighting 22 days 1 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 5 October 2026.
On what Rust version does [U.S]OzziGaming 2x | Bi-Weekly | sit?
You will find [U.S]OzziGaming 2x | Bi-Weekly | on Rust network protocol 2634 and build 166652, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does [U.S]OzziGaming 2x | Bi-Weekly | reset?
There are too few wipes on record for [U.S]OzziGaming 2x | Bi-Weekly | to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 23 days 11 hours have passed since this world was made.
Population
Where does [U.S]OzziGaming 2x | Bi-Weekly | place in the wider field of Rust servers?
Over the last seven days, [U.S]OzziGaming 2x | Bi-Weekly | has #15,986 for player hours, in the top 71% of all ranked servers.
Is [U.S]OzziGaming 2x | Bi-Weekly | a busy server?
The last sighting of [U.S]OzziGaming 2x | Bi-Weekly | was 22 days 1 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on [U.S]OzziGaming 2x | Bi-Weekly |?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): Its slot count is 100; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags [U.S]OzziGaming 2x | Bi-Weekly | publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show [U.S]OzziGaming 2x | Bi-Weekly |?
These Rust Server Score lists count [U.S]OzziGaming 2x | Bi-Weekly | among them: 2x Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.
Rules and settings
What settings and rules apply on [U.S]OzziGaming 2x | Bi-Weekly |?
Going by its name, [U.S]OzziGaming 2x | Bi-Weekly | runs 2x gather. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [U.S]OzziGaming 2x | Bi-Weekly | uses?
A procedural map of size 3,000 and seed 1, generated by the game, is what [U.S]OzziGaming 2x | Bi-Weekly | runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join [U.S]OzziGaming 2x | Bi-Weekly |?
To connect, start Rust, press F1, and type client.connect 193.31.31.104:28056. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://ozzigaming.com.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits 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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).