Station EA-16730 · no signal
ALUBA-001
Offline EA 45.125.47.230:6229 checked 32d ago
- Players now
- 0/ 40
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,730
- top 71% · #496 in EA
- Last wipe
- 63d ago
- monthly schedule
- Next wipe
- 7d 11h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 40 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 71% of all ranked servers, top 89% in EA, and #659 of the quad servers (top 77%). Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 11h. The force wipe
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 ALUBA-001?
The procedural map on ALUBA-001 is size 4,000 with seed 1, 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 ALUBA-001?
You will find no gather rate in the name of ALUBA-001. You can have up to 4 players in a group (quad). pve is the game mode, no player-versus-player fighting. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. Vanilla is the label it uses for itself: no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on ALUBA-001?
No players are recorded on ALUBA-001 at this moment; it is offline, and the last sighting was 32 days 17 hours ago.
How does ALUBA-001 rank against other Rust servers?
The last seven days of player hours place ALUBA-001 at #16,730, in the top 71% of all ranked servers and #496 in Asia. It sits at #659 among quad servers.
Server details
How reliably does ALUBA-001 stay online?
No contact with ALUBA-001 right now, and the last recorded contact was 32 days 17 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Which region does ALUBA-001 run from?
In Asia ALUBA-001 lists itself, with the tag EA. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 45.125.47.230:6229.
What build of Rust does ALUBA-001 use?
ALUBA-001 is running Rust network protocol 2632 and build 162434 on a machine with Linux. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
How often does ALUBA-001 wipe, and on which days?
An estimate from the force wipe gives ALUBA-001's next wipe. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The present world dates from 63 days 16 hours. The tags it publishes carry a monthly wipe schedule.
Lists and tags
What do the server tags on ALUBA-001 mean?
The game's server browser reads the tags ALUBA-001 publishes: gmrust (Game mode): The game mode is standard Rust survival; mp40 (Max players): Slots: 40; ts4 (Group limit): Teams are capped at 4 players; v2632 (Protocol): To connect, your game must be on the same protocol, 2632; cs162434 (Build): It runs game build 162434; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; EA (East Asia): The server browser files it under East Asia. 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 ALUBA-001 appear?
These Rust Server Trends lists include ALUBA-001: Modded Rust servers, tracked live and Rust PvE servers. You will find it under these filters on the server list: Region: Asia; Type: Vanilla and Modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Monthly.
Connecting
How do you connect to ALUBA-001?
To join, enter client.connect 45.125.47.230:6229 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.