On the class lists: F (40), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,344top 69%
Last wipe23d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,344 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
49/ 100
D
Slipped a little: down 171 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); population 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 69% 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
Which region is [U.S]OzziGaming Vanilla | Bi-Weekly | based in?
No region is published for [U.S]OzziGaming Vanilla | Bi-Weekly |. Rust Server Score takes the server's word for its location and does not trace the hardware. 193.31.31.104:28032 is the address to use.
How dependable is [U.S]OzziGaming Vanilla | Bi-Weekly |, and is it online at the moment?
At this moment, [U.S]OzziGaming Vanilla | Bi-Weekly | is offline; the last time it was seen was 5 days 5 hours ago. It was up 66 of 168 hours over the last 7 full days, which is 39% of the time. The first sighting by Rust Server Score was on 5 October 2026.
What Rust version is [U.S]OzziGaming Vanilla | Bi-Weekly | on?
You will find [U.S]OzziGaming Vanilla | 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.
Wipe cycle
How frequently does [U.S]OzziGaming Vanilla | Bi-Weekly | wipe its map?
There are too few wipes on record for [U.S]OzziGaming Vanilla | Bi-Weekly | to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 23 days 9 hours.
Player numbers
What position does [U.S]OzziGaming Vanilla | Bi-Weekly | hold in the rankings?
Over the last seven days, [U.S]OzziGaming Vanilla | Bi-Weekly | has #15,344 for player hours, in the top 69% of all ranked servers.
How many players does [U.S]OzziGaming Vanilla | Bi-Weekly | usually have?
[U.S]OzziGaming Vanilla | Bi-Weekly | is offline at the moment; the last time it was seen was 5 days 5 hours ago. A seven-day average of 0 players applies here.
Tags and filters
How should you read the tags on [U.S]OzziGaming Vanilla | Bi-Weekly |?
gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): Build number: 166652; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags [U.S]OzziGaming Vanilla | Bi-Weekly | publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show [U.S]OzziGaming Vanilla | Bi-Weekly |?
Rust Server Score lists that include [U.S]OzziGaming Vanilla | Bi-Weekly |: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What settings and rules apply on [U.S]OzziGaming Vanilla | Bi-Weekly |?
Nothing in the name of [U.S]OzziGaming Vanilla | Bi-Weekly | states a gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
[U.S]OzziGaming Vanilla | Bi-Weekly | runs which map?
A procedural map of size 3,000 and seed 1, generated by the game, is what [U.S]OzziGaming Vanilla | Bi-Weekly | runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to [U.S]OzziGaming Vanilla | Bi-Weekly |?
To connect, start Rust, press F1, and type client.connect 193.31.31.104:28032. Or click Launch Rust here, which launches Rust through Steam and joins you.
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 players100 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^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); population is the one to work on (F).