TNK Rust Server in Japan
Offline EA 133.88.120.172:28015 checked 19d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 72% of all ranked servers, top 94% in EA. 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 1, 1 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 9 Oct, 09:48 UTC20d ago | 1 | – | running | 0 |
| Thu 1 Oct, 22:52 UTC FW27d ago | 2 | held half | 7.5 days | 0 |
| Tue 29 Sep, 14:36 UTC30d ago | 3 | held half | 2.3 days | 0 |
| Tue 29 Sep, 07:22 UTC30d ago | 2 | – | 0.3 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| Server | Profile | Players now |
|---|---|---|
| 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 26 / 200 |
| QS『鱼山路』pve｜耐玩｜升级｜突袭 | EA · groups of 8+ · 37 on average | 33 / 100 |
| [坚果PVE]宗门师徒/每日打榜/合成强化/打金赚钱 | EA · groups of 8+ · monthly · 34 on average | 26 / 100 |
| Japan Tokyo - Vanilla PvE|JP|Beginner | EA · groups of 16+ · 33 on average | 11 / 100 |
| Japan Tokyo - Chill PvE|JP | EA · groups of 16+ · 21 on average | 7 / 100 |
| 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 20 on average | 15 / 88 |
Quick answers
from the figures on this pageWipe cycle
When does TNK Rust Server in Japan wipe?
No next wipe can be predicted for TNK Rust Server in Japan, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. 20 days 11 hours ago the current world was made.
Wipe day on TNK Rust Server in Japan: what should you expect?
Across recent wipes the busiest point averaged 2 players. The highest player count on the latest wipe arrived 1 hours in. Recent wipes held the crowd above half that peak until the next wipe in 100% of cases.
Server
In which region does TNK Rust Server in Japan sit?
Its EA tag puts TNK Rust Server in Japan in Asia. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 133.88.120.172:28015 is its address.
Which Rust version is TNK Rust Server in Japan on?
On Linux, TNK Rust Server in Japan runs Rust network protocol 2634 and build 166494. The protocol has to match before you can join; Steam updates it automatically.
How reliable is TNK Rust Server in Japan, and is it online now?
The current status is offline for TNK Rust Server in Japan, with the last sighting 19 days 18 hours ago. 0% uptime over the last 7 full days, equal to 0 of 168 hours. The first sighting of it by Rust Server Analytics was on 28 September 2026.
Tags
How should the tags on TNK Rust Server in Japan be read?
The game's server browser reads the tags TNK Rust Server in Japan publishes: gmrust (Game mode): Rust survival, standard ruleset; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: 8 per team at most; v2634 (Protocol): To join, your game version must match protocol 2634; cs166494 (Build): Game build: 166494; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): The region code is blank; ^v (Vanilla): Nothing altered from Facepunch's release: rates, kits and rules are stock; ^p (PvE): No fighting between players, with the world as the threat; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): Plugins or settings change the game, so it sits under Modded; EA (East Asia): The server browser files it under East Asia. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
Where does TNK Rust Server in Japan appear across Rust Server Analytics's lists and filters?
These Rust Server Analytics lists include TNK Rust Server in Japan: Modded Rust servers: live data and PvE Rust servers by live population. It appears on the server list under the following filters: Region: Asia; Type: Vanilla and Modded; Game mode: PvE; Server tag: Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What position does TNK Rust Server in Japan hold in the server rankings?
Ranked on seven-day player hours, TNK Rust Server in Japan is #15,816 overall and #495 in Asia, within the top 72% of ranked servers.
What is the population of TNK Rust Server in Japan?
TNK Rust Server in Japan is offline at this refresh; the last contact was 19 days 18 hours ago.
Map and rules
How is TNK Rust Server in Japan configured, and what rules apply?
Gather rate is not mentioned in the name of TNK Rust Server in Japan. The game's default 8-player group limit is in force. It runs pve, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. The plugin framework is Oxide. Its self-description is vanilla: nothing altered from Facepunch's release: rates, kits and rules are stock. VAC, Valve's anti-cheat, is enabled.
The map on TNK Rust Server in Japan: which one is it?
A procedural map of size 4,000 with seed 6543210, generated by the game, runs on TNK Rust Server in Japan. Because size and seed determine the map, it can be viewed on RustMaps via this page.
How to join
How can a player join TNK Rust Server in Japan?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 133.88.120.172:28015.