Working its way up from the back of the class: #15,498 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
51/ 100
D
Moving up: up 352 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.
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 68% 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 10h.
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
In what location does Russian Siberia Test RAM sit?
Russian Siberia Test RAM leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 176.9.26.61:35000.
How reliable is Russian Siberia Test RAM, and is it up?
At this moment, Russian Siberia Test RAM is offline; the last time it was seen was 41 days 13 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Which Rust version is Russian Siberia Test RAM running?
You will find Russian Siberia Test RAM on Rust network protocol 2633 and build 163207, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Russian Siberia Test RAM wipe, and how often?
The estimate for Russian Siberia Test RAM's next wipe comes 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. It has been running its current world for 51 days 1 hours. The tags show a monthly wipe schedule.
Player numbers
Where does Russian Siberia Test RAM place in the wider field of Rust servers?
Over the last seven days, Russian Siberia Test RAM has #15,498 for player hours, in the top 68% of all ranked servers.
How many players does Russian Siberia Test RAM usually have?
It has been 41 days 13 hours since Russian Siberia Test RAM was last seen, and it is offline right now.
Tags and filters
What do Russian Siberia Test RAM's tags stand for?
You'll see Russian Siberia Test RAM tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): 10 slots are available; ts10 (Group limit): No team may go above 10; v2633 (Protocol): Join only if your game runs protocol 2633; cs163207 (Build): Build number: 163207; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded 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 Russian Siberia Test RAM appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Russian Siberia Test RAM among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
How is Russian Siberia Test RAM set up, and what rules does it keep?
Nothing in the name of Russian Siberia Test RAM states a gather rate. A group here can reach 10 players. It runs survival, gather and build and raid: 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.
Russian Siberia Test RAM runs which map?
Russian Siberia Test RAM runs a procedural map, which the game generates.
Connecting
How do you get onto Russian Siberia Test RAM?
Enter client.connect 176.9.26.61:35000 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?,v2633,^m,gmrust,cs163207,ts10,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max players10 slots are available.
ts10
Group limitNo team may go above 10.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163207
BuildBuild number: 163207.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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 momentum (D); standing is the one to work on (F).