Working its way up from the back of the class: #16,730 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
47/ 100
D
Slipped a little: down 899 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 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.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h.
The force wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll see ALUBA-001 listed in Asia, tagged EA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 45.125.47.230:6229.
How reliable is ALUBA-001, and is it up?
The server is down: ALUBA-001 is offline now, with the last sighting 32 days 23 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does ALUBA-001 sit?
Rust network protocol 2632 and build 162434 on Linux is what ALUBA-001 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does ALUBA-001 wipe, and how often?
the force wipe gives the basis for estimating ALUBA-001's next wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 63 days 23 hours. The tags show a monthly wipe schedule.
Population
Where does ALUBA-001 place in the wider field of Rust servers?
In Asia, ALUBA-001 is #496, and overall it is #16,730 on player hours over the last seven days, in the top 71% of all ranked servers. In the quad group, it ranks #659.
What does the population on ALUBA-001 look like?
ALUBA-001 is offline at the moment; the last time it was seen was 32 days 23 hours ago.
Tags and filters
How should you read the tags on ALUBA-001?
The game's browser takes its cue from the tags ALUBA-001 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp40 (Max players): Its slot count is 40; ts4 (Group limit): Teams cap out at 4; v2632 (Protocol): The game protocol is 2632, so your game must match that version to join; cs162434 (Build): Build number: 162434; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EA (East Asia): You will find it under East Asia in the browser. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature ALUBA-001?
These Rust Server Score lists count ALUBA-001 among them: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: 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.
Server rules
What settings and rules apply on ALUBA-001?
Nothing in the name of ALUBA-001 states a gather rate. You can have up to 4 players in a group (quad). It runs pve, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The vanilla label is its own: you get the unmodified game: no rate changes, no kits, no rule changes. You are covered by VAC, Valve's anti-cheat.
Which map is in play on ALUBA-001?
A procedural map of size 4,000 and seed 1, generated by the game, is what ALUBA-001 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto ALUBA-001?
To connect, start Rust, press F1, and type client.connect 45.125.47.230:6229. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2632,^m,^v,EA,^p,gmrust,cs162434,ts4,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp40
Max playersIts slot count is 40.
ts4
Group limitTeams cap out at 4.
v2632
ProtocolThe game protocol is 2632, so your game must match that version to join.
cs162434
BuildBuild number: 162434.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
EA
East AsiaYou will find it under East Asia in the browser.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).