Japan Tokyo - Limited Raid Hours |3x|PvP|JP
Key statistics
the figures behind the quote- Players now
- 43/ 300 14% full
- Change · 24h
- ▼−11 −19.8% from 54
- 7-day average
- 31 peak 125
- Rank
- #594 top 3%
- Rank · 7d ago
- #647 ▲53 places up
- Last wipe
- 5d ago weekly schedule
- Next wipe
- 1d 19h Fri 16 Oct, 08:31 UTC
- Group limit
- 8 8, the default
- Gather rate
- 3x read from the name
- Score
- 5,218 player hours, last seven days
- Map
- 3800 Custom Map · seed 1337
- First seen
- 13 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 71 players.
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 22 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 3% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdays- usual gap
- 7 days between real wipes
- on rhythm
- 100% of its recent wipes
- wipe-day peak
- 137 players, last three wipes
- crowd held
- 0% else halves by day 4
Coming wipes
- 1d 19hFri 16 Oct, 08:31 UTC
- 8d 19hFri 23 Oct, 08:31 UTC
- 15d 19hFri 30 Oct, 08:31 UTC
- 22d 6hThu 5 Nov, 19:00 UTCFW
- 22d 19hFri 6 Nov, 08:31 UTC
- 29d 19hFri 13 Nov, 08:31 UTC
- 36d 19hFri 20 Nov, 08:31 UTC
- 43d 19hFri 27 Nov, 08:31 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 125, 4 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 9 Oct, 08:31 UTC5d ago | 125 | – | running | 0 |
| Fri 2 Oct, 08:31 UTC12d ago | 153+68 queue | halved by day 3 | 7 days | 0 |
| Fri 25 Sep, 08:31 UTC19d ago | 133+3 queue | halved by day 4 | 7 days | 0 |
| Fri 18 Sep, 08:31 UTC26d ago | 181 | halved by day 6 | 7 days | 4 |
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 | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | [SEA] CHICKEN 3x | Max 8 | Low Ping | TH | Wipe 10/05EA · groups of 8+ · 3x · weekly · 31 on average | 51/300 | ▼−42−45.4% | |
| 2 | SIX-SEVEN 67 | Max 8 | SEA | Kits | Shop | 3X | Wiped 10/10EA · groups of 8+ · 3x · weekly · 1 on average | 0/150 | ▪+0 | |
| 3 | Jumprust.com - RustyIron 3x|JP/SEA|Full PVP|Shop|Kits|LongEA · groups of 100+ · 3x · monthly · 13 on average | 30/120 | ▲+7+30.9% | |
| 4 | VandalRust|JP/KR/SEA|2X|Raid Hours|初心者歓迎|金曜日EA · groups of 8+ · 2x · weekly · 4 on average | 5/100 | ▲+5 | |
| 5 | HQM.GG SEA 3x Monthly Solo Only - Skins - Pvp - ORPEA · groups of 8+ · 3x · monthly · 3 on average | 8/75 | ▲+1+14.3% | |
| 6 | 초보/농사/힐링 [ 놀자컴퍼니서버 ] PVE/24H/X3EA · groups of 8+ · 3x · 3 on average | 3/50 | ▼−3−50.0% |
Quick answers
from the figures on this pageMap and Rules
How is Japan Tokyo - Limited Raid Hours |3x|PvP|JP configured in terms of rules and settings?
A gather rate of 3x appears in the name of Japan Tokyo - Limited Raid Hours |3x|PvP|JP. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. You can fight and raid other players. The server browser lists it as Modded: plugins or settings change the game. Carbon plugins are running. VAC, Valve's anti-cheat, is enabled.
What is the current map on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?
Japan Tokyo - Limited Raid Hours |3x|PvP|JP uses a procedural map of size 3,800 with seed 1337, generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page. The map in use is Custom Map.
Activity
What position does Japan Tokyo - Limited Raid Hours |3x|PvP|JP hold in the server rankings?
In the top 3% of all ranked servers, Japan Tokyo - Limited Raid Hours |3x|PvP|JP is #594 on player hours over the last seven days.
How many players does Japan Tokyo - Limited Raid Hours |3x|PvP|JP have?
43 of 300 slots on Japan Tokyo - Limited Raid Hours |3x|PvP|JP are filled right now. Average players over seven days: 31; peak: 125. At 13:00 UTC in the last 48 hours, it averaged 67 players, the busiest hour.
Wipe Cycle
How does Japan Tokyo - Limited Raid Hours |3x|PvP|JP handle wipe day?
Recent wipes at this server drew an average peak of 137 players. On the latest wipe, 4 hours after the wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The crowd fell below half by day 4 when it did not hold.
When does Japan Tokyo - Limited Raid Hours |3x|PvP|JP schedule its wipes?
The wipe rhythm at Japan Tokyo - Limited Raid Hours |3x|PvP|JP is every Friday at 08:31 UTC. On Friday 16 October at 08:31 UTC the next wipe is due. Its world now is 5 days 4 hours old. Weekly wipes are what its tags advertise.
Server Info
Where can Japan Tokyo - Limited Raid Hours |3x|PvP|JP be found?
Its name points to Asia, but Japan Tokyo - Limited Raid Hours |3x|PvP|JP publishes no region tag. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 162.222.17.4:30040.
Is Japan Tokyo - Limited Raid Hours |3x|PvP|JP performing well?
The last 48 hours average 30 server fps, the low being 30. The entity count reached 180,692, covering buildings, deployables and all else in the world. Up to 5,241 MB of memory was used. What players feel as lag is low fps together with a rising entity count.
What Rust version is Japan Tokyo - Limited Raid Hours |3x|PvP|JP running?
The version in use at Japan Tokyo - Limited Raid Hours |3x|PvP|JP: Rust network protocol 2634 and build 167781, on Linux. Your game needs the same protocol to get in; Steam takes care of the update.
Is Japan Tokyo - Limited Raid Hours |3x|PvP|JP up, and how consistent is its uptime?
Online at this moment: Japan Tokyo - Limited Raid Hours |3x|PvP|JP. The reported uptime puts its last restart at about 14 hours ago. 7 full days have passed with 100% uptime, 168 of 168 hours. 13 September 2026 is when Rust Analytics first saw it.
Tags and Rankings
What is the meaning of the tags on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?
Published by Japan Tokyo - Limited Raid Hours |3x|PvP|JP for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust format; mp300 (Max players): Slot count: 300; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167781 (Build): Game build: 167781; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set; ^w (Weekly): Wipes land every week; ^z (Modded): The Modded listing applies: plugins or settings change play; ^y (Carbon): The plugin framework here is Carbon. Also in the tags and at the top of this page: current players, queue and world creation time.
Japan Tokyo - Limited Raid Hours |3x|PvP|JP appears in which of the lists and filters on Rust Analytics?
The following Rust Analytics lists feature Japan Tokyo - Limited Raid Hours |3x|PvP|JP: 3x Rust servers and Modded Rust servers. It appears under these filters on the server list: Region: Asia; Type: Modded; Server tag: Weekly ^w, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 3x; Players now: At least 10; Average players: 25+ on average.
Connection
What steps do I take to join Japan Tokyo - Limited Raid Hours |3x|PvP|JP?
The console route: start Rust, press F1, enter client.connect 162.222.17.4:30040. The page's Launch Rust button opens Rust through Steam and connects you instead. You can reach its website at https://discord.com/invite/AH7FXJ2Xet.
Server tags
what each one meansPublished as mp300,ptrak,$r?,v2634,^z,^y,^w,gmrust,cs167781,ts8
Game
gmrust
mp300
ts8
v2634
cs167781
ptrak
$r?
Wipe schedule
^w
Mods and access
^z
^y
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.