Offline 178.66.0.10:28015 checked 26d ago
TEST
Connect
srv = rust.server("178.66.0.10: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 60% 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 5, 3 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 17:09 UTC FW27d ago | 5 | NaN | running | 4 |
| 1 | Wed 30 Sep, 19:24 UTC28d ago | 5 | NaN | 0.9 days | 3 |
| 2 | Tue 29 Sep, 16:50 UTC29d ago | 5 | NaN | 1.1 days | 0 |
| 3 | Mon 28 Sep, 14:23 UTC30d ago | 4 | NaN | 1.1 days | 1 |
| 4 | Sun 27 Sep, 13:22 UTC31d ago | 5 | NaN | 1 days | 2 |
| 5 | Sat 26 Sep, 05:34 UTC32d ago | 5 | NaN | 1.3 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
- 178.66.0.10:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 19:56 UTC
- hostname
- –
- first seen
- 21 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 · 552 on average | 588/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 · 299 on average | 49/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 298 on average | 40/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 271 on average | 130/200 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 254 on average | 140/300 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does TEST rank?
Over the last seven days TEST sits at #13,894 on player hours, in the top 60% of ranked servers.
What population does TEST carry?
The current row shows TEST offline; the last response was 26 days 22 hours ago.
Server data
What Rust version does TEST run?
The build is Rust network protocol 2634 and build 166494 on Windows, run by TEST. Steam updates your game for you, but the protocol must match to join.
Is TEST up, and what does its uptime show?
TEST is offline at this refresh; the last response came 26 days 22 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 21 September 2026.
In which location is TEST hosted?
There is no region published for TEST. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 178.66.0.10:28015.
Map and rules
Which settings and rules does TEST run?
You will not find a gather rate in the string TEST. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: 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.
Which map has TEST selected?
The game generates its map: procedural, on TEST.
Wipe schedule
When does TEST wipe, and how often?
TEST wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 27 days ago.
On TEST, what happens on wipe day?
Across recent wipes the busiest point averaged 5 players. The crowd on the latest wipe topped out 3 hours after it began.
Tags, lists
Which lists on Rust Data hold TEST, and which filters?
The Rust Data lists that TEST fits are: Rust community servers, unfiltered. These filters bring it up 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 TEST?
These tags are published by TEST and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): Build number: 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not 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.
Join steps
What is the way to join TEST?
In Rust, F1 opens the console: type client.connect 178.66.0.10:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.