[JP/Tokyo] Solo/Duo/Trio
Online 160.251.250.21:28015 checked 12m ago
Server instruments
last reading Thu 20:00 UTCPlayers now
2% full 7-day avg7-day peakServer fps
48 h low 53 · below 20 is lag, below 10 is badEntities
48 h range 74,898–78,837 · memory 3,817 MBUptime
5 days 22 hours since its last restart, at the last readingPlayers
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
daily · 1 is bestTop 7% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts 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
newest first| 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
the same kind of game, then region, group limit, rate and wipes- 199/250
- 1/550
- 42/200
- 94/150
- 0/200
- 44/150
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on [JP/Tokyo] Solo/Duo/Trio?
An average of 5 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 32 hours in. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.
When does [JP/Tokyo] Solo/Duo/Trio wipe?
There is no next wipe to predict: [JP/Tokyo] Solo/Duo/Trio wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 6 days 13 hours ago.
Tags
How should you read the tags on [JP/Tokyo] Solo/Duo/Trio?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod from [JP/Tokyo] Solo/Duo/Trio. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does [JP/Tokyo] Solo/Duo/Trio appear in Rust Metrics lists and filters?
These Rust Metrics lists carry [JP/Tokyo] Solo/Duo/Trio: Rust community servers: live readings. 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.
Player count
Where does [JP/Tokyo] Solo/Duo/Trio sit in the rankings?
Player hours over seven days put [JP/Tokyo] Solo/Duo/Trio at #1,563, in the top 7% of all ranked servers.
How full does [JP/Tokyo] Solo/Duo/Trio get?
Current headcount on [JP/Tokyo] Solo/Duo/Trio: 2 players, 100 slots available. Seven-day check: 4 players on average. Peak reading: 11. The last 48 hours peaked at 15:00 UTC, averaging 9 players at that hour.
Operator and location
What location is [JP/Tokyo] Solo/Duo/Trio hosted in?
The name of [JP/Tokyo] Solo/Duo/Trio points to Asia, though it publishes no region tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 160.251.250.21:28015.
What Rust version is [JP/Tokyo] Solo/Duo/Trio on?
Reading: [JP/Tokyo] Solo/Duo/Trio, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.
What is the performance reading for [JP/Tokyo] Solo/Duo/Trio?
Check: fps. Average 73 server fps over the last 48 hours, low of 53. Within range. Reading: 78,837 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,282 MB. What players call lag comes from low fps and an entity count on the rise.
How reliable is [JP/Tokyo] Solo/Duo/Trio, and is it online now?
Check: connection. [JP/Tokyo] Solo/Duo/Trio is online at this moment. Check: restart. The uptime it reports puts the last restart about 5 days 22 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What rules does [JP/Tokyo] Solo/Duo/Trio enforce, and what are its settings?
No gather rate appears in the name: [JP/Tokyo] Solo/Duo/Trio. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
Which map is live on [JP/Tokyo] Solo/Duo/Trio?
From seed 17761776, the game generates the procedural map on [JP/Tokyo] Solo/Duo/Trio. Its size is 3,500. View it on RustMaps from this page: matching size and seed give an identical map.
Join
What do you do to join [JP/Tokyo] Solo/Duo/Trio?
To join: start Rust, press F1 and type client.connect 160.251.250.21:28015. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://discord.com/invite/QjJSb4U6T.