On the class lists: F (36), with population over 48 hours and no performance mark.
Players now1/ 250% full
7-day average0peak 1
Rank#9,094top 41%
Last wipe11h agomonthly schedule
Next wipe6d 19hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
12/ 100
F
A quiet classroom so far: 0 of 2 on average. Plenty of space to grow.
Standingrank on player hours
59/ 100
C−
Working its way up from the back of the class: #9,094 on player hours.
Uptimehours on the list, last 48
12/ 100
F
Attendance needs work: on the list only 6 of the last 48 hours.
Performanceserver fps, last 48 hours
76/ 100
B
Mostly smooth: 46 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
64/ 100
C
Moving up: up 2,546 places this week.
A term to build on.
Strongest in performance (B); wipes are 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.
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 41% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
······W
······W
·······
·······
·······
···W
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 6d 19h.
The force wipe · high confidence
usual gap13.5 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 3
Coming wipes
6d 19hThu 5 Nov, 19:00 UTCFW
34d 19hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Sun 4 OctSun 27 SepMon 14 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 3 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 29 Oct, 12:16 UTC11h ago
–
–
running
1
Sun 4 Oct, 08:55 UTC25d ago
1
–
–
0
Sun 27 Sep, 23:55 UTC31d ago
1
halved by day 3
6.4 days
0
Mon 14 Sep, 12:21 UTC45d ago
1
halved by day 8
13.5 days
1
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 RiSu-Test Server. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 121.1.248.130:37600 is the address to use.
How dependable is RiSu-Test Server, and is it online at the moment?
You cannot join now: RiSu-Test Server is offline, last seen 10 hours ago. The uptime it reports puts the last restart at about 47 minutes ago. For the last 7 full days, it was up 21 of 168 hours, or 12% of the time. It was first seen by Rust Server Score on 13 September 2026.
How well does RiSu-Test Server run?
It averaged 46 server fps over the last 48 hours, with a low of 41. Buildings, deployables and everything else in the world added up to as many as 129,913 entities. Memory use reached up to 3,531 MB. When fps is low and entities climb, that is lag to players.
What Rust version is RiSu-Test Server on?
Rust network protocol 2635 and build 168909 on Linux is what RiSu-Test Server runs. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does RiSu-Test Server reset?
RiSu-Test Server wipes with the force wipe and at no other time. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 11 hours. Its tags list a monthly wipe schedule.
What should you expect from wipe day on RiSu-Test Server?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 3 hours after it began. Half the peak held until the next wipe in 0% of its recent wipes. The crowd dropped below half by day 3 in the wipes where it did not hold.
Population
What position does RiSu-Test Server hold in the rankings?
Over the last seven days, RiSu-Test Server has #9,094 for player hours, in the top 41% of all ranked servers.
How many players does RiSu-Test Server usually have?
RiSu-Test Server is offline at the moment; the last time it was seen was 10 hours ago. Averaging 0 players over seven days, it peaked at 1. The highest average in the last 48 hours came at 12:00 UTC, with 1 players.
Lists and filters
What do RiSu-Test Server's tags stand for?
You'll see RiSu-Test Server tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp2 (Max players): 2 slots are available; 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): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. 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 RiSu-Test Server?
These Rust Server Score lists count RiSu-Test Server among them: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 24 hours.
Server rules
How is RiSu-Test Server set up, and what rules does it keep?
Nothing in the name of RiSu-Test Server states a gather rate. With no change from the game default, groups take up to 8 players. pve is the mode here, no PvP between players. 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.
Can you tell me which map RiSu-Test Server uses?
The game generates the procedural map on RiSu-Test Server at size 4,500 with seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Custom Map.
Getting in
How do you get onto RiSu-Test Server?
Enter client.connect 121.1.248.130:37600 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 asmp2,ptrak,$r?,v2635,^m,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp2
Max players2 slots are available.
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
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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 performance (B); wipes are the one to work on (F).