DWG RG-S1563Server sheetchecked 13m ago
[JP/Tokyo] Solo/Duo/Trio
Online 160.251.250.21:28015 checked 13m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
Top 7% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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.
Wipes
| 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 |
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.
Similar servers
Quick answers
Server data
How reliable is [JP/Tokyo] Solo/Duo/Trio, and is it online now?
[JP/Tokyo] Solo/Duo/Trio is up at this moment. The uptime it reports puts the last restart at about 5 days 22 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. First seen by Rust Graphs on 13 September 2026.
How does [JP/Tokyo] Solo/Duo/Trio perform, as measured?
73 server fps on average over the last 48 hours, and never under 53. Counted at its highest: 78,837 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 4,282 MB. What players feel as lag is low fps together with a climbing entity count.
In which location is [JP/Tokyo] Solo/Duo/Trio hosted?
Its name points to Asia, though [JP/Tokyo] Solo/Duo/Trio publishes no region tag. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 160.251.250.21:28015 is its address.
What Rust version is recorded for [JP/Tokyo] Solo/Duo/Trio?
Rust network protocol 2635 and build 168909 on Linux: that is what [JP/Tokyo] Solo/Duo/Trio runs. The same protocol is required for joining, and Steam updates your game to it.
Counts
What player count is recorded on [JP/Tokyo] Solo/Duo/Trio?
At the last refresh, [JP/Tokyo] Solo/Duo/Trio recorded 2 players across 100 slots. The seven-day mean is 4 players; the peak over the same period is 11. The 48-hour peak falls at 15:00 UTC, averaging 9 players.
What rank has been recorded for [JP/Tokyo] Solo/Duo/Trio?
Player hours over seven days place [JP/Tokyo] Solo/Duo/Trio at #1,563, within the top 7% of ranked servers.
Wipe times
On [JP/Tokyo] Solo/Duo/Trio, what does the data show for wipe day?
The recent wipes averaged a busiest count of 5 players. 32 hours after the latest wipe, the crowd peaked. The crowd stayed above half the peak until the next wipe in 100% of its recent wipes.
Which times and days are wipes plotted at on [JP/Tokyo] Solo/Duo/Trio?
No next wipe can be predicted for [JP/Tokyo] Solo/Duo/Trio: its wipes fall at irregular times. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. The world it runs now was made 6 days 13 hours ago.
Rules and settings
Which settings does [JP/Tokyo] Solo/Duo/Trio run, and what rules?
The name of [JP/Tokyo] Solo/Duo/Trio records no gather rate. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. Community is its tab in the server browser. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.
Which map has [JP/Tokyo] Solo/Duo/Trio loaded?
Seed 17761776 and size 3,500 define the procedural map [JP/Tokyo] Solo/Duo/Trio generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Lists and filters
Where does [JP/Tokyo] Solo/Duo/Trio appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry [JP/Tokyo] Solo/Duo/Trio are: Rust community servers, plotted. It is returned by these filters 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 meaning is attached to each tag on [JP/Tokyo] Solo/Duo/Trio?
The game's server browser reads these tags from [JP/Tokyo] Solo/Duo/Trio: gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): 100 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^o (Oxide): The plugin framework is Oxide (uMod). Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
How to join
How is [JP/Tokyo] Solo/Duo/Trio joined?
In Rust, press F1 and type client.connect 160.251.250.21:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. You will find its website at https://discord.com/invite/QjJSb4U6T.
Server tags
Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o
Game
gmrust
mp100
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^o
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.