A quiet classroom so far: 0 of 50 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,272 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
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
50/ 100
D
Holding steady: down 99 places this week.
A term to build on.
Strongest in uptime (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
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. 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, top 85% in OC, and #519 of the trio servers (top 83%). Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·····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 Saturday 31 October, 05:04 UTC, in 2d 10h.
Its weekly schedule tag · low confidence
usual gap7 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak0players, last three wipes
Coming wipes
2d 10hSat 31 Oct, 05:04 UTC
8d 0hThu 5 Nov, 19:00 UTCFW
9d 10hSat 7 Nov, 05:04 UTC
16d 10hSat 14 Nov, 05:04 UTC
23d 10hSat 21 Nov, 05:04 UTC
30d 10hSat 28 Nov, 05:04 UTC
36d 0hThu 3 Dec, 19:00 UTCFW
37d 10hSat 5 Dec, 05:04 UTC
The first 48 hours of its last wipes
Sat 24 OctThu 15 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 37 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 24 Oct, 05:04 UTC4d ago
1
–
running
0
Thu 15 Oct, 05:03 UTC13d ago
0
–
9 days
0
Thu 8 Oct, 05:02 UTC20d ago
0
–
7 days
0
Mon 5 Oct, 05:02 UTC23d ago
0
–
3 days
0
Sat 3 Oct, 21:58 UTC24d ago
0
–
1.3 days
0
Thu 17 Sep, 06:03 UTC41d ago
0
–
16.7 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 [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. sit?
In Oceania, according to its own listing, sits [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only., with the OC tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 121.200.13.115:28023.
How dependable is [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only., and is it online at the moment?
Right now, [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. is online. It was up 144 of 168 hours over the last 7 full days, which is 86% of the time. It was first seen by Rust Server Score on 13 September 2026.
Which Rust version is [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. running?
Rust network protocol 2635 and build 168909 on Linux is what [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. wipe, and how often?
The prediction follows its tag, because too few of [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only.'s wipes are on record to confirm the schedule. Expect the next wipe on Saturday 31 October at 05:04 UTC. The world it runs now was created 4 days 13 hours. Wipes are scheduled weekly, according to its tags.
What happens on [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. when wipe day arrives?
The average peak on its recent wipes was 0 players. Peak numbers came 37 hours into the latest wipe.
Player count
What position does [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. hold in the rankings?
Over the last seven days, [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. has #15,272 for player hours, in the top 69% of all ranked servers and #175 in Oceania. It comes #519 among servers in the trio group.
What does the population on [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. look like?
With 50 slots available, [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. currently has 0 players. Averaging 0 players over seven days, it peaked at 1.
Tags and filters
What do [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only.'s tags stand for?
The game's browser takes its cue from the tags [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts3 (Group limit): No team may go above 3; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^w (Weekly): A wipe happens every week; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; OC (Oceania): The server browser lists it under Oceania. 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 [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only.?
Rust Server Score lists that include [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only.: Oceania Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. It shows under the following filters on the server list: Region: Oceania; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last week.
Rules and settings
Which rules does [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. enforce, and what are its settings?
Nothing in the name of [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. states a gather rate. You can have up to 3 players in a group (trio). It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only. uses?
The game generates a procedural map for [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only..
Connecting
What is the way to join [AU] Rust Captain Server - Weekly TEST Solo/Duo/Trio only.?
To connect, start Rust, press F1, and type client.connect 121.200.13.115:28023. 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,^v,OC,gmrust,cs168909,ts3,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts3
Group limitNo team may go above 3.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
OC
OceaniaThe server browser lists it under Oceania.
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 uptime (A+); population is the one to work on (F).