Station XX-417 · recording
Japan Tokyo - Limited Raid Hours |3x|PvP|JP
Online 162.222.17.4:30040 checked 8m ago
- Players now
- 18/ 300
- 6% full
- Motion · 24 h
- M0.6▼falling
- −4 players on the day
- 7-day average
- 38
- peak 171
- Rank
- #417
- top 2%
- Last wipe
- 4d ago
- weekly schedule
- Next wipe
- 2d 14h
- Fri 30 Oct, 08:31 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 18of 300 slots
- Motion · 24 h
- M0.6▼falling−4 players
- Sharpest hour
- −26into Mon 15:00 UTC
- Peak · 48 h
- 96most players in any hour
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 22 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 2% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Friday 30 October, 08:31 UTC, in 2d 14h. Every Friday at 08:31 UTC · high confidence
- usual gap
- 7 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 142players, last three wipes
- crowd held
- 0%else halves by day 4
Coming wipes
- 2d 14hFri 30 Oct, 08:31 UTC
- 9d 0hThu 5 Nov, 19:00 UTCFW
- 9d 14hFri 6 Nov, 08:31 UTC
- 16d 14hFri 13 Nov, 08:31 UTC
- 23d 14hFri 20 Nov, 08:31 UTC
- 30d 14hFri 27 Nov, 08:31 UTC
- 37d 0hThu 3 Dec, 19:00 UTCFW
- 37d 14hFri 4 Dec, 08:31 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 171, 4 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 23 Oct, 08:31 UTC4d ago | M2.2▲rising | 171 | – | running | 4 | |
| Fri 16 Oct, 08:31 UTC11d ago | M2.1▲rising | 129+39 queue | halved by day 5 | 7 days | 3 | |
| Fri 9 Oct, 08:31 UTC18d ago | M2.1▲rising | 125 | halved by day 4 | 7 days | 0 | |
| Fri 2 Oct, 08:31 UTC25d ago | M2.2▲rising | 153+68 queue | halved by day 3 | 7 days | 0 | |
| Fri 25 Sep, 08:31 UTC32d ago | M2.1▲rising | 133+3 queue | halved by day 4 | 7 days | 0 | |
| Fri 18 Sep, 08:31 UTC39d ago | M2.2▲rising | 181 | halved by day 6 | 7 days | 4 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?
The procedural map on Japan Tokyo - Limited Raid Hours |3x|PvP|JP is size 3,800 with seed 1337, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. The name of its map is Custom Map.
Which settings and rules apply on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?
Going by its name, Japan Tokyo - Limited Raid Hours |3x|PvP|JP runs 3x gather. Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Carbon is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on Japan Tokyo - Limited Raid Hours |3x|PvP|JP right now?
At this moment, Japan Tokyo - Limited Raid Hours |3x|PvP|JP records 18 players across 300 slots. The seven-day average is 38 players, with a peak of 171. The busiest point in the last 48 hours came at 14:00 UTC, averaging 92 players.
How does Japan Tokyo - Limited Raid Hours |3x|PvP|JP rank against other Rust servers?
Over the last seven days, Japan Tokyo - Limited Raid Hours |3x|PvP|JP recorded enough player hours to reach #417 worldwide, placing it in the top 2% of all ranked servers.
Operator and location
How reliably does Japan Tokyo - Limited Raid Hours |3x|PvP|JP stay online?
As recorded now, Japan Tokyo - Limited Raid Hours |3x|PvP|JP is running. Its reported uptime points to a restart about 19 hours ago. Of the 168 hours in the last 7 full days, it was up for 168, or 100% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Does Japan Tokyo - Limited Raid Hours |3x|PvP|JP hold a steady tick rate?
The 48-hour average is 30 server fps; 30 is the lowest observed. Buildings, deployables and all the rest of the world's entities brought it to a high of 187,722. Memory use peaked at 5,366 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does Japan Tokyo - Limited Raid Hours |3x|PvP|JP run from?
No region tag comes from Japan Tokyo - Limited Raid Hours |3x|PvP|JP, though the name points to Asia. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 162.222.17.4:30040.
What build of Rust does Japan Tokyo - Limited Raid Hours |3x|PvP|JP use?
Rust network protocol 2635 and build 168909 on Linux is what Japan Tokyo - Limited Raid Hours |3x|PvP|JP runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on Japan Tokyo - Limited Raid Hours |3x|PvP|JP?
142 players, on average, was the busiest crowd at its recent wipes. 4 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. By day 4 it fell below half in the wipes where it didn't hold.
On what timetable does Japan Tokyo - Limited Raid Hours |3x|PvP|JP run its wipes?
At Japan Tokyo - Limited Raid Hours |3x|PvP|JP the wipes follow a every Friday at 08:31 UTC rhythm. The date of its next wipe is Friday 30 October at 08:31 UTC. The present world dates from 4 days 9 hours. A weekly wipe schedule is published in its tags.
Server tags
What do the server tags on Japan Tokyo - Limited Raid Hours |3x|PvP|JP mean?
These are the tags Japan Tokyo - Limited Raid Hours |3x|PvP|JP publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp300 (Max players): Slots: 300; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^w (Weekly): Wipes happen weekly; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Japan Tokyo - Limited Raid Hours |3x|PvP|JP appear?
The Rust Server Trends lists that take in Japan Tokyo - Limited Raid Hours |3x|PvP|JP are: 3x Rust servers, by live population and Modded Rust servers, tracked live. On the server list, the filters it matches are: 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.
Connecting
What steps get you onto Japan Tokyo - Limited Raid Hours |3x|PvP|JP?
You can connect by pressing F1 in Rust and typing client.connect 162.222.17.4:30040 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. For the website, go to https://discord.com/invite/AH7FXJ2Xet.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.