Hamilton

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 11m ago · 176.57.171.141:28815

Abstract

We describe the public Rust server Hamilton, reached at 176.57.171.141:28815. At the last check it held 0 of 50 places, against a seven-day mean of 0 and a peak of 1¹. It ranks #6,861 of all servers, the top 31%. It last wiped 22d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Plate 1: The server's own banner, as it publishes it. Table 1 gives its figures at the last check.

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/50	0% full
In the queue	0	no queue
Seven-day mean	0	peak 1, 48 h peak 1
Rank²	#6,861	top 31%
Last wipe	22d ago	no schedule published
Next wipe³	–	no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

Figure 2: Server performance. 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.

4Rank

The server stands in the top 31% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: no rhythm it keeps

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

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Usual gap	1.9 days	between real wipes
On rhythm	67%	of its recent wipes
Wipe-day peak	2	players, last three wipes

Tue 6 OctSun 4 OctFri 2 Oct

Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Tue 6 Oct, 10:4622d ago	1	–	running	2
Sun 4 Oct, 16:1624d ago	2	–	1.8 d	2
Fri 2 Oct, 18:1326d ago	3	–	1.9 d	0
Sun 20 Sep, 14:3538d ago	0	–	12.2 d	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of Hamilton — Figure 5: The map: Procedural Map, size 4500, seed 2147483647. Open on RustMaps.

Table 4: The server's published settings.

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
Map	Procedural Map
Size	4500
Seed	2147483647

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and servers wiping soon [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 149 on average	127/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10EU · groups of 8+ · weekly · 128 on average	131/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average	190/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average	68/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 88 on average	8/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	22/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1Does Hamilton perform well?

The server fps averaged 12 over the last 48 hours, never dropping below 5. The highest number of entities it carried was 119,280, comprising buildings, deployables and all other objects. Memory use peaked at 3,181 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2In which location is Hamilton based?

There is no region published for Hamilton. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 176.57.171.141:28815.

A.3What is the online status and reliability of Hamilton?

Hamilton is currently online. The uptime it reports indicates a restart about 8 hours ago. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. It was first observed on 13 September 2026 by Rust Statistics.

A.4What version of Rust is run on Hamilton?

The version of Rust on Hamilton is network protocol 2635 and build 168909, and the operating system is Windows. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.5When are wipes carried out on Hamilton?

With irregular wipe times, Hamilton offers no next wipe to predict. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 22 days 17 hours have passed since the current world was generated.

A.6What characterises wipe day on Hamilton?

The average busiest point of recent wipes was 2 players. The crowd reached its maximum 0 hours after the latest wipe.

Player count

A.7What is the rank of Hamilton among Rust servers?

The seven-day player-hours ranking puts Hamilton at #6,861, within the top 31% of ranked servers.

A.8How would you characterise the player activity on Hamilton?

On Hamilton, 0 of the 50 slots are occupied at present. Averaged over the last seven days: 0 players; the same period peaks at 1. Of the last 48 hours, the peak hour falls at 06:00 UTC, with an average of 0 players.

Tags, lists

A.9What is the meaning of the tags on Hamilton?

The game's server browser reads gmvanilla (Game mode): This is survival in its vanilla form; mp50 (Max players): It offers 50 slots; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game, which Hamilton publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can Hamilton be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that Hamilton fits. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Rules, settings, map

A.11What are the settings and rules that govern Hamilton?

Its name carries no gather rate for Hamilton. The group cap is 8 players, which is the default in the game. survival is the game mode here; gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Oxide on this server. VAC is active: that is Valve's anti-cheat.

A.12On which map does Hamilton take place?

Generated by the game from seed 2147483647, the procedural map on Hamilton measures 4,500. Because size and seed determine the map, RustMaps can show it, linked from this page.

How to join

A.13What is the process for joining Hamilton?

Press F1 inside Rust to open the console and enter client.connect 176.57.171.141:28815. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.

Tag	Meaning
Game
`gmvanilla`	Game mode. This is survival in its vanilla form.
`mp50`	Max players. It offers 50 slots.
`ts8`	Group limit. Teams are limited to 8, as the game defaults.
`v2635`	Protocol. Your game must run protocol 2635 to connect.
`cs168909`	Build. This server runs 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. Plugins are handled by Oxide (uMod).
`^z`	Modded. Modded listing: plugins or settings modify 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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.