Offline 144.31.232.228:28015 checked 34d ago
Waiting for RCON to come up...
Connect
srv = rust.server("144.31.232.228:28017")
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. 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 best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 144.31.232.228:28015
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 20:52 UTC
- hostname
- –
- first seen
- 24 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 54/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 72/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 22/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 6/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Waiting for RCON to come up... rank?
Rank #16,066 on seven-day player hours for Waiting for RCON to come up..., within the top 71% of all ranked servers.
What population does Waiting for RCON to come up... carry?
Waiting for RCON to come up... returns no live count at this refresh, having last been seen 34 days 7 hours ago.
Server data
Which Rust version is Waiting for RCON to come up... on?
The build is Rust network protocol 2633 and build 165217 on Linux, run by Waiting for RCON to come up.... Joining needs the same protocol on your game; Steam handles the update.
Is Waiting for RCON to come up... up, and what does its uptime show?
Waiting for RCON to come up... is offline at this refresh; the last response came 34 days 7 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 24 September 2026.
In which location is Waiting for RCON to come up... hosted?
For Waiting for RCON to come up..., no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 144.31.232.228:28015 is its address.
Settings and map
What rules and settings are recorded for Waiting for RCON to come up...?
The name Waiting for RCON to come up... carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.
What is the map on Waiting for RCON to come up...?
A procedural map runs on Waiting for RCON to come up..., generated by the game.
Wipe schedule
On what schedule does Waiting for RCON to come up... wipe?
Too few wipes are on record for Waiting for RCON to come up... to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 34 days 9 hours ago.
Tags and filters
Which Rust Data filters and lists contain Waiting for RCON to come up...?
On Rust Data, Waiting for RCON to come up... appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Waiting for RCON to come up... hold?
These tags are published by Waiting for RCON to come up... and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): The server lists 40 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): Build number: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
How can I connect to Waiting for RCON to come up...?
In Rust, F1 opens the console: type client.connect 144.31.232.228:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.