Station XX-4451 · recording
Hazmat Monthly Vanilla
Online 65.75.211.105:30007 checked 12m ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 4
- Rank
- #4,451
- top 20%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- 7d 18h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −3into Tue 03:00 UTC
- Peak · 48 h
- 4most 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 18h. The force wipe · high confidence
- wipe-day peak
- 4players, last three wipes
Coming wipes
- 7d 18hThu 5 Nov, 19:00 UTCFW
- 35d 18hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 6 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 19:04 UTC FW27d ago | M0.6▲rising | 4 | – | running | 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 Hazmat Monthly Vanilla?
The procedural map on Hazmat Monthly Vanilla is size 3,500 with seed 1884690038, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Hazmat Monthly Vanilla?
No gather rate appears in the name of Hazmat Monthly Vanilla. At the game's default, groups can have up to 8 players. survival is the game mode, gather, build and raid in the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on Hazmat Monthly Vanilla right now?
A reading taken now shows 0 players on Hazmat Monthly Vanilla, which has 100 slots. The seven-day average is 0 players, with a peak of 4. The busiest point in the last 48 hours came at 02:00 UTC, averaging 4 players.
How does Hazmat Monthly Vanilla rank against other Rust servers?
Over the last seven days, Hazmat Monthly Vanilla recorded enough player hours to reach #4,451 worldwide, placing it in the top 20% of all ranked servers.
Server facts
How reliably does Hazmat Monthly Vanilla stay online?
Hazmat Monthly Vanilla is up at the moment. The uptime it reports puts its last restart about 6 hours ago. 144 of 168 hours in the last 7 full days were up time, 86% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
Does Hazmat Monthly Vanilla hold a steady tick rate?
Its average server fps over the last 48 hours was 59, and it never dropped below 34. At its highest, it carried 74,103 entities: buildings, deployables and the world's other contents. It reached a ceiling of 2,335 MB of memory. What you feel as lag is the combination of low fps and a rising entity count.
Which region does Hazmat Monthly Vanilla run from?
A region is not published by Hazmat Monthly Vanilla. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 65.75.211.105:30007.
What build of Rust does Hazmat Monthly Vanilla use?
Hazmat Monthly Vanilla is running Rust network protocol 2635 and build 168909 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Hazmat Monthly Vanilla?
On average, the busiest point of its recent wipes drew 4 players. 6 hours into the latest wipe, the crowd reached its peak.
How often does Hazmat Monthly Vanilla wipe, and on which days?
The force wipe is the only wipe Hazmat Monthly Vanilla takes, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The present world dates from 27 days 4 hours.
Lists and tags
What do the server tags on Hazmat Monthly Vanilla mean?
These are the tags Hazmat Monthly Vanilla publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): Slots: 100; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Hazmat Monthly Vanilla appear?
The Rust Server Trends lists that take in Hazmat Monthly Vanilla are: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How to join
What steps get you onto Hazmat Monthly Vanilla?
To join, enter client.connect 65.75.211.105:30007 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. For the website, go to https://discord.com/invite/NUWAfEt.
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.