Offline 194.9.118.64:28015 checked 30d ago
MY RUST STAGING TEST
Connect
srv = rust.server("194.9.118.64: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 · 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 28 Sep, 14:58 UTC30d ago | 1 | 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
- 194.9.118.64:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 28 Sep 2026, 14:58 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 514 on average | 523/525 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 385/450 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 48/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 51/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 54/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 241 on average | 161/200 |
Quick answers
From the figures on this page.
Population
What position does MY RUST STAGING TEST take in the server rankings?
Rank #16,970 on seven-day player hours for MY RUST STAGING TEST, within the top 71% of all ranked servers.
How full does MY RUST STAGING TEST run?
The current row shows MY RUST STAGING TEST offline; the last response was 30 days 20 hours ago.
Server facts
What Rust version does MY RUST STAGING TEST run?
The build is Rust network protocol 2634 and build 166040 on Windows, run by MY RUST STAGING TEST. Steam updates your game for you, but the protocol must match to join.
Is MY RUST STAGING TEST up, and what does its uptime show?
Offline now for MY RUST STAGING TEST, last seen 30 days 20 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 24 September 2026.
In which location is MY RUST STAGING TEST hosted?
No region is published by MY RUST STAGING TEST. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 194.9.118.64:28015.
Map and rules
Which settings and rules does MY RUST STAGING TEST run?
The name MY RUST STAGING TEST carries no gather rate. 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. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.
Which map has MY RUST STAGING TEST selected?
MY RUST STAGING TEST runs a procedural map, which the game generates.
Wipe schedule
When does MY RUST STAGING TEST wipe, and how often?
A rhythm cannot be read from the wipes of MY RUST STAGING TEST on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 30 days 21 hours ago, and that is the one in play.
What is wipe day on MY RUST STAGING TEST like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in.
Tags and filters
Which Rust Data filters and lists contain MY RUST STAGING TEST?
These Rust Data lists include MY RUST STAGING TEST: 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.
How should you read the server tags on MY RUST STAGING TEST?
These tags are published by MY RUST STAGING TEST and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): 5 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166040 (Build): Build number: 166040; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join MY RUST STAGING TEST?
In Rust, F1 opens the console: type client.connect 194.9.118.64:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.