Rust Server TrendsSeismic network · station log
Recording Stations11,765 Players73,690 Active3,473 Wipes · 3 h229 48 h

Station XX-1565 · recording

[JP/Tokyo] Solo/Duo/Trio

Online 160.251.250.21:28015 checked 6m ago

oxide
Connect
Players now
3/ 100
3% full
Motion · 24 h
M0.0rising
+1 players on the day
7-day average
4
peak 11
Rank
#1,565
top 7%
Last wipe
6d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-1565 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
3of 100 slots
Motion · 24 h
M0.0rising+1 players
Sharpest hour
−5into Thu 17:00 UTC
Peak · 48 h
10most players in any hour
Channel 1 · calibrated

Players

AveragePeak
02.557.51023:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

025507510023:0008:0017:0003:0012:0021: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.

Channel 3 · rank movement

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.

Expected events

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 gap
13.9 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
5players, last three wipes
crowd held
100%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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 23 Oct, 08:02 UTC6d ago M0.8rising 8 – running 1
Fri 2 Oct, 11:13 UTC27d ago M0.5rising 3 held half 20.9 days 0
Fri 25 Sep, 11:07 UTC34d ago M0.6rising 4 held half 7 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rustoria.co - SEA Main EA · groups of 16+ · weekly · 181 on average
149/ 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
31/ 200
Rustafied.com - SEA Main EA · groups of 16+ · weekly · 79 on average
51/ 225
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] EA · groups of 8+ · weekly · 54 on average
0/ 200
[ASIA] Siam Rust | Vanilla | Weekly EA · groups of 8+ · weekly · 38 on average
31/ 150
Readings, in words

Quick answers

from the figures on this page

Server rules

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

[JP/Tokyo] Solo/Duo/Trio runs a procedural map of size 3,500 with seed 17761776, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

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

You will find no gather rate in the name of [JP/Tokyo] Solo/Duo/Trio. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. It is a community server, and the browser lists it under Community. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.

Player counts

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

A reading taken now shows 3 players on [JP/Tokyo] Solo/Duo/Trio, which has 100 slots. Across seven days this server recorded an average of 4 players and a peak of 11. Averaged over the last 48 hours, the busiest hour was 15:00 UTC at 9 players.

How does [JP/Tokyo] Solo/Duo/Trio rank against other Rust servers?

On player hours for the past week, [JP/Tokyo] Solo/Duo/Trio sits at #1,565, which puts it inside the top 7% of every ranked server.

Operator and location

How reliably does [JP/Tokyo] Solo/Duo/Trio stay online?

As recorded now, [JP/Tokyo] Solo/Duo/Trio is running. Going by the uptime figure it reports, it restarted about 5 days 23 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

Does [JP/Tokyo] Solo/Duo/Trio hold a steady tick rate?

The 48-hour average is 72 server fps; 50 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 78,837. Memory use peaked at 4,282 MB. Low fps together with a growing entity count is what players experience as lag.

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

The name of [JP/Tokyo] Solo/Duo/Trio points to Asia, even though it publishes no region tag. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 160.251.250.21:28015.

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

On Linux, [JP/Tokyo] Solo/Duo/Trio runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe day

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

5 players, on average, was the busiest crowd at its recent wipes. 32 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.

On what timetable does [JP/Tokyo] Solo/Duo/Trio run its wipes?

There is no next wipe to predict at [JP/Tokyo] Solo/Duo/Trio, since its wipes fall at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 6 days 14 hours is how long the current world has been running.

Tags

What do the server tags on [JP/Tokyo] Solo/Duo/Trio mean?

The game's server browser reads the tags [JP/Tokyo] Solo/Duo/Trio publishes: gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): The server has 100 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

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

The Rust Server Trends lists that take in [JP/Tokyo] Solo/Duo/Trio are: Rust community servers without the side modes. 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.

Connecting

What steps get you onto [JP/Tokyo] Solo/Duo/Trio?

To join, enter client.connect 160.251.250.21:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. For the website, go to https://discord.com/invite/QjJSb4U6T.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode You'll find standard Rust survival here.
mp100
Max players The server has 100 slots.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol Game protocol 2635: to join, your game must match this version.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.