Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO P SRV11,899online PAX103,131playing OCC3,962with players WIPED 3H371
COMCommunity traffic
Callsign

TKO1559↓

[JP/Tokyo] Solo/Duo/Trio

Online 160.251.250.21:28015 checked 11m ago

oxide
Clearance · join
Players now 2/ 100 2% full
7-day average4peak 11
Rank#1,559top 7%
Last wipe6d agono schedule published
Next wipe–no rhythm it keeps
Track history

Players

AveragePeak
02.557.51019:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

025507510019:0004:0013:0023:0008:0017: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.

Flight plan

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.

Nearby traffic

Similar servers

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

  1. 01COM
    Callsign RST015EA · groups of 16+ · weekly · 180 on average Rustoria.co - SEA Main
    Players 356/400
  2. 02COM
    Callsign JPN002EA · groups of 16+ · weekly · 119 on average Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com
    Players 17/550
  3. 03COM
    Callsign RST015EA · groups of 12+ · monthly · 101 on average Rustoria.co - SEA Long
    Players 56/200
  4. 04COM
    Callsign RST018EA · groups of 16+ · weekly · 80 on average Rustafied.com - SEA Main
    Players 161/450
  5. 05COM
    Callsign JPN016EA · groups of 8+ · weekly · 54 on average Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]
    Players 5/200
  6. 06COM
    Callsign SMI017EA · groups of 8+ · weekly · 38 on average [ASIA] Siam Rust | Vanilla | Weekly
    Players 97/180
ATIS · this server

Quick answers

From the figures on this page.

Filters

Which Rust Tracker filters and lists carry [JP/Tokyo] Solo/Duo/Trio?

On Rust Tracker, [JP/Tokyo] Solo/Duo/Trio sits in these lists: Community servers, no tags. These filters surface it 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.

Which tags does [JP/Tokyo] Solo/Duo/Trio carry, and what do they mean?

The game's server browser reads these tags from [JP/Tokyo] Solo/Duo/Trio: gmrust (Game mode): Rust survival, standard mode; mp100 (Max players): 100 slots on this server; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): The region code is unset; ^o (Oxide): Plugin framework confirmed: Oxide (uMod). Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Schedule

What happens on [JP/Tokyo] Solo/Duo/Trio on wipe day?

The average peak across recent wipes: 5 players. The peak on the latest wipe came 32 hours after it. The crowd stayed above half the peak until the next wipe in 100% of recent wipes.

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

Wipe times at [JP/Tokyo] Solo/Duo/Trio are irregular, so no next wipe can be predicted. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. This world has been running 6 days 10 hours.

Location and Status

How reliable is [JP/Tokyo] Solo/Duo/Trio, and is it online now?

Right now [JP/Tokyo] Solo/Duo/Trio is online. The uptime it reports puts the last restart about 5 days 19 hours ago. 99% uptime over the last 7 full days, with 167 of 168 hours up. The first sighting by Rust Tracker was 13 September 2026.

Which Rust version is confirmed on [JP/Tokyo] Solo/Duo/Trio?

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

How smoothly does [JP/Tokyo] Solo/Duo/Trio run?

For the last 48 hours it averaged 73 server fps; the floor was 53. Peak entity count: 78,837, covering buildings, deployables and all else in the world. Memory peaked at 4,282 MB. Lag, as players experience it, comes from low fps and a rising entity count.

What location is [JP/Tokyo] Solo/Duo/Trio hosted in?

No region tag from [JP/Tokyo] Solo/Duo/Trio, but the name points to Asia. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 160.251.250.21:28015.

Population

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

Slots 100; players on board 2: that is [JP/Tokyo] Solo/Duo/Trio now. Seven-day average 4 players; peak 11. Busiest window in 48 hours: 15:00 UTC, 9 players on average.

How does [JP/Tokyo] Solo/Duo/Trio compare in the rankings?

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

Settings

Which settings and rules are confirmed on [JP/Tokyo] Solo/Duo/Trio?

Nothing in [JP/Tokyo] Solo/Duo/Trio's name states a gather rate. The game's default applies: groups can have up to 8 players. survival is the game mode, gather, build, raid, as the game intends. Players can raid and fight each other here. Listed under Community in the server browser, it is a community server. The plugin count stands at Oxide. VAC is on, Valve's anti-cheat.

Which map is confirmed for [JP/Tokyo] Solo/Duo/Trio?

A procedural map of size 3,500 runs on [JP/Tokyo] Solo/Duo/Trio, generated by the game from seed 17761776. Look at it on RustMaps from this page: equal size and seed return the same map.

How to Join

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

Open the console in Rust with F1 after starting the game, then type client.connect 160.251.250.21:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you. For the website, go to https://discord.com/invite/QjJSb4U6T.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Rust survival, standard mode.
mp100
Max players 100 slots on this server.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol Join only if your game is on protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code The region code is unset.

Mods and access

^o
Oxide Plugin framework confirmed: Oxide (uMod).

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.