Offline EA 202.70.47.214:28015 checked 45d ago
Mongolia Ulaanbaatar | 2X Vanilla
Connect
srv = rust.server("202.70.47.214:28017")
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. 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 bestWipe schedule
srv.wipe_schedule()Next wipe Friday 30 October, 23:16 UTC, in 1d 16h. # Weekly: 7 days after its last 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 202.70.47.214:28015
- region
- EA
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- weekly
- last wipe
- 4 Sep 2026, 23:16 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 | |TW-JP-SEA|Rustyafied 2X Vanilla|MAP WIPE 10/23 | EA · groups of 12+ · 2x · weekly · 2 on average | 1/200 |
| 1 | [KR/EN/JP/CN] 한국서버 | 2x Resources|WIPE 10.23 | EA · groups of 8+ · 2x · weekly · 4 on average | 0/100 |
| 2 | [SEA] AseanPanda.net | 2x Vanilla | MAP WIPE 3 | 27/10 | EA · groups of 8+ · 2x · biweekly · 82 on average | 52/115 |
| 3 | Japan Tokyo - Limited Raid Hours |3x|PvP|JP | EA · groups of 8+ · 3x · weekly · 40 on average | 9/300 |
| 4 | QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造 | EA · groups of 20+ · weekly · 24 on average | 31/100 |
| 5 | [SEA] Rust Manila 2x | Biweekly | EA · groups of 8+ · 2x · biweekly · 24 on average | 38/150 |
Quick answers
From the figures on this page.
Population data
How full does Mongolia Ulaanbaatar | 2X Vanilla run?
Offline now for Mongolia Ulaanbaatar | 2X Vanilla, with the last sample 45 days 17 hours ago.
Server facts
What Rust version does Mongolia Ulaanbaatar | 2X Vanilla run?
The build is Rust network protocol 2633 and build 163207 on Linux, run by Mongolia Ulaanbaatar | 2X Vanilla. Steam updates your game for you, but the protocol must match to join.
How reliable is Mongolia Ulaanbaatar | 2X Vanilla, and is it up?
Offline now for Mongolia Ulaanbaatar | 2X Vanilla, last seen 45 days 17 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 13 September 2026.
Which location does Mongolia Ulaanbaatar | 2X Vanilla run from?
The EA tag is what Mongolia Ulaanbaatar | 2X Vanilla uses to list itself in Asia. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 202.70.47.214:28015 is its address.
Map and rules
What rules and settings are recorded for Mongolia Ulaanbaatar | 2X Vanilla?
2x gather is what the name states, and the name is Mongolia Ulaanbaatar | 2X Vanilla. 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. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Vanilla, by its own description: no changed rates, kits or rules: the game as Facepunch ships it. VAC, Valve's anti-cheat, is enabled.
Which map has Mongolia Ulaanbaatar | 2X Vanilla selected?
The game generates its map: procedural, on Mongolia Ulaanbaatar | 2X Vanilla.
Wipe data
When does Mongolia Ulaanbaatar | 2X Vanilla wipe, and on what schedule?
The next wipe for Mongolia Ulaanbaatar | 2X Vanilla is an estimate, drawn from weekly: 7 days after its last wipe. Friday 30 October at 23:16 UTC is when the next wipe is due. This world was created 54 days 7 hours ago. Its tags carry a weekly wipe schedule.
Tags and filters
Where does Mongolia Ulaanbaatar | 2X Vanilla appear among Rust Data lists and filters?
On Rust Data, Mongolia Ulaanbaatar | 2X Vanilla appears in these lists: Modded Rust servers and 2x Rust servers. These filters bring it up on the server list: Region: Asia; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Gather rate: 2x.
How should you read the server tags on Mongolia Ulaanbaatar | 2X Vanilla?
The game's server browser reads these tags from Mongolia Ulaanbaatar | 2X Vanilla: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs163207 (Build): The server runs build 163207; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^w (Weekly): A wipe every week; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings; EA (East Asia): East Asia is its listing in the server browser. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way to join Mongolia Ulaanbaatar | 2X Vanilla?
The manual route: launch Rust, F1, then client.connect 202.70.47.214:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.