Working its way up from the back of the class: #16,921 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
46/ 100
D
Slipped a little: down 1,449 places this week. Nothing a good wipe can't fix.
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.
No daily history yet.
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 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
Next wipe Thursday 5 November, 19:00 UTC, in 8d 7h.
The 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 150+ · 1x · monthly · 130 on average
142 / 300
Quick answers
from the figures on this page
Server details
Which region is _mod_retest_rust_oxide_5453fc6a based in?
No region is published for _mod_retest_rust_oxide_5453fc6a. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 167.114.157.40:40798.
How reliable is _mod_retest_rust_oxide_5453fc6a, and is it up?
You cannot join now: _mod_retest_rust_oxide_5453fc6a is offline, last seen 29 days 7 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 29 September 2026.
Which Rust version is _mod_retest_rust_oxide_5453fc6a running?
Rust network protocol 2633 and build 165217 on Linux is what _mod_retest_rust_oxide_5453fc6a runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does _mod_retest_rust_oxide_5453fc6a wipe its map?
The next wipe on _mod_retest_rust_oxide_5453fc6a is a projection from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. The world it runs now was created 29 days 7 hours. Its tags record that it wipes monthly.
Population
What position does _mod_retest_rust_oxide_5453fc6a hold in the rankings?
Over the last seven days, _mod_retest_rust_oxide_5453fc6a has #16,921 for player hours, in the top 71% of all ranked servers.
How many players does _mod_retest_rust_oxide_5453fc6a usually have?
The last sighting of _mod_retest_rust_oxide_5453fc6a was 29 days 7 hours ago, and it is offline right now.
Lists and filters
What do _mod_retest_rust_oxide_5453fc6a's tags stand for?
You'll see _mod_retest_rust_oxide_5453fc6a tagged with gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): Its slot count is 50; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does _mod_retest_rust_oxide_5453fc6a appear in the Rust Server Score lists and filters?
Rust Server Score lists that include _mod_retest_rust_oxide_5453fc6a: Best community servers, graded and Vanilla Rust servers, graded. These filters bring it up on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Monthly ^m and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
Which rules does _mod_retest_rust_oxide_5453fc6a enforce, and what are its settings?
The name of _mod_retest_rust_oxide_5453fc6a gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. By its own description it is vanilla: facepunch's own version, with no changed rates, kits or rules. The server runs Valve's anti-cheat, VAC.
Which map is in play on _mod_retest_rust_oxide_5453fc6a?
A procedural map, generated by the game, is what _mod_retest_rust_oxide_5453fc6a runs.
Connecting
What is the way to join _mod_retest_rust_oxide_5453fc6a?
Enter client.connect 167.114.157.40:40798 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,^m,^v,gmvanilla,cs165217,ts8
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max playersIts slot count is 50.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
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).