On the class lists: D (45), with population over 48 hours and no performance mark.
Players now1/ 1010% full
7-day average2peak 3
Rank#12,302top 55%
Last wipe5d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
17/ 100
F
A quiet classroom so far: 2 of 10 on average. Plenty of space to grow.
Standingrank on player hours
45/ 100
D
Working its way up from the back of the class: #12,302 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (D); 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
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 55% 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
Which region is RustScape test | RFM_FO_0.0.36 (1) based in?
RustScape test | RFM_FO_0.0.36 (1) leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 167.233.208.36:28015.
Is RustScape test | RFM_FO_0.0.36 (1) up, and how steady is its uptime?
You cannot join now: RustScape test | RFM_FO_0.0.36 (1) is offline, last seen 5 days ago. For the last 4 full days, it was up 0 of 96 hours, or 0% of the time. The first sighting by Rust Server Score was on 23 October 2026.
What Rust version is RustScape test | RFM_FO_0.0.36 (1) on?
The server RustScape test | RFM_FO_0.0.36 (1) is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does RustScape test | RFM_FO_0.0.36 (1) wipe its map?
The record holds too few of RustScape test | RFM_FO_0.0.36 (1)'s wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 5 days.
Population
Where does RustScape test | RFM_FO_0.0.36 (1) sit among Rust servers?
Over the last seven days, RustScape test | RFM_FO_0.0.36 (1) has #12,302 for player hours, in the top 55% of all ranked servers.
What does the population on RustScape test | RFM_FO_0.0.36 (1) look like?
It has been 5 days since RustScape test | RFM_FO_0.0.36 (1) was last seen, and it is offline right now. It peaked at 3 and averaged 2 players over the last seven days.
Tags
What do RustScape test | RFM_FO_0.0.36 (1)'s tags stand for?
The game's browser takes its cue from the tags RustScape test | RFM_FO_0.0.36 (1) has set: gmrust (Game mode): Survival in the standard Rust style; mp10 (Max players): Its slot count is 10; 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; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show RustScape test | RFM_FO_0.0.36 (1)?
These Rust Server Score lists count RustScape test | RFM_FO_0.0.36 (1) among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Server rules
Which rules does RustScape test | RFM_FO_0.0.36 (1) enforce, and what are its settings?
You will find no gather rate in the name of RustScape test | RFM_FO_0.0.36 (1). The default of 8 players applies as the group cap. You get survival here, gather and build and raid: 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.
How to join
What is the way to join RustScape test | RFM_FO_0.0.36 (1)?
Enter client.connect 167.233.208.36:28015 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 asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp10
Max playersIts slot count is 10.
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.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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 term to build on. Strongest in standing (D); population is the one to work on (F).