Station NA-15986 · no signal
Tokyo| US | 2x |
Offline NA 66.51.98.74:28000 checked 25d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,986
- top 71% · #1567 in NA
- Last wipe
- 46d ago
- monthly schedule
- Next wipe
- 7d 6h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M –not enough readings
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
daily · 1 is bestTop 71% of all ranked servers, top 85% in NA. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h. The force wipe
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 Tokyo| US | 2x |?
The procedural map on Tokyo| US | 2x | is size 1,500 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. Its map carries the name Custom Map.
Which settings and rules apply on Tokyo| US | 2x |?
2x gather is what Tokyo| US | 2x | runs, judging by its name. 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. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Player counts
What is the current population on Tokyo| US | 2x |?
No players are recorded on Tokyo| US | 2x | at this moment; it is offline, and the last sighting was 25 days 8 hours ago.
How does Tokyo| US | 2x | rank against other Rust servers?
Tokyo| US | 2x | is #1,567 in North America and #15,986 worldwide on the past week's player hours, within the top 71% of ranked servers.
Server facts
How reliably does Tokyo| US | 2x | stay online?
No contact with Tokyo| US | 2x | right now, and the last recorded contact was 25 days 8 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Which region does Tokyo| US | 2x | run from?
With its NA tag, Tokyo| US | 2x | lists itself in North America. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 66.51.98.74:28000.
Which Rust version is Tokyo| US | 2x | running?
Tokyo| US | 2x | is running Rust network protocol 2633 and build 163794 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
On what timetable does Tokyo| US | 2x | run its wipes?
An estimate from the force wipe gives Tokyo| US | 2x |'s next wipe. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. The present world dates from 46 days 17 hours. The tags it publishes carry a monthly wipe schedule.
Lists and tags
What do the server tags on Tokyo| US | 2x | mean?
Tags published by Tokyo| US | 2x | and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp50 (Max players): The server has 50 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs163794 (Build): The game build is 163794; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; NA (North America): In the server browser it appears under North America. 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 Tokyo| US | 2x | appear?
You will find Tokyo| US | 2x | on the following Rust Server Trends lists: 2x Rust servers, listed live, Modded Rust servers, tracked live and North America Rust servers. You will find it under these filters on the server list: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
Connecting
What steps get you onto Tokyo| US | 2x |?
You can connect by pressing F1 in Rust and typing client.connect 66.51.98.74:28000 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
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.