Offline 72.178.40.244:29015 checked 30d ago
LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER
Connect
srv = rust.server("72.178.40.244:29017")
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 · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 27 Sep, 20:31 UTC30d 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 72.178.40.244:29015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Sep 2026, 20:31 UTC
- hostname
- –
- first seen
- 27 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 | 214/250 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 327 on average | 15/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 325 on average | 19/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 115/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.
Player counts
Against other Rust servers, how does LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER rank?
Over the last seven days LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER sits at #16,943 on player hours, in the top 71% of ranked servers.
How full does LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER run?
Offline now for LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER, with the last sample 30 days 7 hours ago.
Server data
What Rust version does LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER run?
Version Rust network protocol 2633 and build 165217 on Linux is reported by LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER. The protocol has to match before you can join, and Steam does the updating.
How reliable is LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER, and is it up?
Offline now for LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER, last seen 30 days 7 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 27 September 2026.
Where does LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER sit?
For LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 72.178.40.244:29015.
Rules, settings, map
Which settings and rules does LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER run?
The name LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and 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. VAC, Valve's anti-cheat, is enabled.
What is the map on LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER?
LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER runs a procedural map, which the game generates.
Wipe schedule
When does LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER wipe, and how often?
The record for LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 30 days 7 hours ago.
On LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER, what happens on wipe day?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Which lists on Rust Data hold LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER, and which filters?
The Rust Data lists that LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER hold?
These tags are published by LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
How can I connect to LOCAL AUTOMATION TEST - NOT A PUBLIC SERVER?
Enter client.connect 72.178.40.244:29015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.