Offline 98.60.228.203:28015 checked 15h ago
test
Connect
srv = rust.server("98.60.228.203: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 37% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 10h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 10h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 10h | 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 15:42 UTC26d ago | 1 | NaN | running | 1 |
| 1 | Tue 22 Sep, 15:31 UTC36d ago | 1 | held half | 10 days | 1 |
| 2 | Sun 20 Sep, 17:23 UTC38d ago | 1 | NaN | 1.9 days | 1 |
# 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
- 98.60.228.203:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 2 Oct 2026, 15:42 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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 46/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19/1000 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 79 on average | 163/700 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 71 on average | 73/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10 | EU · groups of 16+ · monthly · 66 on average | 11/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 64 on average | 145/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does test rank?
Rank #8,231 on seven-day player hours for test, within the top 37% of all ranked servers.
What population does test carry?
Offline now for test, with the last sample 15 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 18:00 UTC, averaging 1 players.
Server data
Which Rust version is test on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by test. Steam updates your game for you, but the protocol must match to join.
Is test up, and what does its uptime show?
The latest sample has test offline, with a last sighting 15 hours ago. 11 of 168 hours up over the last 7 full days, or 7%. The first row Rust Data holds for it is dated 13 September 2026.
Where does test sit?
No region is published by test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 98.60.228.203:28015 is its address.
Settings and map
Which rules apply on test, and what settings?
No gather rate appears in the name: test. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
Wipe data
When does test wipe, and how often?
The only wipe test takes is the monthly force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 26 days 16 hours ago. A monthly wipe schedule is published in its tags.
On test, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags and filters
Which Rust Data filters and lists contain test?
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: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on test?
Read by the game's server browser, the tags test publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; 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; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins; modded (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join test?
The manual route: launch Rust, F1, then client.connect 98.60.228.203:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.