On the class lists: D (49), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average1peak 1
Rank#6,434top 29%
Last wipe5d agoweekly schedule
Next wipe1d 17hThu 29 Oct, 18:35 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 50 on average. Plenty of space to grow.
Standingrank on player hours
71/ 100
B−
Holds a respectable place: #6,434 on player hours.
Uptimehours on the list, last 48
25/ 100
F
Attendance needs work: on the list only 12 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 60 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
47/ 100
D
Slipped a little: down 349 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 29% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
9 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W·W·
·······
·W·F·W·
·····W·
···W··W
···W···
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 29 October, 18:35 UTC, in 1d 17h.
Its weekly schedule tag · low confidence
usual gap3.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
Coming wipes
1d 17hThu 29 Oct, 18:35 UTC
8d 18hThu 5 Nov, 19:00 UTCFW
15d 17hThu 12 Nov, 18:35 UTC
22d 17hThu 19 Nov, 18:35 UTC
29d 17hThu 26 Nov, 18:35 UTC
36d 18hThu 3 Dec, 19:00 UTCFW
43d 17hThu 10 Dec, 18:35 UTC
The first 48 hours of its last wipes
Thu 22 OctSun 18 OctThu 15 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 18:35 UTC5d ago
1
–
running
0
Sun 18 Oct, 03:13 UTC9d ago
1
✓ held half
4.6 days
0
Thu 15 Oct, 22:53 UTC12d ago
1
✓ held half
2.2 days
0
Sat 10 Oct, 05:34 UTC17d ago
1
✓ held half
5.7 days
0
Sat 3 Oct, 13:45 UTC24d ago
1
✓ held half
6.7 days
0
Thu 1 Oct, 23:01 UTCFW26d ago
1
–
1.6 days
0
Tue 29 Sep, 02:34 UTC28d ago
1
✓ held half
2.9 days
0
Sat 19 Sep, 03:02 UTC38d ago
1
halved by day 1
10 days
1
Thu 17 Sep, 22:54 UTC40d ago
1
–
1.2 days
0
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
In what location does S.O.S.Au/NZ (.Shoot.on.Sight.) sit?
The name of S.O.S.Au/NZ (.Shoot.on.Sight.) points to Oceania, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 203.12.3.54:28015.
Is S.O.S.Au/NZ (.Shoot.on.Sight.) up, and how steady is its uptime?
You can join now: S.O.S.Au/NZ (.Shoot.on.Sight.) is online. The uptime it reports puts the last restart at about 2 hours ago. For the last 7 full days, it was up 39 of 168 hours, or 23% of the time. It was first seen by Rust Server Score on 17 September 2026.
Does S.O.S.Au/NZ (.Shoot.on.Sight.) perform well?
It never fell below 60 server fps in the last 48 hours, averaging 60. At its peak, it held 124,722 entities, including buildings, deployables and all else in the world. Memory use reached up to 3,386 MB. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is S.O.S.Au/NZ (.Shoot.on.Sight.) running?
Rust network protocol 2635 and build 168909 on Windows is what S.O.S.Au/NZ (.Shoot.on.Sight.) runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does S.O.S.Au/NZ (.Shoot.on.Sight.) reset?
Too few wipes on S.O.S.Au/NZ (.Shoot.on.Sight.) are recorded to confirm the schedule, so its tag guides the prediction. It is due to wipe next on Thursday 29 October at 18:35 UTC. 5 days 6 hours have passed since this world was made. Wipes are scheduled weekly, according to its tags.
What happens on S.O.S.Au/NZ (.Shoot.on.Sight.) when wipe day arrives?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 100% of its recent wipes.
Player numbers
Where does S.O.S.Au/NZ (.Shoot.on.Sight.) place in the wider field of Rust servers?
Over the last seven days, S.O.S.Au/NZ (.Shoot.on.Sight.) has #6,434 for player hours, in the top 29% of all ranked servers.
Is S.O.S.Au/NZ (.Shoot.on.Sight.) a busy server?
Right now, 0 players are on S.O.S.Au/NZ (.Shoot.on.Sight.), which has 50 slots. The seven-day average is 1 players, with a peak of 1. The highest average in the last 48 hours came at 04:00 UTC, with 1 players.
Tags and filters
What do S.O.S.Au/NZ (.Shoot.on.Sight.)'s tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^w (Weekly): It wipes weekly; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags S.O.S.Au/NZ (.Shoot.on.Sight.) publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does S.O.S.Au/NZ (.Shoot.on.Sight.) appear in the Rust Server Score lists and filters?
Rust Server Score lists that include S.O.S.Au/NZ (.Shoot.on.Sight.): Oceania Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Oceania; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week.
Map and rules
How is S.O.S.Au/NZ (.Shoot.on.Sight.) set up, and what rules does it keep?
The name of S.O.S.Au/NZ (.Shoot.on.Sight.) gives no gather rate. The default of 8 players applies as the group cap. It runs survival, 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. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
S.O.S.Au/NZ (.Shoot.on.Sight.) runs which map?
The game generates the procedural map on S.O.S.Au/NZ (.Shoot.on.Sight.) at size 4,680 with seed 23102026. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
What is the way to join S.O.S.Au/NZ (.Shoot.on.Sight.)?
To connect, start Rust, press F1, and type client.connect 203.12.3.54:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^w,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).