Rust Server Analytics 52,148 players11,694 servers
All servers
Drill-through Server detail

[JP/Tokyo] Solo/Duo/Trio

Online 160.251.250.21:28015 checked 8m ago

Drill-through
FilterServeris [JP/Tokyo] Solo/Duo/Trio
Attributes
oxide
Last refreshed
Players now 3/ 100
7-day average 4 peak 11
Rank #1,567 top 7%
Last wipe 6d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 3% full

Players

average and peak, with its wipes marked
AveragePeak
02.557.51002:0011:0021:0006:0015:0000:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
025507510002:0011:0021:0006:0015:0000: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 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

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 gap13.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak5players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

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

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

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 08:02 UTC6d ago 8 – running 1
Fri 2 Oct, 11:13 UTC27d ago 3 held half 20.9 days 0
Fri 25 Sep, 11:07 UTC34d 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
ServerProfilePlayers now
Rustoria.co - SEA Main EA · groups of 16+ · weekly · 181 on average 141 / 200
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com EA · groups of 16+ · weekly · 119 on average 2 / 550
Rustoria.co - SEA Long EA · groups of 12+ · monthly · 100 on average 35 / 200
Rustafied.com - SEA Main EA · groups of 16+ · weekly · 79 on average 44 / 100
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] EA · groups of 8+ · weekly · 54 on average 2 / 200
[ASIA] Siam Rust | Vanilla | Weekly EA · groups of 8+ · weekly · 38 on average 24 / 150

Quick answers

from the figures on this page

Wipe cycle

When does [JP/Tokyo] Solo/Duo/Trio wipe?

The next wipe on [JP/Tokyo] Solo/Duo/Trio cannot be predicted, because it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. The world now in play was created 6 days 17 hours ago.

Wipe day on [JP/Tokyo] Solo/Duo/Trio: what should you expect?

The average busiest count over recent wipes is 5 players. 32 hours after the latest wipe the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Server details

In which region does [JP/Tokyo] Solo/Duo/Trio sit?

No region tag is published by [JP/Tokyo] Solo/Duo/Trio, but the name points to Asia. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. You will find it at 160.251.250.21:28015.

What Rust build does [JP/Tokyo] Solo/Duo/Trio run?

Rust network protocol 2635 and build 168909 on Linux is the setup for [JP/Tokyo] Solo/Duo/Trio. Joining requires the same protocol on your game; Steam handles the update.

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

As of the latest refresh, [JP/Tokyo] Solo/Duo/Trio is online. The uptime it reports puts the last restart at about 6 days 2 hours ago. 99% uptime over the last 7 full days, equal to 167 of 168 hours. 13 September 2026 is when Rust Server Analytics first recorded it.

Does [JP/Tokyo] Solo/Duo/Trio perform well?

Server fps averaged 71 over the last 48 hours, with a floor of 50. At its highest the entity count was 78,837, including buildings, deployables and all else. Memory use reached 4,282 MB at peak. Lag, for players, means low fps alongside a growing entity count.

Lists and tags

Which meanings do the tags on [JP/Tokyo] Solo/Duo/Trio carry?

The game's server browser reads the tags [JP/Tokyo] Solo/Duo/Trio publishes: gmrust (Game mode): Rust survival, standard ruleset; mp100 (Max players): Capacity of 100 slots; ts8 (Group limit): Default team size of 8; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Build number 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): A region code is not set; ^o (Oxide): The Oxide (uMod) plugin framework is installed. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.

On Rust Server Analytics, which lists and filters feature [JP/Tokyo] Solo/Duo/Trio?

Among the Rust Server Analytics lists [JP/Tokyo] Solo/Duo/Trio fits are: Community Rust servers, live. These filters bring it up on the server list: Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Player numbers

Against other Rust servers, how does [JP/Tokyo] Solo/Duo/Trio compare?

On player hours over seven days, [JP/Tokyo] Solo/Duo/Trio ranks #1,567, within the top 7% of ranked servers.

How many players does [JP/Tokyo] Solo/Duo/Trio carry?

[JP/Tokyo] Solo/Duo/Trio holds 3 players of its 100 slots as of the latest update. The seven-day mean is 4 players, against a peak of 11. The 48-hour peak window is 15:00 UTC, at an average of 9 players.

Map and rules

What are the settings on [JP/Tokyo] Solo/Duo/Trio, and its rules?

Gather rate is not mentioned in the name of [JP/Tokyo] Solo/Duo/Trio. No custom group limit: 8 players is the standard. It runs survival, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. The Community category in the server browser lists it. The plugin framework is Oxide. VAC, Valve's anti-cheat, is enabled.

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

The game generates a procedural map of size 3,500 with seed 17761776 for [JP/Tokyo] Solo/Duo/Trio. The map is reproducible from its size and seed and can be seen on RustMaps from here.

Connection

What is the way onto [JP/Tokyo] Solo/Duo/Trio?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 160.251.250.21:28015. https://discord.com/invite/QjJSb4U6T is its website.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o

Game

gmrust
Game mode Rust survival, standard ruleset.
mp100
Max players Capacity of 100 slots.
ts8
Group limit Default team size of 8.
v2635
Protocol Joining needs your game on protocol 2635.
cs168909
Build Build number 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code A region code is not set.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.

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.