Rust StatisticsWorking papers on every public Rust server · 60,571 players now

[JP/Tokyo] Solo/Duo/Trio

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 14m ago · 160.251.250.21:28015

Abstract

We describe the public Rust server [JP/Tokyo] Solo/Duo/Trio, reached at 160.251.250.21:28015. At the last check it held 3 of 100 places, against a seven-day mean of 4 and a peak of 111. It ranks #1,565 of all servers, the top 7%. It last wiped 6d ago.

Keywordsoxide

Access. Launch Rust and join Website ‹ all servers

1Summary statistics

Plate 1: The server's own banner, as it publishes it. Table 1 gives its figures at the last check.
Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now3/1003% full
In the queue0no queue
Seven-day mean4peak 11, 48 h peak 10
Rank2#1,565top 7%
Last wipe6d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
02.557.51001:0010:0020:0005:0014:0023:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
025507510001:0010:0020:0005:0014:0023:00
Figure 2: Server performance. 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.

4Rank

The server stands in the top 7% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
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
Fri 23 OctFri 2 OctFri 25 Sep
02468+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 8, 32 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 23 Oct, 08:026d ago 8 – running 1
Fri 2 Oct, 11:1327d ago 3 held half 20.9 d 0
Fri 25 Sep, 11:0734d ago 4 held half 7 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of [JP/Tokyo] Solo/Duo/Trio
Figure 5: The map: Procedural Map, size 3500, seed 17761776. Open on RustMaps.
Table 4: The server's published settings.
Address160.251.250.21:28015
Region–
Max players100
Group limit8, the default
Wipe schedule–
Last wipe23 Oct 2026, 08:02 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size3500
Seed17761776

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are player-run rust server list [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rustoria.co - SEA MainEA · groups of 16+ · weekly · 181 on average133/200
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.comEA · groups of 16+ · weekly · 119 on average0/550
Rustoria.co - SEA LongEA · groups of 12+ · monthly · 100 on average28/200
Rustafied.com - SEA MainEA · groups of 16+ · weekly · 79 on average39/100
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]EA · groups of 8+ · weekly · 54 on average1/200
[ASIA] Siam Rust | Vanilla | WeeklyEA · groups of 8+ · weekly · 38 on average23/150

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of [JP/Tokyo] Solo/Duo/Trio smooth?

Its average server fps over the last 48 hours was 71, with a minimum of 50. The highest number of entities it carried was 78,837, comprising buildings, deployables and all other objects. Its highest memory usage was 4,282 MB. When fps is low and entity count climbs, players feel lag.

A.2In which location is [JP/Tokyo] Solo/Duo/Trio based?

Its name points to Asia, though [JP/Tokyo] Solo/Duo/Trio publishes no region tag. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 160.251.250.21:28015 is its address.

A.3What is the reliability of [JP/Tokyo] Solo/Duo/Trio, and is it online?

At the present moment, [JP/Tokyo] Solo/Duo/Trio is online. Based on the uptime it reports, the last restart occurred about 6 days 1 hours ago. Of the 168 hours in the last 7 full days, 143 were served, an availability of 85%. The first record of it by Rust Statistics dates to 13 September 2026.

A.4What version of Rust is run on [JP/Tokyo] Solo/Duo/Trio?

The version of Rust on [JP/Tokyo] Solo/Duo/Trio is network protocol 2635 and build 168909, and the operating system is Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.5On what cycle does [JP/Tokyo] Solo/Duo/Trio wipe?

Prediction of the next wipe is impossible for [JP/Tokyo] Solo/Duo/Trio, which wipes irregularly. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 6 days 16 hours have passed since the current world was generated.

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

Across its recent wipes, the average peak population was 5 players. The crowd reached its maximum 32 hours after the latest wipe. Half the peak was sustained until the next wipe in 100% of recent wipes.

Player count

A.7What position does [JP/Tokyo] Solo/Duo/Trio occupy in the ranking of Rust servers?

Ranked by player hours across seven days, [JP/Tokyo] Solo/Duo/Trio holds #1,565, in the top 7% of all ranked servers.

A.8How would you characterise the player activity on [JP/Tokyo] Solo/Duo/Trio?

On [JP/Tokyo] Solo/Duo/Trio, 3 of the 100 slots are occupied at present. Averaged over the last seven days: 4 players; the same period peaks at 11. Averaging 9 players, 15:00 UTC was the busiest hour of the past 48.

Tags, lists

A.9How should the tags on [JP/Tokyo] Solo/Duo/Trio be interpreted?

The game's server browser reads gmrust (Game mode): Rust survival, in its standard form; mp100 (Max players): It offers 100 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod), which [JP/Tokyo] Solo/Duo/Trio publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.10Where can [JP/Tokyo] Solo/Duo/Trio be found among the Rust Statistics lists and filters?

These Rust Statistics lists include [JP/Tokyo] Solo/Duo/Trio: Rust community servers, measured. You will find it on the server list filtered by: 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.

Rules, settings, map

A.11Under what rules and settings does [JP/Tokyo] Solo/Duo/Trio operate?

The name of [JP/Tokyo] Solo/Duo/Trio states no gather rate. At 8 players, the group limit equals the game's default. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. The server browser lists it under Community. Plugins number Oxide on this server. VAC, Valve's anti-cheat, is enabled.

A.12On which map does [JP/Tokyo] Solo/Duo/Trio take place?

The game generates [JP/Tokyo] Solo/Duo/Trio's procedural map at size 3,500, from seed 17761776. Because size and seed determine the map, RustMaps can show it, linked from this page.

How to join

A.13What steps are required to join [JP/Tokyo] Solo/Duo/Trio?

Enter client.connect 160.251.250.21:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you. Its website can be found at https://discord.com/invite/QjJSb4U6T.

Appendix BServer tags

What each of the server's tags means. Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp100Max players. It offers 100 slots.
ts8Group limit. 8 per team, the value the game sets by default.
v2635Protocol. The game protocol is 2635; your client must match it to join.
cs168909Build. Build 168909 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. No region code is set.
Mods and access
^oOxide. The plugin framework in use is 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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.