On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 520% full
7-day average0peak –
Rank#15,338top 69%
Last wipe27d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 52 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,338 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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 213 places this week. Nothing a good wipe can't fix.
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W······
·······
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap18.1 daysbetween real wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Fri 2 OctMon 14 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 03:12 UTC27d ago
0
–
running
0
Mon 14 Sep, 00:11 UTC45d ago
0
–
18.1 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
The name of テストサーバー_ABC田中2テスト points to Asia, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 162.43.1.10:28015 is the address to use.
Is テストサーバー_ABC田中2テスト up, and how steady is its uptime?
The server is up: テストサーバー_ABC田中2テスト is online now. About 11 days 20 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Is テストサーバー_ABC田中2テスト smooth to play on?
It never fell below 224 server fps in the last 48 hours, averaging 239. At its peak, it held 3,120 entities, including buildings, deployables and all else in the world. At its highest, it used 1,156 MB of memory. When fps is low and entities climb, that is lag to players.
Which Rust version is テストサーバー_ABC田中2テスト running?
Rust network protocol 2634 and build 167781 on Linux is what テストサーバー_ABC田中2テスト runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does テストサーバー_ABC田中2テスト wipe its map?
There are too few wipes on record for テストサーバー_ABC田中2テスト to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 27 days 5 hours have passed since this world was made.
What happens on テストサーバー_ABC田中2テスト when wipe day arrives?
Recent wipes have peaked at 0 players on average. Peak numbers came 0 hours into the latest wipe.
Player count
What position does テストサーバー_ABC田中2テスト hold in the rankings?
Over the last seven days, テストサーバー_ABC田中2テスト has #15,338 for player hours, in the top 69% of all ranked servers.
How many players does テストサーバー_ABC田中2テスト usually have?
テストサーバー_ABC田中2テスト is showing 0 players right now, with 52 slots in total. Over the past seven days, the average player count was 0.
Tags
What is meant by the tags on テストサーバー_ABC田中2テスト?
You'll see テストサーバー_ABC田中2テスト tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp52 (Max players): Its slot count is 52; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here 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 テストサーバー_ABC田中2テスト?
Rust Server Score lists that include テストサーバー_ABC田中2テスト: Best community servers, graded. You can find it under these server-list filters: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does テストサーバー_ABC田中2テスト enforce, and what are its settings?
The name of テストサーバー_ABC田中2テスト gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map テストサーバー_ABC田中2テスト uses?
テストサーバー_ABC田中2テスト runs a game-generated procedural map at size 1,024, seed 50000. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: CraggyIsland.
How to join
How should you connect to テストサーバー_ABC田中2テスト?
To connect, start Rust, press F1, and type client.connect 162.43.1.10:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp52,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp52
Max playersIts slot count is 52.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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).