Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
No daily history yet.
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
No rank history yet.
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
The name of DEATH GAME練習サーバー points to Asia, though no region tag is set. Rust Server Score takes the server's word for its location and does not trace the hardware. 82.21.2.7:10255 is the address to use.
How reliable is DEATH GAME練習サーバー, and is it up?
You cannot join now: DEATH GAME練習サーバー is offline, last seen 44 days 16 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is DEATH GAME練習サーバー on?
Rust network protocol 2632 and build 161125 on Linux is what DEATH GAME練習サーバー runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does DEATH GAME練習サーバー wipe, and how often?
There are too few wipes on record for DEATH GAME練習サーバー to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 62 days 2 hours.
Player count
Is DEATH GAME練習サーバー a busy server?
DEATH GAME練習サーバー is offline at the moment; the last time it was seen was 44 days 16 hours ago.
Tags and filters
What is meant by the tags on DEATH GAME練習サーバー?
gmrust (Game mode): Survival in the standard Rust style; mp55 (Max players): The server holds 55 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2632 (Protocol): The game protocol is 2632, so your game must match that version to join; cs161125 (Build): This runs on build 161125; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags DEATH GAME練習サーバー publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show DEATH GAME練習サーバー?
These Rust Server Score lists count DEATH GAME練習サーバー among them: Modded Rust servers, graded. You can find it under these server-list filters: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What settings and rules apply on DEATH GAME練習サーバー?
The name of DEATH GAME練習サーバー gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on DEATH GAME練習サーバー?
The game generates a procedural map for DEATH GAME練習サーバー.
Getting in
How should you connect to DEATH GAME練習サーバー?
Enter client.connect 82.21.2.7:10255 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 asmp55,ptrak,$r?,v2632,gmrust,cs161125,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp55
Max playersThe server holds 55 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2632
ProtocolThe game protocol is 2632, so your game must match that version to join.
cs161125
BuildThis runs on build 161125.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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.
Not enough figures yet to write a report. Check back after a few days on the list.