Station XX-16810 · no signal
Mane.DB
Offline 95.216.61.213:60414 checked 29d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,810
- top 70%
- Last wipe
- 39d ago
- monthly schedule
- Next wipe
- 6d 17h
- 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
- M –not enough readings
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 70% 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 6d 17h. The force wipe · high confidence
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 6d 17hThu 5 Nov, 19:00 UTCFW
- 34d 17hThu 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 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 20 Sep, 15:51 UTC39d ago | M0.0▲rising | 1 | – | 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 Mane.DB?
Generated by the game, the map on Mane.DB is procedural, size 6,000 with seed 889389380. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on Mane.DB?
No gather rate appears in the name of Mane.DB. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Player counts
What is the current population on Mane.DB?
A reading taken now finds Mane.DB offline; the most recent activity was 29 days 11 hours ago.
How does Mane.DB rank against other Rust servers?
Over the last seven days, Mane.DB recorded enough player hours to reach #16,810 worldwide, placing it in the top 70% of all ranked servers.
Operator and location
How reliably does Mane.DB stay online?
As recorded now, Mane.DB is not reachable, the last contact having been 29 days 11 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.
Which region does Mane.DB run from?
Nothing about a region comes from Mane.DB. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 95.216.61.213:60414.
What build of Rust does Mane.DB use?
On Linux, Mane.DB runs Rust network protocol 2633 and build 164530. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on Mane.DB?
On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak.
How often does Mane.DB wipe, and on which days?
The force wipe is the only wipe Mane.DB takes, once a month. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. 39 days 9 hours is how long the current world has been running. Its tags state a monthly wipe schedule.
Tags
What do the server tags on Mane.DB mean?
Tags published by Mane.DB and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp100 (Max players): The server has 100 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs164530 (Build): It runs game build 164530; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^m (Monthly): Wipes happen monthly, at the same time as Facepunch's force wipe; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Mane.DB appear?
You will find Mane.DB 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: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How to join
How do you connect to Mane.DB?
You can connect by pressing F1 in Rust and typing client.connect 95.216.61.213:60414 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects 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.