Rust Wipe StatsWipe forecast
Now 47,205 players 11,672 servers 97 fresh wipes in 3 h

Local forecast

[JP/Tokyo] Solo/Duo/Trio

Online 160.251.250.21:28015 checked 6m ago

oxide

Current conditions

observed 6m ago
3 / 100
players now
Quiet H 11 · avg 4 7-day high and average

3% full

7-day average
4
peak 11
Rank
#1,563
top 7%
Last wipe
6d ago
no schedule published
Next wipe
–
no rhythm it keeps

Next wipe

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.

Players

AveragePeak
02.557.51003:0012:0022:0007:0016:0001:00

Hourly average and peak, UTC.

Server performance

025507510003:0012:0022:0007:0016:0001: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.

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

Past weather: its wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 09:02 UKFri 23 Oct, 08:02 UTC · 6d ago 8 – running 1
Fri 2 Oct, 12:13 UKFri 2 Oct, 11:13 UTC · 27d ago 3 held half 20.9 days 0
Fri 25 Sep, 12:07 UKFri 25 Sep, 11:07 UTC · 34d 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. The weather: fair when the crowd held, showers when it halved within two days, a storm for the force wipe.

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rustoria.co - SEA Main EA · groups of 16+ · weekly · 180 on average
127/ 200
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com EA · groups of 16+ · weekly · 119 on average
4/ 550
Rustoria.co - SEA Long EA · groups of 12+ · monthly · 100 on average
25/ 200
Rustafied.com - SEA Main EA · groups of 16+ · weekly · 79 on average
53/ 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 · 37 on average
40/ 150

Quick answers

from the figures on this page

About the server

Is performance good on [JP/Tokyo] Solo/Duo/Trio?

Across the last 48 hours the average was 71 server fps, with a floor of 50. At its peak the world had 78,837 entities, counting buildings, deployables and the rest. Memory use reached 4,282 MB at its peak. Players feel lag when fps drops and the entity count climbs.

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

As of now, [JP/Tokyo] Solo/Duo/Trio is online. The uptime it reports puts the last restart about 6 days 3 hours ago. In the last 7 full days it stayed up 167 of 168 hours, 99% of the time. It came to Rust Wipe Stats's notice first on 13 September 2026.

Where does [JP/Tokyo] Solo/Duo/Trio run from?

No region tag is published by [JP/Tokyo] Solo/Duo/Trio, but the name suggests Asia. Where a server says it is, that is what Rust Wipe Stats shows; it does not look up the machine's actual location. 160.251.250.21:28015 is its address.

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

On [JP/Tokyo] Solo/Duo/Trio you will find Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you; the protocol must match to join.

Server tags

What do [JP/Tokyo] Solo/Duo/Trio's tags tell you?

The server browser reads these tags from [JP/Tokyo] Solo/Duo/Trio: gmrust (Game mode): The mode is plain Rust survival; mp100 (Max players): It holds 100 players; ts8 (Group limit): The default cap of 8 per team applies here; v2635 (Protocol): Joining needs game protocol 2635 on your copy of the game; cs168909 (Build): Build 168909 is installed here; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region has been set; ^o (Oxide): It runs on Oxide, also called uMod, for plugins. The tags also carry the current players, the queue and when the world was created; you will find them at the top of this page.

Where does [JP/Tokyo] Solo/Duo/Trio appear among the Rust Wipe Stats lists and filters?

These Rust Wipe Stats lists include [JP/Tokyo] Solo/Duo/Trio: Community Rust servers. 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.

Settings and rules

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

[JP/Tokyo] Solo/Duo/Trio runs a procedural map of size 3,500, seed 17761776, made by the game. You can look at it on RustMaps from this page: same size and seed, same map.

What settings does [JP/Tokyo] Solo/Duo/Trio use, and what rules does it enforce?

Gather rate is not given in the name for [JP/Tokyo] Solo/Duo/Trio. The default of 8 players is the group limit here. survival is the game mode, the usual game of gathering, building and raiding. Raiding and player combat are both allowed. You will find it under Community in the server browser. Plugin frameworks in use: Oxide. This server has VAC switched on.

Wipe schedule

Which days and times does [JP/Tokyo] Solo/Duo/Trio schedule its wipes for?

There is no next wipe to predict, because [JP/Tokyo] Solo/Duo/Trio wipes at irregular times. The next monthly force wipe, which every Rust server takes, is on Thursday 5 November at 19:00 UTC. The current map and world began 6 days 18 hours.

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

At their busiest, its recent wipes averaged 5 players. The crowd on the latest wipe reached its high 32 hours in. Half the peak or more lasted to the next wipe in 100% of its recent wipes.

Population

Is [JP/Tokyo] Solo/Duo/Trio busy or quiet?

Out of 100 slots, [JP/Tokyo] Solo/Duo/Trio has 3 filled right now. Averaged over seven days: 4 players, peaking at 11. Its busiest point in the last 48 hours was 15:00 UTC, averaging 9 players.

What position does [JP/Tokyo] Solo/Duo/Trio hold among Rust servers?

The last seven days of player hours rank [JP/Tokyo] Solo/Duo/Trio at #1,563, in the top 7% of ranked servers.

How to join

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

Two ways in: press F1 and enter client.connect 160.251.250.21:28015, or join from this page with Launch Rust, which opens Steam and connects you. 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 The mode is plain Rust survival.
mp100
Max players It holds 100 players.
ts8
Group limit The default cap of 8 per team applies here.
v2635
Protocol Joining needs game protocol 2635 on your copy of the game.
cs168909
Build Build 168909 is installed here.
ptrak
Networking Networking runs on RakNet, the game's standard layer.
$r?
Region code No region has been set.

Mods and access

^o
Oxide It runs on Oxide, also called uMod, for plugins.

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.