At press time 11,763 servers72,839 players218 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 1,561

[JP/Tokyo] Solo/Duo/Trio

Online 160.251.250.21:28015 checked 7m ago

[JP/Tokyo] Solo/Duo/Trio is a Rust server. At the last count it had 3 players of a possible 100; over the past week it averaged 4, with a peak of 11. It stands at No. 1,561 of the ranked servers, the top 7%. It last wiped 6d ago. Its own tags class it as oxide.

§ 1Attendance

AveragePeak
02.557.51000:0009:0019:0003:0012:0021:00

Hourly average and peak, UTC.

§ 2Performance

025507510000:0009:0019: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.

§ 3Standingthe 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.

§ 4The wipe scheduleno rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

The rhythm
Usual gap13.9 days

between real wipes

On rhythm0%

of its recent wipes

Wipe-day peak5

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

§ 5The record of wipesnewest 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.

§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes

  1. 1 Rustoria.co - SEA Main143/200 EA · groups of 16+ · weekly · 181 on average
  2. 2 Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com1/550 EA · groups of 16+ · weekly · 119 on average
  3. 3 Rustoria.co - SEA Long32/200 EA · groups of 12+ · monthly · 100 on average
  4. 4 Rustafied.com - SEA Main50/225 EA · groups of 16+ · weekly · 79 on average
  5. 5 Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]0/200 EA · groups of 8+ · weekly · 54 on average
  6. 6 [ASIA] Siam Rust | Vanilla | Weekly29/150 EA · groups of 8+ · weekly · 38 on average

§ 7Questions answeredfrom the figures in this entry

Server details

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

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

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

The records show [JP/Tokyo] Solo/Duo/Trio online at the time of this check. A restart came about 5 days 23 hours ago, by the server's own uptime figure. In the last 7 full days it was up for 167 of 168 hours, 99% of the time. Its earliest entry at Rust Server Stats is dated 13 September 2026.

How does [JP/Tokyo] Solo/Duo/Trio perform?

Server fps averaged 71 over the last 48 hours; the low was 50. Buildings, deployables and the rest brought the entity count to a high of 78,837. Of note: memory use reached 4,282 MB. Lag, as players meet it, comes from low fps and an entity count on the rise.

In which location does [JP/Tokyo] Solo/Duo/Trio sit?

The name of [JP/Tokyo] Solo/Duo/Trio points to Asia, though no region tag is published. Where the machine stands is not looked up by Rust Server Stats; it shows where a server says it is. At 160.251.250.21:28015 stands the address.

Rules, settings, map

The map for [JP/Tokyo] Solo/Duo/Trio: which one is it?

[JP/Tokyo] Solo/Duo/Trio runs a procedural map, generated by the game, of size 3,500 with seed 17761776. RustMaps can display it from this page, since equal size and seed yield the same map.

The rules and settings of [JP/Tokyo] Solo/Duo/Trio: what are they?

Nothing in the name of [JP/Tokyo] Solo/Duo/Trio gives a gather rate. Groups are capped at 8 players, the standard default. Play is survival, gather, build and raid: the standard game. Player-versus-player fighting and raiding are enabled. It appears under Community in the server browser and is a community server. The plugin set is Oxide. VAC is enabled: Valve's anti-cheat.

Population

What population does [JP/Tokyo] Solo/Duo/Trio carry?

At the latest count [JP/Tokyo] Solo/Duo/Trio has 3 players, with 100 slots in total. Averaged across seven days, 4 players; the peak reached 11. Of the last 48 hours, 15:00 UTC drew the highest average: 9 players.

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

The seven-day player-hour table places [JP/Tokyo] Solo/Duo/Trio at #1,561, within the top 7% of ranked servers.

The tags and lists

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

On Rust Server Stats, [JP/Tokyo] Solo/Duo/Trio is placed in these lists: Best Rust community servers. On the server list it comes up under 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.

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

gmrust (Game mode): Standard survival, as Rust plays it; mp100 (Max players): 100 is the number of slots; ts8 (Group limit): Set at the game default of 8 per team; v2635 (Protocol): The game version must match protocol 2635 to join; cs168909 (Build): The build number is 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod) — that is the set of tags [JP/Tokyo] Solo/Duo/Trio publishes for the game's browser. The tags include current players, queue and the time the world was made; the top of this page shows them.

The wipes

What is the shape of wipe day on [JP/Tokyo] Solo/Duo/Trio?

The average peak across recent wipes was 5 players. 32 hours after the latest wipe, the crowd peaked. The crowd held above half the peak until the next wipe in 100% of recent wipes.

The wipe timetable for [JP/Tokyo] Solo/Duo/Trio: what does it show?

Wipes on [JP/Tokyo] Solo/Duo/Trio follow no fixed times, so no next wipe is forecast. On Thursday 5 November at 19:00 UTC the monthly force wipe takes every Rust server, without exception. Of note: the current world is 6 days 14 hours old.

Joining the server

How does one connect to [JP/Tokyo] Solo/Duo/Trio?

To connect, open the console with F1 in Rust and enter client.connect 160.251.250.21:28015. The Launch Rust and join button on this page does the same through Steam. https://discord.com/invite/QjJSb4U6T carries the server's website.

§ 8Key to the tagswhat each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays it.
mp100
Max players 100 is the number of slots.
ts8
Group limit Set at the game default of 8 per team.
v2635
Protocol The game version must match protocol 2635 to join.
cs168909
Build The build number is 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework: 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.