Station XX-6853 · recording
Hamilton
Online 176.57.171.141:28815 checked 10m ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #6,853
- top 31%
- Last wipe
- 22d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −1into Tue 08:00 UTC
- Peak · 48 h
- 1most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 31% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 1.9 daysbetween real wipes
- on rhythm
- 67%of its recent wipes
- wipe-day peak
- 2players, last three wipes
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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 6 Oct, 10:46 UTC22d ago | M0.0▼falling | 1 | – | running | 2 | |
| Sun 4 Oct, 16:16 UTC24d ago | M0.0■steady | 2 | – | 1.8 days | 2 | |
| Fri 2 Oct, 18:13 UTC26d ago | M0.5▲rising | 3 | – | 1.9 days | 0 | |
| Sun 20 Sep, 14:35 UTC38d ago | M0.0■steady | 0 | – | 12.2 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Hamilton?
Generated by the game, the map on Hamilton is procedural, size 4,500 with seed 2147483647. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Hamilton?
No gather rate appears in the name of Hamilton. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on Hamilton right now?
0 of the 50 slots on Hamilton are filled right now. Averaged across the last seven days the population was 0 players, reaching a peak of 1. The busiest point in the last 48 hours came at 07:00 UTC, averaging 1 players.
How does Hamilton rank against other Rust servers?
On player hours for the past week, Hamilton sits at #6,853, which puts it inside the top 31% of every ranked server.
Operator and location
How reliably does Hamilton stay online?
As recorded now, Hamilton is running. Going by the uptime figure it reports, it restarted about 4 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
How well does Hamilton perform under load?
The 48-hour average is 11 server fps; 5 is the lowest observed. The world held up to 119,280 entities at its peak, buildings and deployables included. It reached a ceiling of 3,181 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does Hamilton run from?
No region is published by Hamilton. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 176.57.171.141:28815 is the address it uses.
What build of Rust does Hamilton use?
Hamilton is running Rust network protocol 2635 and build 168909 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on Hamilton?
The recent wipes averaged a busiest count of 2 players. 0 hours after the latest wipe, the crowd peaked.
How often does Hamilton wipe, and on which days?
There is no next wipe to predict at Hamilton, since its wipes fall at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 22 days 14 hours.
Tags
What do the server tags on Hamilton mean?
Tags published by Hamilton and read by the game's server browser include gmvanilla (Game mode): Survival in vanilla mode; mp50 (Max players): 50 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Hamilton appear?
You will find Hamilton on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto Hamilton?
To join, enter client.connect 176.57.171.141:28815 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.