Offline 188.113.32.189:28015 checked 33d ago
TEST
Connect
srv = rust.server("188.113.32.189: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 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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
- 188.113.32.189:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 19:32 UTC
- hostname
- –
- first seen
- 26 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 | 20/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 39/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 5/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 23/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 96/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TEST rank?
Over the last seven days TEST sits at #14,459 on player hours, in the top 61% of ranked servers.
How full does TEST run?
TEST returns no live count at this refresh, having last been seen 33 days 3 hours ago.
Server facts
What Rust version does TEST run?
The build is Rust network protocol 2633 and build 163207 on Windows, run by TEST. The protocol has to match before you can join, and Steam does the updating.
How reliable is TEST, and is it up?
Offline now for TEST, last seen 33 days 3 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 26 September 2026.
Where does TEST sit?
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. 188.113.32.189:28015 is its address.
Rules, settings, map
Which settings and rules does TEST run?
You will not find a gather rate in the string TEST. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
What is the map on TEST?
TEST runs a procedural map, which the game generates.
Wipes and dates
On what schedule does TEST wipe?
The record for TEST holds too few wipes to show a 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 8 hours ago.
Tags and filters
Which lists on Rust Data hold TEST, and which filters?
The Rust Data lists that TEST fits are: 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.
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): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs163207 (Build): The server runs build 163207; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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?
In Rust, F1 opens the console: type client.connect 188.113.32.189:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.