Online 151.80.25.50:28016 checked 11m ago
aux03
Connect
srv = rust.server("151.80.25.50:28026")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 40% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 21h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 21h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 17:50 UTC FW28d ago | 0 | NaN | running | 0 |
# 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.
display(srv.map, srv.info())Map
4250 · seed 60139
- map
- Procedural Map
- size
- 4250
- seed
- 60139
Server
srv.info()- address
- 151.80.25.50:28016
- region
- –
- max players
- 150
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:50 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 506 on average | 231/275 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 315/350 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 282 on average | 765/1000 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 277 on average | 46/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 893/950 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 242 on average | 739/800 |
Quick answers
From the figures on this page.
Population
How does aux03 compare in the rankings?
Over the last seven days aux03 sits at #8,826 on player hours, in the top 40% of ranked servers.
What population does aux03 carry?
Current row: 0 players on aux03, against 150 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
How smoothly does aux03 run?
The 48-hour average is 20 server fps, with a low of 20. The entity count peaked at 105,848, covering buildings, deployables and the rest of the world. The memory field tops out at 4,078 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is aux03 on?
The build is Rust network protocol 2635 and build 168909 on Linux, run by aux03. Joining needs the same protocol on your game; Steam handles the update.
Is aux03 up, and what does its uptime show?
aux03 reports itself online at the current refresh. Count back 3 days 13 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 13 September 2026.
Which location does aux03 run from?
There is no region published for aux03. Rust Data does not look up where the machine stands; it shows where a server says it is. 151.80.25.50:28016 is its address.
Settings and map
Which settings and rules does aux03 run?
The name aux03 carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.
What is the map on aux03?
aux03 runs a procedural map of size 4,250 with seed 60139, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
On what schedule does aux03 wipe?
A single wipe each month, the force wipe, is all aux03 does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 28 days 3 hours ago.
What is wipe day on aux03 like?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Where does aux03 appear among Rust Data lists and filters?
On Rust Data, aux03 appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on aux03 hold?
The game's server browser reads these tags from aux03: gmrust (Game mode): Rust survival in its standard form; mp150 (Max players): 150 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
How can I connect to aux03?
The manual route: launch Rust, F1, then client.connect 151.80.25.50:28016. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.