Working its way up from the back of the class: #15,346 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
52/ 100
D
Moving up: up 631 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.
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 7d 22h.
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
Where in the world is _mod_retest_rust_oxide_3ce296e3?
No region is published for _mod_retest_rust_oxide_3ce296e3. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 167.114.157.40:41146.
Is _mod_retest_rust_oxide_3ce296e3 up, and how steady is its uptime?
At this moment, _mod_retest_rust_oxide_3ce296e3 is offline; the last time it was seen was 15 days 5 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 13 October 2026.
On what Rust version does _mod_retest_rust_oxide_3ce296e3 sit?
The server _mod_retest_rust_oxide_3ce296e3 is on Rust network protocol 2634 and build 167781 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does _mod_retest_rust_oxide_3ce296e3 wipe its map?
the force wipe gives the basis for estimating _mod_retest_rust_oxide_3ce296e3's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 15 days 5 hours have passed since this world was made. Its tags list a monthly wipe schedule.
Player numbers
Where does _mod_retest_rust_oxide_3ce296e3 sit among Rust servers?
In the top 71% of all ranked servers, _mod_retest_rust_oxide_3ce296e3 sits at #15,346 for player hours over the last seven days.
What does the population on _mod_retest_rust_oxide_3ce296e3 look like?
The last sighting of _mod_retest_rust_oxide_3ce296e3 was 15 days 5 hours ago, and it is offline right now.
Lists and filters
What do _mod_retest_rust_oxide_3ce296e3's tags stand for?
You'll see _mod_retest_rust_oxide_3ce296e3 tagged with gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; 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): You get the unmodified game: no rate changes, no kits, no rule changes 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 lists and filters on Rust Server Score show _mod_retest_rust_oxide_3ce296e3?
These Rust Server Score lists count _mod_retest_rust_oxide_3ce296e3 among them: Best community servers, graded and Vanilla Rust servers, graded. You can find it under these server-list filters: 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.
Server rules
What settings and rules apply on _mod_retest_rust_oxide_3ce296e3?
Nothing in the name of _mod_retest_rust_oxide_3ce296e3 states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. Vanilla is what it calls itself: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
Can you tell me which map _mod_retest_rust_oxide_3ce296e3 uses?
A procedural map, generated by the game, is what _mod_retest_rust_oxide_3ce296e3 runs.
Connecting
What is the way to join _mod_retest_rust_oxide_3ce296e3?
Enter client.connect 167.114.157.40:41146 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?,v2634,^m,^v,gmvanilla,cs167781,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
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
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
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).