Statistical profileOnline
[JP/Tokyo] Solo/Duo/Trio
160.251.250.21:28015 checked 14m ago
Connect to this server
1. Main points
Players now
3/ 100
3% full
7-day average
4
peak 11
Rank
#1,565
top 7%
Last wipe
6d ago
no schedule published
Next wipe
–
no rhythm it keeps
Main points
- There were 3 players on it, 3% of its 100 slots.
- Over the last seven days it averaged 4 players, with a peak of 11.
- It ranks #1,565 of all ranked servers, the top 7%, on player hours over the last seven days.
- Its current map went up 6d ago.
2. Players
Figure 1: Players on [JP/Tokyo] Solo/Duo/Trio
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 7% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternno 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 days
between real wipes
On rhythm
0%
of its recent wipes
Wipe-day peak
5
players, last three wipes
Crowd held
100%
of its cycles kept half the crowd
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 8, 32 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players 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 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of [JP/Tokyo] Solo/Duo/Trio
3500 · seed 17761776
![Map of [JP/Tokyo] Solo/Duo/Trio](https://files.facepunch.com/rust/map-images/faaaa8c0f6ac4bfa60216af0089efaa19a7d7ddc530740d49077af1afb7e1e0e/proceduralmap.3500.1792742526773.289_faaaa8c0f6ac4bfa60216af0089efaa1.jpg)
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | 3500 |
| Seed | 17761776 |
8. Server characteristics
Table 3: Characteristics of [JP/Tokyo] Solo/Duo/Trio
What the server publishes and what was recorded
| Address | 160.251.250.21:28015 |
|---|---|
| Region | – |
| Max players | 100 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 23 Oct 2026, 08:02 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| Rustoria.co - SEA Main | EA · groups of 16+ · weekly · 181 on average | 133 / 200 |
| Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com | EA · groups of 16+ · weekly · 119 on average | 0 / 550 |
| Rustoria.co - SEA Long | EA · groups of 12+ · monthly · 100 on average | 28 / 200 |
| Rustafied.com - SEA Main | EA · groups of 16+ · weekly · 79 on average | 39 / 100 |
| Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] | EA · groups of 8+ · weekly · 54 on average | 1 / 200 |
| [ASIA] Siam Rust | Vanilla | Weekly | EA · groups of 8+ · weekly · 38 on average | 23 / 150 |
10. Quick answers
From the figures on this page.
Wipe schedule
On what schedule are wipes carried out on [JP/Tokyo] Solo/Duo/Trio?
No next wipe can be predicted for [JP/Tokyo] Solo/Duo/Trio, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The present world dates from 6 days 16 hours.
On [JP/Tokyo] Solo/Duo/Trio, what happens on wipe day?
An average of 5 players attended at peak across recent wipes. 32 hours after the latest wipe, the crowd peaked. Recent wipes kept the crowd above half the peak until the next wipe in 100% of cases.
Server details
What does the record show for the uptime and current status of [JP/Tokyo] Solo/Duo/Trio?
At the latest check, [JP/Tokyo] Solo/Duo/Trio was online. By its own reported uptime, it restarted about 6 days 1 hours ago. 143 of 168 hours on across the last 7 full days gives an uptime of 85%. The first sighting of it by Rust Census was on 13 September 2026.
What does the performance record of [JP/Tokyo] Solo/Duo/Trio show?
Over the last 48 hours, server fps averaged 71; the lowest reading was 50. The world carried up to 78,837 entities, including buildings, deployables and all else. Memory use reached 4,282 MB at its peak. What players experience as lag is low fps combined with a climbing entity count.
What location has been recorded for [JP/Tokyo] Solo/Duo/Trio?
Its name points to Asia, though [JP/Tokyo] Solo/Duo/Trio publishes no region tag. Rust Census does not look up where the machine stands; it shows where a server says it is. 160.251.250.21:28015 is its address.
Which Rust version is [JP/Tokyo] Solo/Duo/Trio running?
Rust network protocol 2635 and build 168909 on Linux is the version [JP/Tokyo] Solo/Duo/Trio runs. The same protocol is required for your game to join, and Steam updates it for you.
Population
What population has been recorded on [JP/Tokyo] Solo/Duo/Trio?
[JP/Tokyo] Solo/Duo/Trio stands at 3 players from 100 slots in this release. Averaged over seven days: 4 players, with a peak of 11. Over the past 48 hours the highest average fell at 15:00 UTC: 9 players.
What position does [JP/Tokyo] Solo/Duo/Trio hold in the server rankings?
The rank for [JP/Tokyo] Solo/Duo/Trio is #1,565 on seven-day player hours, in the top 7% of ranked servers.
Tag details
On Rust Census, which lists and filters carry [JP/Tokyo] Solo/Duo/Trio?
These Rust Census lists include [JP/Tokyo] Solo/Duo/Trio: Community servers. Under these filters it comes 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.
Which meanings do the tags on [JP/Tokyo] Solo/Duo/Trio carry?
gmrust (Game mode): Survival play, in the standard Rust format; mp100 (Max players): Slots: 100; ts8 (Group limit): This is the game default: 8 to a team; v2635 (Protocol): Protocol 2635 is required; a different version cannot join; cs168909 (Build): Build 168909 is installed; ptrak (Networking): Networking is handled by RakNet, which the game uses by default; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod) are the tags [JP/Tokyo] Solo/Duo/Trio publishes, and the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Map and rules
Which map has been recorded for [JP/Tokyo] Solo/Duo/Trio?
The procedural map on [JP/Tokyo] Solo/Duo/Trio is generated by the game, measures 3,500 and carries seed 17761776. The same size and seed produce the same map; RustMaps shows it from this page.
How is [JP/Tokyo] Solo/Duo/Trio configured, and what rules does it keep?
The name of [JP/Tokyo] Solo/Duo/Trio carries no gather rate. 8 players is the group limit, the game's default. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. It appears under Community in the server browser. Oxide plugins are recorded on it. VAC, Valve's anti-cheat, is enabled.
Join details
What is the way to join [JP/Tokyo] Solo/Duo/Trio?
Enter client.connect 160.251.250.21:28015 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you. This release lists its website as https://discord.com/invite/QjJSb4U6T.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp100 | Max players Slots: 100. |
ts8 | Group limit This is the game default: 8 to a team. |
v2635 | Protocol Protocol 2635 is required; a different version cannot join. |
cs168909 | Build Build 168909 is installed. |
ptrak | Networking Networking is handled by RakNet, which the game uses by default. |
$r? | Region code No region code is set. |
Mods and access
^o | Oxide 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.