Rust Data

rustdata.spaceservers202.72.243.222:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 202.72.243.222:28015 checked 28d ago

Mongol

Connect

srv = rust.server("202.72.243.222:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #16,674 # top 70%
last wipe 55d ago # no schedule published
next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 best
RankRank in region
15k10k15k20k20 Sep24 Sep27 Sep1 Oct4 Oct8 Oct

Top 70% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
202.72.243.222:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
3 Sep 2026, 17:40 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)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 555 on average149/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average104/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average14/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 286 on average16/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average12/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 250 on average20/200

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does Mongol rank?

Rank #16,674 on seven-day player hours for Mongol, within the top 70% of all ranked servers.

How full does Mongol run?

Mongol returns no live count at this refresh, having last been seen 28 days ago.

About the server

What is the Rust version on Mongol?

The build is Rust network protocol 2633 and build 165217 on Linux, run by Mongol. Steam updates your game for you, but the protocol must match to join.

How reliable is Mongol, and is it up?

The latest sample has Mongol offline, with a last sighting 28 days ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 13 September 2026.

Where does Mongol sit?

No region is published by Mongol. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 202.72.243.222:28015.

Rules, settings, map

Which rules apply on Mongol, and what settings?

No gather rate appears in the name: Mongol. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.

What is the map on Mongol?

Mongol runs a procedural map, which the game generates.

Wipes and dates

On what schedule does Mongol wipe?

The record for Mongol holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 55 days 9 hours ago.

Lists and tags

Which lists on Rust Data hold Mongol, and which filters?

The Rust Data lists that Mongol fits are: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the server tags on Mongol?

The game's server browser reads these tags from Mongol: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. 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.

Join steps

What is the way into Mongol?

In Rust, F1 opens the console: type client.connect 202.72.243.222:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2633,gmvanilla,cs165217,ts8

Game

gmvanilla
Game mode Game mode: vanilla survival.
mp50
Max players The server lists 50 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2633
Protocol Protocol 2633 is required; a different game version cannot connect.
cs165217
Build Recorded game build: 165217.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

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.

Rust Data 34,855 players 11,686 servers online