Skip to the page
Network live 11,859 servers online 101,852 players aboard 538 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

[JP/Tokyo] Solo/Duo/Trio

Online 160.251.250.21:28015 checked 9m ago

oxide
Tracking number · connect
Wipe progress · wiped 6d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
1/ 100 players now 1% full
47-day averagepeak 11
#1,561ranktop 7%
6d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeak
02.557.51021:0006:0015:0000:0009:0018:00

Hourly average and peak, UTC.

Server performance

025507510021:0006:0015:0000:0009:0018: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 Oct13 Oct21 Oct29 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.

13.9 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
5wipe-day peakplayers, last three wipes
100%crowd heldof 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

every wipe as a delivery, newest first
  1. Fri 23 Oct, 08:02 UTC 09:02 UK · 6d ago
    Wipe delivered
    Peak
    8
    Crowd
    –
    Lasted
    running
    Players before
    1
  2. Fri 2 Oct, 11:13 UTC 12:13 UK · 27d ago
    Wipe delivered
    Peak
    3
    Crowd
    held half
    Lasted
    20.9 days
    Players before
    0
  3. Fri 25 Sep, 11:07 UTC 12:07 UK · 34d ago
    Wipe delivered
    Peak
    4
    Crowd
    held half
    Lasted
    7 days
    Players before
    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 parcels

Similar servers

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

  1. Rustoria.co - SEA MainEA · groups of 16+ · weekly · 181 on average 247 / 300
  2. Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.comEA · groups of 16+ · weekly · 119 on average 9 / 550
  3. Rustoria.co - SEA LongEA · groups of 12+ · monthly · 101 on average 51 / 200
  4. Rustafied.com - SEA MainEA · groups of 16+ · weekly · 80 on average 133 / 250
  5. Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]EA · groups of 8+ · weekly · 54 on average 1 / 200
  6. [ASIA] Siam Rust | Vanilla | WeeklyEA · groups of 8+ · weekly · 38 on average 58 / 180
Help desk

Quick answers

From the figures on this page.

Player count

How does [JP/Tokyo] Solo/Duo/Trio compare with other Rust servers in the rankings?

A seven-day player-hours count places [JP/Tokyo] Solo/Duo/Trio at #1,561: the top 7% of every ranked server.

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

The current count is 1 players on 100 slots for [JP/Tokyo] Solo/Duo/Trio. The seven-day figures show an average of 4 players and a peak of 11. The busiest hour over the last 48 hours was 15:00 UTC, averaging 9 players.

Rules and settings

On what map does [JP/Tokyo] Solo/Duo/Trio take place?

The game generates the procedural map on [JP/Tokyo] Solo/Duo/Trio at size 3,500 with seed 17761776. Size and seed match means the map matches, so you can view it on RustMaps from this page.

What settings and rules should you know for [JP/Tokyo] Solo/Duo/Trio?

The name of [JP/Tokyo] Solo/Duo/Trio gives no gather rate. 8 players is the group limit, since the game's default applies. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players is allowed. The server browser files it under Community, as a community server. Plugins come from Oxide. The VAC anti-cheat from Valve is enabled.

Operator and location

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

The name of [JP/Tokyo] Solo/Duo/Trio points to Asia, though no region tag is published. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. The address to connect to is 160.251.250.21:28015.

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

The 48-hour average for server fps stands at 73, never dipping below 53. The world held as many as 78,837 entities: buildings, deployables and the rest. The highest memory reading was 4,282 MB. Lag, to players, means low fps alongside an entity count on the rise.

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

Right now, [JP/Tokyo] Solo/Duo/Trio is online. About 5 days 20 hours ago is when it last restarted, judged by the uptime it gives. 99% is the uptime for the last 7 full days, up for 167 of 168 hours. It was first seen by Rust Wipe Tracker on 13 September 2026.

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

On Linux, [JP/Tokyo] Solo/Duo/Trio runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles that update for you.

Map resets

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

The average busiest point of its recent wipes was 5 players. On the latest wipe, 32 hours passed before the crowd peaked. Until the next wipe, the crowd stayed over half the peak in 100% of recent cases.

On what schedule does [JP/Tokyo] Solo/Duo/Trio reset its map?

[JP/Tokyo] Solo/Duo/Trio wipes when it chooses, not on a fixed rhythm, so there is no next wipe to predict. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. 6 days 12 hours have passed since this world was made.

Server tags

On Rust Wipe Tracker, which lists and filters is [JP/Tokyo] Solo/Duo/Trio part of?

You will find [JP/Tokyo] Solo/Duo/Trio on the following Rust Wipe Tracker lists: Rust community servers, unmodded. On the server list, apply 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 and it appears.

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

gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): The server has 100 slots; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): A region code isn't set; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here are the tags [JP/Tokyo] Solo/Duo/Trio publishes, and the server browser takes them as read. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

How to join

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

Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 160.251.250.21:28015. Its website can be found at https://discord.com/invite/QjJSb4U6T.

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players The server has 100 slots.
ts8
Group limit 8 per team, which is the default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code A region code isn't set.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed here.

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.