On the class lists: C (60), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak 2
Rank#7,143top 32%
Last wipe6d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
68/ 100
C+
Working its way up from the back of the class: #7,143 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
17/ 100
F
Needs to work on its frame rate: 10 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
74/ 100
B−
Climbing fast: up 3,377 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
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 23 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 32% 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
You'll find no region listed by || by Servarium.ru test. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 136.234.5.125:27099.
How reliable is || by Servarium.ru test, and is it up?
Right now, || by Servarium.ru test is online. About 1 hours ago, it restarted, based on the uptime it reports. It was up 143 of 144 hours over the last 6 full days, which is 99% of the time. It was first seen by Rust Server Score on 23 October 2026.
How well does || by Servarium.ru test run?
It averaged 10 server fps over the last 48 hours, with a low of 10. At its peak, it held 214,535 entities, including buildings, deployables and all else in the world. Memory use reached up to 4,766 MB. When fps is low and entities climb, that is lag to players.
What Rust version is || by Servarium.ru test on?
Rust network protocol 2635 and build 168909 on Linux is what || by Servarium.ru test runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does || by Servarium.ru test reset?
|| by Servarium.ru test has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 6 days 10 hours have passed since this world was made.
Population
What position does || by Servarium.ru test hold in the rankings?
In the top 32% of all ranked servers, || by Servarium.ru test sits at #7,143 for player hours over the last seven days.
What does the population on || by Servarium.ru test look like?
|| by Servarium.ru test is showing 0 players right now, with 10 slots in total. Averaging 0 players over seven days, it peaked at 2. The highest average in the last 48 hours came at 13:00 UTC, with 0 players.
Lists and filters
How should you read the tags on || by Servarium.ru test?
The game's browser takes its cue from the tags || by Servarium.ru test has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as 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.
Where does || by Servarium.ru test appear in the Rust Server Score lists and filters?
Rust Server Score lists that include || by Servarium.ru test: 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.
Map and rules
How is || by Servarium.ru test set up, and what rules does it keep?
You will find no gather rate in the name of || by Servarium.ru test. With no change from the game default, groups take up to 8 players. You get survival here, 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. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
|| by Servarium.ru test runs which map?
|| by Servarium.ru test runs a game-generated procedural map at size 6,000, seed 12345. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to || by Servarium.ru test?
To connect, start Rust, press F1, and type client.connect 136.234.5.125:27099. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 uptime (A+); population is the one to work on (F).