Rust Data

rustdata.spaceservers120.220.76.192:13232.ipynb

Run all rust-data · live

‹ All servers

Online 120.220.76.192:13231 checked 10m ago

MY TEST SERVER | Default

moddedoxide

Connect

srv = rust.server("120.220.76.192:13232")
print(srv.connect_command)

Right now

srv.summary()
players now 0/3 # 0% full
7-day average 0 # peak 1
rank #6,196 # top 28%
last wipe 5d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75100:0009:0018:0004:0013:0022:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020000:0009:0018:0004:0013:0022:00

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 best
RankRank in region
15k10k15k20k20 Sep27 Sep5 Oct12 Oct20 Oct27 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

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

usual gap20.8 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Thu 22 OctThu 1 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 15 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 22 Oct, 14:05 UTC5d ago 1 NaN running 0
1 Thu 1 Oct, 17:56 UTC FW26d ago 1 halved by day 1 20.8 days 0

# 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

4096 · seed 1337
Map of MY TEST SERVER | Default
map
Custom Map
size
4096
seed
1337

Server

srv.info()
address
120.220.76.192:13231
region
–
max players
3
group limit
8, the default
wipe schedule
–
last wipe
22 Oct 2026, 14:05 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
0ShockRust | Blue | NoLimitno group limit · 163 on average63/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average129/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 113 on average75/225
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average18/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 87 on average67/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average15/1000

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does MY TEST SERVER | Default rank?

Rank #6,196 on seven-day player hours for MY TEST SERVER | Default, within the top 28% of all ranked servers.

How full does MY TEST SERVER | Default run?

MY TEST SERVER | Default reports 0 players at this refresh, with 3 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 06:00 UTC is the busiest, at 1 players.

Server data

How smoothly does MY TEST SERVER | Default run?

The 48-hour average is 110 server fps, with a low of 56. Buildings, deployables and all else in the world took the count as high as 62,919 entities. Memory peaked at 2,907 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does MY TEST SERVER | Default run?

The build is Rust network protocol 2635 and build 168909 on Windows, run by MY TEST SERVER | Default. Steam updates your game for you, but the protocol must match to join.

How reliable is MY TEST SERVER | Default, and is it up?

The current sample puts MY TEST SERVER | Default online. A restart about 29 hours ago is what its reported uptime implies. 91 of 168 hours up over the last 7 full days, or 54%. Rust Data logged it first on 13 September 2026.

Where does MY TEST SERVER | Default sit?

No region is published by MY TEST SERVER | Default. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 120.220.76.192:13231 is its address.

Rules, settings, map

What rules and settings are recorded for MY TEST SERVER | Default?

You will not find a gather rate in the string MY TEST SERVER | Default. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

Which map has MY TEST SERVER | Default loaded?

MY TEST SERVER | Default runs a procedural map of size 4,096 with seed 1337, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Custom Map is what the map name field says.

Wipe schedule

When does MY TEST SERVER | Default wipe, and how often?

Too few wipes are on record for MY TEST SERVER | Default to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 5 days 9 hours ago.

On MY TEST SERVER | Default, what happens on wipe day?

The average peak over recent wipes is 1 players. 15 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 1.

Tags, lists

Where does MY TEST SERVER | Default appear among Rust Data lists and filters?

On Rust Data, MY TEST SERVER | Default appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Which meanings do the tags on MY TEST SERVER | Default hold?

These tags are published by MY TEST SERVER | Default and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp3 (Max players): Slot count: 3; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 MY TEST SERVER | Default?

Enter client.connect 120.220.76.192:13231 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp3
Max players Slot count: 3.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 58,097 players 11,747 servers online