Skip to the page
RUST ANALYTICS
LIVE47,399PLY11,539SRV
QUOTE 160.251.250.21:28015 Online checked 9m ago

[JP/Tokyo] Solo/Duo/Trio

Players · last
1/ 100
+0+0.0%24h
1% full
Day range 1 4
7-day avg 3 peak 7
Players · 24 hourshourly average, then now · dashed: 24 hours ago
Launch Rust and join Website

Key statistics

the figures behind the quote
Players now
1/ 100
1% full
Change · 24h
+0
+0.0% from 1
7-day average
3
peak 7
Rank
#2,065
top 9%
Rank · 7d ago
#3,656
1591 places up
Last wipe
12d ago
no schedule published
Next wipe
–
too few wipes seen yet
Group limit
8
8, the default
Gather rate
–
no rate in the name
Score
426
player hours, last seven days
Map
3500
Procedural Map · seed 714728274
First seen
13 Sep 2026
no hostname published

Players

AveragePeak
0123400:0009:0018:0004:0013:0022:00

Hourly average and peak, UTC. Busiest hour of the two days: 4 players.

Server performance

05010015020000:0009:0018:0004:0013:0022:00

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
11k2k3k4k20 Sep25 Sep30 Sep4 Oct9 Oct14 Oct

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

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 gap
7 days
between real wipes
wipe-day peak
4
players, last three wipes
crowd held
100%
of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 2 OctFri 25 Sep
01234+0h+9h+19h+28h+38h+47h

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 11:13 UTC12d ago 3 – running 0
Fri 25 Sep, 11:07 UTC19d ago 4 held half 7 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

the same kind of game, then region, group limit, rate and wipes
#ServerLastChg 24hPlayers over the last 24 hours24h
1Rustoria.co - SEA LongEA · groups of 12+ · monthly · 197 on average105/200+19+21.5%
2Rustoria.co - SEA MainEA · groups of 16+ · weekly · 144 on average14/200−8−37.4%
3Japan Tokyo - Main|10/09|JP/KR/SEA|金曜日|JumpRust.comEA · groups of 16+ · weekly · 97 on average8/415−2−21.4%
4Rustafied.com - SEA LongEA · groups of 16+ · monthly · 95 on average30/100−8−20.5%
5Rustafied.com - SEA MainEA · groups of 16+ · weekly · 76 on average4/100−7−63.0%
6[SEA] Facepunch Premium 1EA · groups of 8+ · monthly · 58 on average31/250+0+0.3%

Quick answers

from the figures on this page

Map and Rules

How is [JP/Tokyo] Solo/Duo/Trio configured in terms of rules and settings?

No gather rate is given in the name of [JP/Tokyo] Solo/Duo/Trio. Groups can contain a maximum of 8 players, the default for the game. It runs survival, gather, build and raid in the standard game. PvP and raiding are enabled. You will find it under Community in the server browser: it is a community server. VAC is active.

What is the current map on [JP/Tokyo] Solo/Duo/Trio?

The map on [JP/Tokyo] Solo/Duo/Trio is procedural, size 3,500, with seed 714728274, and generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page.

Activity

Where does [JP/Tokyo] Solo/Duo/Trio sit in the rankings?

For the last seven days, [JP/Tokyo] Solo/Duo/Trio holds rank #2,065 on player hours, in the top 9% of all ranked servers.

What is the population on [JP/Tokyo] Solo/Duo/Trio?

1 of 100 slots on [JP/Tokyo] Solo/Duo/Trio are filled at the moment. Average players over seven days: 3; peak: 7. The busiest hour in the last 48 hours was 13:00 UTC, with an average of 4 players.

Wipe Schedule

What can you expect on wipe day for [JP/Tokyo] Solo/Duo/Trio?

An average of 4 players marked the busiest point of its recent wipes. On the latest wipe, 1 hours after the wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

When does [JP/Tokyo] Solo/Duo/Trio schedule its wipes?

No rhythm can be told for [JP/Tokyo] Solo/Duo/Trio yet: too few of its wipes are on record. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. This world has been running for 12 days 12 hours.

Server Info

What is the server location for [JP/Tokyo] Solo/Duo/Trio?

No region tag is published by [JP/Tokyo] Solo/Duo/Trio, though its name points to Asia. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 160.251.250.21:28015.

How is the performance on [JP/Tokyo] Solo/Duo/Trio?

Server fps over the last 48 hours: 80 on average, 58 at the lowest. At its peak it held 74,570 entities: buildings, deployables and the rest of the world. Up to 4,019 MB of memory was used. A climbing entity count plus low fps is the lag players report.

What Rust version is [JP/Tokyo] Solo/Duo/Trio running?

The build is Rust network protocol 2634 and build 166652 on Linux, running on [JP/Tokyo] Solo/Duo/Trio. Your game needs the same protocol to get in; Steam takes care of the update.

Is [JP/Tokyo] Solo/Duo/Trio up, and how consistent is its uptime?

[JP/Tokyo] Solo/Duo/Trio is up. It is taking players now. The reported uptime puts its last restart at about 10 days 8 hours ago. The last 7 full days give 100% uptime, 168 hours on out of 168. The earliest Rust Analytics saw it was 13 September 2026.

Server Tags

How should you interpret the tags on [JP/Tokyo] Solo/Duo/Trio?

Published by [JP/Tokyo] Solo/Duo/Trio for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): Capacity: 100 slots; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): To join, your game needs protocol 2634; cs166652 (Build): Game build: 166652; ptrak (Networking): The standard network layer, RakNet; $r? (Region code): Region code: none set. The tags also carry its current players, queue and world creation time; this page shows them at the top.

[JP/Tokyo] Solo/Duo/Trio appears in which of the lists and filters on Rust Analytics?

These Rust Analytics lists include [JP/Tokyo] Solo/Duo/Trio: Rust community servers. It appears under these filters on the server list: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How to Join

What steps do I take to join [JP/Tokyo] Solo/Duo/Trio?

The console route: start Rust, press F1, enter client.connect 160.251.250.21:28015. The page's Launch Rust button opens Rust through Steam and connects you instead. You can visit its website at https://discord.com/invite/QjJSb4U6T.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players Capacity: 100 slots.
ts8
Group limit Team size stays at the game default of 8.
v2634
Protocol To join, your game needs protocol 2634.
cs166652
Build Game build: 166652.
ptrak
Networking The standard network layer, RakNet.
$r?
Region code Region code: none set.

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.