Offline 178.34.151.130:28015 checked 24d ago
My Test Rust Server
Connect
srv = rust.server("178.34.151.130: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 bestTop 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 16:58 UTC24d 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
- 178.34.151.130:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 16:58 UTC
- hostname
- –
- first seen
- 3 Oct 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 · 553 on average | 572/675 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 363/525 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 297 on average | 43/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 296 on average | 45/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 272 on average | 119/200 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 253 on average | 140/300 |
Quick answers
From the figures on this page.
Population data
What position does My Test Rust Server take in the server rankings?
Player hours over seven days put My Test Rust Server at #15,967, in the top 71% of the ranked set.
How many players does My Test Rust Server hold at once?
My Test Rust Server returns no live count at this refresh, having last been seen 24 days 3 hours ago.
About the server
Which Rust version is My Test Rust Server on?
Rust network protocol 2634 and build 166652 on Windows is what My Test Rust Server runs. Joining needs the same protocol on your game; Steam handles the update.
Is My Test Rust Server up, and what does its uptime show?
The latest sample has My Test Rust Server offline, with a last sighting 24 days 3 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 3 October 2026.
Where does My Test Rust Server sit?
There is no region published for My Test Rust Server. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 178.34.151.130:28015.
Map and rules
Which rules apply on My Test Rust Server, and what settings?
No gather rate appears in the name: My Test Rust Server. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. The server browser lists it under Community. Anti-cheat status: VAC off.
Which map has My Test Rust Server loaded?
My Test Rust Server runs a procedural map, which the game generates.
Wipe data
On what schedule does My Test Rust Server wipe?
A rhythm cannot be read from the wipes of My Test Rust Server on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 24 days 3 hours ago, and that is the one in play.
On My Test Rust Server, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. 1 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which lists on Rust Data hold My Test Rust Server, and which filters?
These Rust Data lists include My Test Rust Server: 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 Test Rust Server?
Read by the game's server browser, the tags My Test Rust Server publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not 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.
Connecting
What is the way into My Test Rust Server?
The manual route: launch Rust, F1, then client.connect 178.34.151.130:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.