Offline 192.154.104.162:28016 checked 4d ago
RPTEST
Connect
srv = rust.server("192.154.104.162:28027")
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 best
Top 56% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 08:35 UTC4d ago | 1 | NaN | running | 1 |
| 1 | Thu 22 Oct, 20:44 UTC6d ago | 1 | NaN | 1.5 days | 0 |
| 2 | Wed 21 Oct, 02:01 UTC7d ago | 1 | NaN | 1.8 days | 0 |
| 3 | Tue 20 Oct, 17:42 UTC8d ago | 1 | NaN | 0.3 days | 0 |
| 4 | Sun 18 Oct, 12:57 UTC10d ago | 0 | NaN | 2.2 days | 1 |
| 5 | Sun 18 Oct, 06:53 UTC10d ago | 2 | NaN | 0.3 days | 1 |
| 6 | Sat 17 Oct, 14:12 UTC11d ago | 2 | NaN | 0.7 days | 1 |
| 7 | Wed 14 Oct, 17:47 UTC14d ago | 1 | NaN | 2.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
- 192.154.104.162:28016
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 08:35 UTC
- hostname
- –
- first seen
- 2 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 | ShockRust | Blue | NoLimit | no group limit · 157 on average | 109/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 133/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 101/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 31/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 26/1000 |
Quick answers
From the figures on this page.
Player counts
How does RPTEST compare in the rankings?
Player hours over seven days put RPTEST at #12,451, in the top 56% of the ranked set.
How full does RPTEST run?
Offline now for RPTEST, with the last sample 4 days 12 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server data
Which Rust version is RPTEST on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by RPTEST. Steam updates your game for you, but the protocol must match to join.
Is RPTEST up, and what does its uptime show?
RPTEST is offline at this refresh; the last response came 4 days 12 hours ago. 45 of 168 hours up over the last 7 full days, or 27%. The first row Rust Data holds for it is dated 2 October 2026.
Where does RPTEST sit?
For RPTEST, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 192.154.104.162:28016.
Map and rules
Which rules apply on RPTEST, and what settings?
No gather rate appears in the name: RPTEST. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Wipes and dates
When does RPTEST wipe, and how often?
No next wipe can be predicted for RPTEST, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 4 days 12 hours ago.
What is wipe day on RPTEST like?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Where does RPTEST appear among Rust Data lists and filters?
On Rust Data, RPTEST appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on RPTEST hold?
These tags are published by RPTEST and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): Slot count: 500; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (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.
Join steps
What is the way to join RPTEST?
Enter client.connect 192.154.104.162:28016 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.