Rust Data

rustdata.spaceservers162.222.17.4:30131.ipynb

Run all rust-data · live

‹ All servers

Offline 162.222.17.4:30031 checked 4d ago

Hard

moddedcarbonpve

Connect

srv = rust.server("162.222.17.4:30131")
print(srv.connect_command)

Right now

srv.summary()
players now 0/?
7-day average 0 # peak –
rank #15,383 # top 70%
last wipe 25d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 22 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap3.3 daysbetween real wipes
on rhythm14%of its recent wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Tue 20 OctSat 17 OctSat 3 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 20 Oct, 14:47 UTC7d ago 0 NaN running 0
1 Sat 17 Oct, 08:07 UTC10d ago 0 NaN 3.3 days 0
2 Sat 3 Oct, 16:40 UTC24d ago 1 halved by day 1 13.6 days 0
3 Fri 2 Oct, 11:22 UTC25d ago 1 NaN 1.2 days 0
4 Thu 1 Oct, 12:22 UTC26d ago 1 NaN 1 days 1
5 Thu 1 Oct, 05:28 UTC26d ago 1 NaN 0.3 days 0
6 Tue 22 Sep, 06:07 UTC35d ago 1 halved by day 1 9 days 0
7 Fri 4 Sep, 16:17 UTC53d ago 1 halved by day 2 17.6 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.

display(srv.map, srv.info())

Map

5500 · seed 0
Custom map, no picture published
map
Custom Map
size
5500
seed
–

Server

srv.info()
address
162.222.17.4:30031
region
–
max players
–
group limit
16 max
wipe schedule
–
last wipe
2 Oct 2026, 08:46 UTC
hostname
pvemod.japantokyo.jp
first seen
13 Sep 2026

Operator · japantokyo.jp

rust.servers(operator="japantokyo.jp").sort_values("players")

4 servers publish a japantokyo.jp hostname.

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 243 on average232/2000
1[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 231 on average373/2000
2Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 95 on average111/200
3【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average30/200
4Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsidgroups of 8+ · biweekly · 54 on average43/250
5[US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 53 on average37/200

Quick answers

From the figures on this page.

Player counts

What position does Hard take in the server rankings?

Player hours over seven days put Hard at #15,383, in the top 70% of the ranked set.

How many players does Hard hold at once?

Hard returns no live count at this refresh, having last been seen 4 days 22 hours ago. Over the last seven days it averaged 0 players.

Server facts

What Rust version does Hard run?

Rust network protocol 2634 and build 167781 on Linux is what Hard runs. The protocol has to match before you can join, and Steam does the updating.

Is Hard up, and what does its uptime show?

Hard is offline at this refresh; the last response came 4 days 22 hours ago. Over the last 7 full days the hours up number 54 of 168, 32%. The first row Rust Data holds for it is dated 13 September 2026.

In which location is Hard hosted?

For Hard, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 162.222.17.4:30031.

Map and rules

Which settings and rules does Hard run?

You will not find a gather rate in the string Hard. Group size tops out at 16 players. Game mode pve, with this note: player combat is not allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. Anti-cheat status: VAC off.

Which map has Hard loaded?

Generated by the game at size 5,500, the map on Hard is procedural. Under map name you will find: Custom Map.

Wipe schedule

On what schedule does Hard wipe?

Hard wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 25 days 10 hours ago.

What is wipe day on Hard like?

Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.

Tags, lists

Which Rust Data filters and lists contain Hard?

The Rust Data lists that Hard fits are: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.

Which operator runs Hard?

A japantokyo.jp hostname is published by Hard and by 3 other servers we track, which suggests the same operator runs them.

How should you read the server tags on Hard?

Read by the game's server browser, the tags Hard publishes are: gmrust (Game mode): Survival play, standard Rust; mp0 (Max players): 0 slots in total; ts16 (Group limit): Team size tops out at 16; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way to join Hard?

Enter client.connect 162.222.17.4:30031 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp0,ptrak,$r?,v2634,^z,^y,^p,gmrust,cs167781,ts16

Game

gmrust
Game mode Survival play, standard Rust.
mp0
Max players 0 slots in total.
ts16
Group limit Team size tops out at 16.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167781
Build The server runs build 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Gameplay

^p
PvE Players do not fight each other here; the world supplies the danger.

Mods and access

^z
Modded Plugins or settings alter the game, so it sits under Modded.
^y
Carbon The plugin framework in use is Carbon.

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.

Rust Data 93,191 players 11,886 servers online