On the class lists: D (54), with population over 48 hours and no performance mark.
Players now2/ 504% full
7-day average0peak 4
Rank#4,390top 20%
Last wipe15d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
80/ 100
B+
Holds a respectable place: #4,390 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
100/ 100
A+
Runs smoothly: 239 server fps on average.
Wipeskeeping the crowd after a wipe
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
59/ 100
C−
Moving up: up 774 places this week.
A fair term, with more to come.
Strongest in performance (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 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 20% 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
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap5.6 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak3players, last three wipes
crowd held33%else halves by day 1
The first 48 hours of its last wipes
Wed 14 OctThu 8 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 4, 6 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 14 Oct, 07:09 UTC15d ago
4
–
running
0
Thu 8 Oct, 16:02 UTC20d ago
4
halved by day 1
5.6 days
0
Fri 2 Oct, 03:08 UTC27d ago
1
halved by day 1
6.5 days
0
Tue 29 Sep, 04:50 UTC30d ago
3
✓ held half
2.9 days
0
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 won't find a region tag on テストサーバー, but its name indicates Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 157.85.88.112:29581 is the address to use.
Is テストサーバー up, and how steady is its uptime?
The server is up: テストサーバー is online now. The uptime it reports puts the last restart at about 3 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Does テストサーバー perform well?
It never fell below 224 server fps in the last 48 hours, averaging 239. At its peak, it held 66,967 entities, including buildings, deployables and all else in the world. At its highest, it used 4,075 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is テストサーバー on?
You will find テストサーバー on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
When does テストサーバー wipe, and how often?
No next wipe can be predicted for テストサーバー, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 15 days 4 hours.
What should you expect from wipe day on テストサーバー?
Recent wipes have peaked at 3 players on average. 6 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 33% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Player count
What position does テストサーバー hold in the rankings?
Over the last seven days, テストサーバー has #4,390 for player hours, in the top 20% of all ranked servers.
How many players does テストサーバー usually have?
With 50 slots available, テストサーバー currently has 2 players. The seven-day average is 0 players, with a peak of 4. The highest average in the last 48 hours came at 08:00 UTC, with 3 players.
Tags and filters
What is meant by the tags on テストサーバー?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): Its slot count is 50; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^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): The game is changed by plugins or settings; you will find it under Modded are the tags テストサーバー publishes, and the game's server browser reads them. 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 テストサーバー appear in the Rust Server Score lists and filters?
These Rust Server Score lists count テストサーバー among them: Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does テストサーバー enforce, and what are its settings?
The name of テストサーバー gives no gather rate. The group limit stays at the game's default of 8 players. pve is the mode here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on テストサーバー?
The game generates the procedural map on テストサーバー at size 3,000 with seed 1. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto テストサーバー?
To connect, start Rust, press F1, and type client.connect 157.85.88.112:29581. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/uk2Bfmnea.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersIts slot count is 50.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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
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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).