Offline 188.19.102.77:28015 checked 19d ago
Test
Connect
srv = rust.server("188.19.102.77: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 · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 21d 14h | Thu 19 Nov, 20:52 UTC | wipe |
| 2 | 35d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 20:52 UTC20d ago | 1 | NaN | running | 0 |
| 1 | Tue 6 Oct, 16:00 UTC22d ago | 1 | NaN | 2.2 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 188.19.102.77:28015
- region
- –
- max players
- 200
- group limit
- 10 max
- wipe schedule
- biweekly
- last wipe
- 1 Oct 2026, 18:06 UTC
- hostname
- –
- first seen
- 6 Oct 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 · 252 on average | 187/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 241 on average | 88/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 105 on average | 61/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 53/200 |
| 4 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 50 on average | 19/100 |
| 5 | Rust Empires - Roleplay/RP friendly, Cities, PVE, No KOS outsid | groups of 8+ · biweekly · 48 on average | 25/250 |
Quick answers
From the figures on this page.
Population
What position does Test take in the server rankings?
Rank #13,604 on seven-day player hours for Test, within the top 61% of all ranked servers.
What population does Test carry?
Offline now for Test, with the last sample 19 days 10 hours ago.
About the server
Which Rust version is Test on?
Rust network protocol 2634 and build 167398 on Windows is what Test runs. 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 19 days 10 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 6 October 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. You can reach it at 188.19.102.77:28015.
Map and rules
Which rules apply on Test, and what settings?
The name Test carries no gather rate. The cap on a group is 10 players. Recorded as pve, player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Wipes and dates
On what schedule does Test wipe?
The tag sets the prediction: Test has too few wipes on record to confirm its schedule. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 27 days 12 hours ago. Its tags carry a wipe schedule of every two weeks.
What is wipe day on Test like?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 1 hours in.
Tags and filters
Where does Test appear among Rust Data lists and filters?
These Rust Data lists include Test: Modded Rust servers and Rust PvE servers. Under these filters on the server list, it is listed: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Which meanings do the tags on Test hold?
Read by the game's server browser, the tags Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp200 (Max players): Slot count: 200; ts10 (Group limit): The team cap is 10; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Recorded game build: 167398; 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; ^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): 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.
Connecting
How can I connect to Test?
Enter client.connect 188.19.102.77:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.