Offline NA 66.51.98.74:28000 checked 25d ago
Tokyo| US | 2x |
Connect
srv = rust.server("66.51.98.74:28001")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 71% of all ranked servers, top 85% in NA. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 0h. # The force wipe
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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.
display(srv.map, srv.info())Map
1500 · seed 1337
- map
- Custom Map
- size
- 1500
- seed
- 1337
Server
srv.info()- address
- 66.51.98.74:28000
- region
- NA
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 12 Sep 2026, 19:13 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Atlas - US 2X Monthly | Vanilla+ | No BP Wipes | NA · groups of 16+ · 2x · monthly · 379 on average | 154/200 |
| 1 | US Limitless 2x Monthly Main | No BP Wipes | x2 | NA · groups of 12+ · 2x · monthly · 157 on average | 87/200 |
| 2 | US Limitless 2x Monthly No Offlines|No BP Wipes|Noob Friendly | NA · groups of 12+ · 2x · monthly · 8 on average | 5/200 |
| 3 | [US] Spoonkid Rust - 2x Monthly | 8 MAX | No BP Wipes | NA · groups of 8+ · 2x · monthly · 8 on average | 7/67 |
| 4 | Exile.gg | US 2x Monthly | 12 Max | NA · groups of 12+ · 2x · monthly · 6 on average | 1/50 |
| 5 | [US] Ember Rust 2x Monthly | SOLO ONLY | No BP Wipes | NA · groups of 8+ · 2x · monthly · 5 on average | 1/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Tokyo| US | 2x | rank?
On seven-day player hours Tokyo| US | 2x | is #15,986 overall and #1,567 in North America, inside the top 71% of all ranked servers.
What population does Tokyo| US | 2x | carry?
Tokyo| US | 2x | returns no live count at this refresh, having last been seen 25 days 14 hours ago.
Server facts
Which Rust version is Tokyo| US | 2x | on?
Rust network protocol 2633 and build 163794 on Linux is what Tokyo| US | 2x | runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Tokyo| US | 2x |, and is it online now?
The latest sample has Tokyo| US | 2x | offline, with a last sighting 25 days 14 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does Tokyo| US | 2x | sit?
With its NA tag, Tokyo| US | 2x | lists itself in North America. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 66.51.98.74:28000.
Settings and map
Which settings and rules does Tokyo| US | 2x | run?
Gather sits at 2x, read from the server's own name: Tokyo| US | 2x |. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on Tokyo| US | 2x |?
Size 1,500, seed 1337: the procedural map on Tokyo| US | 2x |, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Under map name you will find: Custom Map.
Wipe data
When does Tokyo| US | 2x | wipe, and how often?
The next wipe for Tokyo| US | 2x | is an estimate, drawn from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 46 days 22 hours ago, and that is the one in play. A monthly wipe schedule is published in its tags.
Tags and filters
Which lists on Rust Data hold Tokyo| US | 2x |, and which filters?
On Rust Data, Tokyo| US | 2x | appears in these lists: Modded Rust servers, 2x Rust servers and North America Rust servers. It appears 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.
Which meanings do the tags on Tokyo| US | 2x | hold?
The game's server browser reads these tags from Tokyo| US | 2x |: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163794 (Build): Recorded game build: 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): In the server browser it sits under North America. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into Tokyo| US | 2x |?
Enter client.connect 66.51.98.74:28000 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.