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
Where in the world is [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly |?
You'll find no region listed by [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly |. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 193.31.31.104:28047.
Is [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | up, and how steady is its uptime?
You cannot join now: [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | is offline, last seen 21 days 11 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 5 October 2026, Rust Server Score saw it for the first time.
Which Rust version is [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | running?
You will find [U.S]OzziGaming 1.5x Solo/Duo/Trio | 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 schedule
When does [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | wipe, and how often?
There are too few wipes on record for [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 22 days 21 hours have passed since this world was made.
Player count
Where does [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | place in the wider field of Rust servers?
In the top 71% of all ranked servers, [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | sits at #15,986 for player hours over the last seven days.
Is [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | a busy server?
[U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | is offline at the moment; the last time it was seen was 21 days 11 hours ago.
Tags
How should you read the tags on [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly |?
You'll see [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | tagged with gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly |?
These Rust Server Score lists count [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | among them: 1.5x Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 1.5x.
Server rules
How is [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | set up, and what rules does it keep?
The name of [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | points to a 1.5x gather rate. With no change from the game default, groups take up to 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 1.5x Solo/Duo/Trio | Weekly | runs which map?
[U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly | runs a game-generated procedural map at size 6,000, seed 1. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto [U.S]OzziGaming 1.5x Solo/Duo/Trio | Weekly |?
To connect, start Rust, press F1, and type client.connect 193.31.31.104:28047. 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 modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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).