Online 24.42.149.142:28015 checked 9m ago
WHYPrintRust
Connect
srv = rust.server("24.42.149.142:28016")
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 bestTop 51% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 23:15 UTC FW26d ago | 2 | NaN | running | 0 |
| 1 | Wed 30 Sep, 23:26 UTC27d ago | 2 | NaN | 1 days | 0 |
| 2 | Fri 4 Sep, 23:28 UTC53d ago | NaN | NaN | 26 days | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 24.42.149.142:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 23:15 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 · 532 on average | 217/250 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 327 on average | 16/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 325 on average | 21/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 118/200 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 278 on average | 40/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 264 on average | 42/100 |
Quick answers
From the figures on this page.
Population data
What position does WHYPrintRust take in the server rankings?
Rank #11,240 on seven-day player hours for WHYPrintRust, within the top 51% of all ranked servers.
How many players does WHYPrintRust hold at once?
The sample now reads 0 players for WHYPrintRust, out of 20 slots. Over the last seven days it averaged 0 players and peaked at 2.
About the server
What Rust version does WHYPrintRust run?
Rust network protocol 2635 and build 168909 on Linux is what WHYPrintRust runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is WHYPrintRust, and is it up?
WHYPrintRust reports itself online at the current refresh. 168 of 168 hours up over the last 7 full days, or 100%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is WHYPrintRust hosted?
For WHYPrintRust, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 24.42.149.142:28015 is its address.
Rules, settings, map
Which rules apply on WHYPrintRust, and what settings?
You will not find a gather rate in the string WHYPrintRust. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC off.
Which map has WHYPrintRust loaded?
The game generates its map: procedural, on WHYPrintRust.
Wipe data
When does WHYPrintRust wipe, and on what schedule?
Irregular wipe times on WHYPrintRust leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 26 days 5 hours ago.
What is wipe day on WHYPrintRust like?
Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which lists on Rust Data hold WHYPrintRust, and which filters?
On Rust Data, WHYPrintRust appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on WHYPrintRust?
These tags are published by WHYPrintRust and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp20 (Max players): The server lists 20 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to WHYPrintRust?
Enter client.connect 24.42.149.142:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.