Rust Data

rustdata.spaceservers176.57.171.141:28816.ipynb

Run all rust-data · live

‹ All servers

Online 176.57.171.141:28815 checked 11m ago

Hamilton

moddedoxide

Connect

srv = rust.server("176.57.171.141:28816")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 1
rank #6,861 # top 31%
last wipe 22d ago # no schedule published
next wipe – # no rhythm it keeps
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75109:0018:0003:0012:0022:0007:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304009:0018:0003:0012:0022:0007: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 20 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 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.9 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

Tue 6 OctSun 4 OctFri 2 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 6 Oct, 10:46 UTC22d ago 1 NaN running 2
1 Sun 4 Oct, 16:16 UTC24d ago 2 NaN 1.8 days 2
2 Fri 2 Oct, 18:13 UTC26d ago 3 NaN 1.9 days 0
3 Sun 20 Sep, 14:35 UTC38d ago 0 NaN 12.2 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

4500 · seed 2147483647
Map of Hamilton
map
Procedural Map
size
4500
seed
2147483647
Open on RustMaps

Server

srv.info()
address
176.57.171.141:28815
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
6 Oct 2026, 15:46 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 · 150 on average105/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average122/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average149/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average46/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average4/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average18/1000

Quick answers

From the figures on this page.

Population

What position does Hamilton take in the server rankings?

Player hours over seven days put Hamilton at #6,861, in the top 31% of the ranked set.

What population does Hamilton carry?

The sample now reads 0 players for Hamilton, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 06:00 UTC, averaging 0 players.

Server facts

How well does Hamilton perform?

Averaged over 48 hours: 11 server fps, never under 5. Entity numbers reached 119,280, and that includes buildings, deployables and the rest. A high of 3,181 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

What is the Rust version on Hamilton?

Rust network protocol 2635 and build 168909 on Windows is what Hamilton runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is Hamilton, and is it up?

The current sample puts Hamilton online. A restart about 7 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 13 September 2026.

Which location does Hamilton run from?

No region is published by Hamilton. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 176.57.171.141:28815 is its address.

Rules, settings, map

Which settings and rules does Hamilton run?

No gather rate appears in the name: Hamilton. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has Hamilton selected?

Size 4,500, seed 2147483647: the procedural map on Hamilton, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.

Wipes and dates

On what schedule does Hamilton wipe?

No next wipe can be predicted for Hamilton, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 22 days 16 hours ago, and that is the one in play.

What is wipe day on Hamilton like?

Across recent wipes the busiest point averaged 2 players. 0 hours after the latest wipe, the crowd reached its peak.

Tags and filters

Where does Hamilton appear among Rust Data lists and filters?

On Rust Data, Hamilton appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on Hamilton?

Read by the game's server browser, the tags Hamilton publishes are: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way to join Hamilton?

Enter client.connect 176.57.171.141:28815 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 mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival in vanilla form.
mp50
Max players The server lists 50 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

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 45,345 players 11,642 servers online