Offline 66.51.99.158:4600 checked 45d ago
TEST SERVER #1
Connect
srv = rust.server("66.51.99.158:4601")
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 bestWipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 66.51.99.158:4600
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 02:50 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 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 153/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 185/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 95/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 251/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Population
What position does TEST SERVER #1 take in the server rankings?
Player hours over seven days put TEST SERVER #1 at #15,121, in the top – of the ranked set.
How full does TEST SERVER #1 run?
Offline now for TEST SERVER #1, with the last sample 45 days 14 hours ago.
About the server
What is the Rust version on TEST SERVER #1?
The build is Rust network protocol 2633 and build 163794 on Linux, run by TEST SERVER #1. Steam updates your game for you, but the protocol must match to join.
Is TEST SERVER #1 up, and what does its uptime show?
TEST SERVER #1 is offline at this refresh; the last response came 45 days 14 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 13 September 2026.
In which location is TEST SERVER #1 hosted?
There is no region published for TEST SERVER #1. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 66.51.99.158:4600.
Map and rules
Which settings and rules does TEST SERVER #1 run?
You will not find a gather rate in the string TEST SERVER #1. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has TEST SERVER #1 loaded?
TEST SERVER #1 runs a procedural map, which the game generates.
Wipes and dates
When does TEST SERVER #1 wipe, and how often?
Too few wipes are on record for TEST SERVER #1 to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 55 days 13 hours ago.
Tags and filters
Where does TEST SERVER #1 appear among Rust Data lists and filters?
On Rust Data, TEST SERVER #1 appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on TEST SERVER #1?
These tags are published by TEST SERVER #1 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): 40 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): Build number: 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into TEST SERVER #1?
In Rust, F1 opens the console: type client.connect 66.51.99.158:4600. Launch Rust on this page does the same by opening the game through Steam and connecting.