Skip to the story

Live edition102,658 playing on 11,891 servers

Rust Insights

Server profile

[JP/Tokyo] Solo/Duo/Trio

Online, with 2 of 100 players on; ranked #1,559 of every public Rust server, the top 7%. It last wiped 6d ago.

Filed under oxide
Launch Rust and join Website
The server's own banner, as it publishes it.
2/ 100 players now 2% full
47-day averagepeak 11
#1,559ranktop 7%
6d agolast wipeno schedule published
–next wipeno rhythm it keeps

The crowd

Players

Who is on it, hour by hour and day by day.

AveragePeak
02.557.51019:0004:0013:0022:0007:0016:00

Note: hourly average and peak, UTC.

Under the hood

Server performance

Frames per second, entities and memory, asked of the server itself.

025507510019:0004:0013:0022:0007:0016:00

Note: 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.

The standings

Rank

Its place among every ranked server, day by day; 1 is best.

RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

The wipe cycle

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.

13.9 days usual gap between real wipes
0% on rhythm of its recent wipes
5 wipe-day peak players, last three wipes
100% crowd held of its cycles kept half the crowd

The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe

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

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

The record

Wipes

Every wipe we saw, 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

Note: 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.

If you like this one

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. Rustoria.co - SEA MainEA · groups of 16+ · weekly · 180 on average347/400
  2. Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.comEA · groups of 16+ · weekly · 119 on average16/550
  3. Rustoria.co - SEA LongEA · groups of 12+ · monthly · 101 on average60/200
  4. Rustafied.com - SEA MainEA · groups of 16+ · weekly · 80 on average165/450
  5. Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]EA · groups of 8+ · weekly · 54 on average5/200
  6. [ASIA] Siam Rust | Vanilla | WeeklyEA · groups of 8+ · weekly · 38 on average102/180

The short version

Quick answers

From the figures on this page.

Wipe days

What should you expect on wipe day at [JP/Tokyo] Solo/Duo/Trio?

The average busiest point of its recent wipes was 5 players. The peak crowd on this wipe came 32 hours after it started. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

On what schedule does [JP/Tokyo] Solo/Duo/Trio wipe?

[JP/Tokyo] Solo/Duo/Trio wipes at times that vary, so its next wipe cannot be predicted. The monthly force wipe comes to all Rust servers next on Thursday 5 November at 19:00 UTC. This world dates from 6 days 10 hours ago.

About the server

What does performance look like on [JP/Tokyo] Solo/Duo/Trio?

Average server fps over the last 48 hours was 73, with a floor of 53. Buildings, deployables and the rest took the entity count as high as 78,837. Memory use peaked at 4,282 MB. Lag, for players, is low fps and an entity count that keeps climbing.

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

Running on Linux, [JP/Tokyo] Solo/Duo/Trio is on Rust network protocol 2635 and build 168909. You can only join if your game is on the same protocol; Steam handles that update.

How reliable is [JP/Tokyo] Solo/Duo/Trio, and is it up at the moment?

At the time of this check [JP/Tokyo] Solo/Duo/Trio is online. Going by the uptime figure it gives, its last restart was around 5 days 18 hours ago. The last 7 full days gave 167 of 168 hours up, or 99% of the time. Rust Insights first logged this server on 13 September 2026.

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

[JP/Tokyo] Solo/Duo/Trio publishes no region tag, but Asia is where its name points. The location shown on Rust Insights is the one a server states, not a lookup of where the machine sits. You can reach it at 160.251.250.21:28015.

Tags

Which meanings sit behind the tags on [JP/Tokyo] Solo/Duo/Trio?

The tags gmrust (Game mode): Survival as standard Rust plays; mp100 (Max players): 100 slots in total; ts8 (Group limit): The game default applies: teams cap at 8; v2635 (Protocol): To join you need the same version; protocol 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): Rust's standard network layer, RakNet, carries it; $r? (Region code): The region code field is empty; ^o (Oxide): A plugin framework, Oxide (uMod), is in use are what [JP/Tokyo] Solo/Duo/Trio publishes, and the server browser in the game reads them. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.

On which Rust Insights lists does [JP/Tokyo] Solo/Duo/Trio appear?

[JP/Tokyo] Solo/Duo/Trio appears among the following Rust Insights lists: Best Rust community servers. You will find it on the server list by applying these filters: 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.

Population history

How many players are on [JP/Tokyo] Solo/Duo/Trio right now?

Of its 100 slots, [JP/Tokyo] Solo/Duo/Trio currently has 2 filled. The seven-day average is 4 players, and the highest point in that week was 11. The busiest point of the last 48 hours fell at 15:00 UTC, averaging 9 players.

In the ranking of Rust servers, where does [JP/Tokyo] Solo/Duo/Trio place?

Player hours over seven days put [JP/Tokyo] Solo/Duo/Trio at #1,559, within the top 7% of the ranked field.

Settings and rules

What settings and rules apply on [JP/Tokyo] Solo/Duo/Trio?

The name of [JP/Tokyo] Solo/Duo/Trio does not state a gather rate. Groups can reach 8 players, which is the default in the game. You get survival as the game mode, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Community is the browser category it appears in. Oxide is the plugin count it runs. VAC is on: Valve's anti-cheat is active.

Which map is live on [JP/Tokyo] Solo/Duo/Trio?

[JP/Tokyo] Solo/Duo/Trio runs a procedural map of size 3,500 with seed 17761776, generated by the game. The same size and seed produce the same map, so from this page you can look at it on RustMaps.

Join

How do you connect to [JP/Tokyo] Solo/Duo/Trio?

Type client.connect 160.251.250.21:28015 into the console, which you open with F1 in Rust. The Launch Rust button on this page does the same job by opening Rust through Steam. You will find its website at https://discord.com/invite/QjJSb4U6T.

The small print

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp100
Max players 100 slots in total.
ts8
Group limit The game default applies: teams cap at 8.
v2635
Protocol To join you need the same version; protocol 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking Rust's standard network layer, RakNet, carries it.
$r?
Region code The region code field is empty.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), is in use.

Note: 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.