Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
No rank history yet.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Friday 30 October, 23:16 UTC, in 1d 21h.
Weekly: 7 days after its last wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does Mongolia Ulaanbaatar | 2X Vanilla sit?
You'll see Mongolia Ulaanbaatar | 2X Vanilla listed in Asia, tagged EA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 202.70.47.214:28015.
How reliable is Mongolia Ulaanbaatar | 2X Vanilla, and is it up?
At this moment, Mongolia Ulaanbaatar | 2X Vanilla is offline; the last time it was seen was 45 days 12 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Mongolia Ulaanbaatar | 2X Vanilla sit?
You will find Mongolia Ulaanbaatar | 2X Vanilla on Rust network protocol 2633 and build 163207, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Mongolia Ulaanbaatar | 2X Vanilla wipe, and how often?
weekly: 7 days after its last wipe gives the basis for estimating Mongolia Ulaanbaatar | 2X Vanilla's next wipe. Friday 30 October at 23:16 UTC is the date set for its next wipe. It has been running its current world for 54 days 2 hours. Its tags state that it wipes weekly.
Player numbers
How many players does Mongolia Ulaanbaatar | 2X Vanilla usually have?
It has been 45 days 12 hours since Mongolia Ulaanbaatar | 2X Vanilla was last seen, and it is offline right now.
Tags and filters
How should you read the tags on Mongolia Ulaanbaatar | 2X Vanilla?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163207 (Build): The game build is 163207; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^w (Weekly): Wipes come once a week; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; EA (East Asia): The server browser lists it under East Asia are the tags Mongolia Ulaanbaatar | 2X Vanilla publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Mongolia Ulaanbaatar | 2X Vanilla appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Mongolia Ulaanbaatar | 2X Vanilla among them: 2x Rust servers, graded and Modded Rust servers, graded. 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.
Map and rules
Which rules does Mongolia Ulaanbaatar | 2X Vanilla enforce, and what are its settings?
Going by its name, Mongolia Ulaanbaatar | 2X Vanilla runs 2x gather. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
Mongolia Ulaanbaatar | 2X Vanilla runs which map?
A procedural map, generated by the game, is what Mongolia Ulaanbaatar | 2X Vanilla runs.
How to join
How should you connect to Mongolia Ulaanbaatar | 2X Vanilla?
To connect, start Rust, press F1, and type client.connect 202.70.47.214:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^w,^v,EA,gmrust,cs163207,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163207
BuildThe game build is 163207.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyWipes come once a week.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
EA
East AsiaThe server browser lists it under East Asia.
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.
Not enough figures yet to write a report. Check back after a few days on the list.