Offline 61.105.188.197:28015 checked 34d ago
TEST SERVER
Connect
srv = rust.server("61.105.188.197: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, measured since 25 Sep. 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
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. # The 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
3500 · seed 6
- map
- Procedural Map
- size
- 3500
- seed
- 6
Server
srv.info()- address
- 61.105.188.197:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 24 Sep 2026, 11:15 UTC
- hostname
- –
- first seen
- 25 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 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 254 on average | 185/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 244 on average | 317/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 107 on average | 64/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 45/200 |
| 4 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 49 on average | 93/100 |
| 5 | Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid | groups of 8+ · biweekly · 47 on average | 32/250 |
Quick answers
From the figures on this page.
Population
What position does TEST SERVER take in the server rankings?
Over the last seven days TEST SERVER sits at #16,418 on player hours, in the top 71% of ranked servers.
What population does TEST SERVER carry?
The current row shows TEST SERVER offline; the last response was 34 days ago.
Server data
Which Rust version is TEST SERVER on?
Version Rust network protocol 2633 and build 163794 on Windows is reported by TEST SERVER. Joining needs the same protocol on your game; Steam handles the update.
Is TEST SERVER up, and what does its uptime show?
The latest sample has TEST SERVER offline, with a last sighting 34 days ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 25 September 2026.
Which location does TEST SERVER run from?
For TEST SERVER, no region is published. 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 61.105.188.197:28015.
Rules, settings, map
What rules and settings are recorded for TEST SERVER?
You will not find a gather rate in the string TEST SERVER. Eight players per group: that is the game's default, and it applies here. Game mode roleplay, with this note: jobs, towns and rules for roleplay. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has TEST SERVER loaded?
TEST SERVER runs a procedural map of size 3,500 with seed 6, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does TEST SERVER wipe, and on what schedule?
The next wipe for TEST SERVER is an estimate, drawn from the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 35 days 6 hours ago, and that is the one in play. Its tags carry a wipe schedule of every two weeks.
Tags and filters
Which lists on Rust Data hold TEST SERVER, and which filters?
The Rust Data lists that TEST SERVER fits are: Modded Rust servers, Rust PvE servers and Rust roleplay servers. Under these filters on the server list, it is listed: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Roleplay ^r, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
How should you read the server tags on TEST SERVER?
These tags are published by TEST SERVER and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): The server runs build 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^b (Biweekly): Wipes run on a two-week cycle; ^r (Roleplay): Listed as a roleplay server; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 TEST SERVER?
The manual route: launch Rust, F1, then client.connect 61.105.188.197:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.