Offline 194.186.129.230:28015 checked 3h ago
TEST
Connect
srv = rust.server("194.186.129.230: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 49% 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 1, 33 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 14:36 UTC1d ago | NaN | NaN | running | 0 |
| 1 | Tue 27 Oct, 10:31 UTC2d ago | 1 | NaN | 1.2 days | 1 |
| 2 | Mon 14 Sep, 12:43 UTC45d ago | 2 | held half | 42.9 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
- 194.186.129.230:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 28 Oct 2026, 14:36 UTC
- hostname
- –
- first seen
- 14 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 · 151 on average | 127/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 195/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 74/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 222/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 data
What position does TEST take in the server rankings?
Player hours over seven days put TEST at #10,876, in the top 49% of the ranked set.
What population does TEST carry?
The current row shows TEST offline; the last response was 3 hours ago. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 14:00 UTC, averaging 2 players.
About the server
What Rust version does TEST run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by TEST. Joining needs the same protocol on your game; Steam handles the update.
Is TEST up, and what does its uptime show?
TEST is offline at this refresh; the last response came 3 hours ago. Over the last 7 full days the hours up number 5 of 168, 3%. Its earliest recorded date in Rust Data is 14 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. 194.186.129.230:28015 is its address.
Settings and map
What rules and settings are recorded for TEST?
No gather rate appears in the name: TEST. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC off.
Which map has TEST selected?
A procedural map runs on TEST, generated by the game.
Wipe data
On what schedule does TEST wipe?
Irregular wipe times on TEST leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 28 hours ago.
On TEST, what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 33 hours in. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags, lists
Which Rust Data filters and lists contain TEST?
These Rust Data lists include TEST: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the server tags on TEST?
The game's server browser reads these tags from TEST: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to TEST?
In Rust, F1 opens the console: type client.connect 194.186.129.230:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.