Offline 160.238.154.229:28015 checked 12d ago
TESTE
Connect
srv = rust.server("160.238.154.229: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 70% 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 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 17 Oct, 00:03 UTC12d ago | 2 | NaN | running | 0 |
| 1 | Mon 12 Oct, 20:58 UTC16d ago | 1 | held half | 4.1 days | 0 |
| 2 | Mon 12 Oct, 03:21 UTC17d ago | 1 | NaN | 0.7 days | 1 |
| 3 | Fri 2 Oct, 09:07 UTC27d ago | 2 | held half | 9.8 days | 0 |
| 4 | Thu 1 Oct, 23:38 UTC FW27d ago | 2 | NaN | 0.4 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 WIPED 10 HOURS AGO
- size
- –
- seed
- –
Server
srv.info()- address
- 160.238.154.229:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Oct 2026, 00:03 UTC
- hostname
- –
- first seen
- 30 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 · 149 on average | 154/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 72/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 11/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 23/1000 |
Quick answers
From the figures on this page.
Population data
How does TESTE compare in the rankings?
Over the last seven days TESTE sits at #15,193 on player hours, in the top 70% of ranked servers.
What population does TESTE carry?
TESTE returns no live count at this refresh, having last been seen 12 days 1 hours ago.
About the server
What is the Rust version on TESTE?
Version Rust network protocol 2634 and build 167781 on Windows is reported by TESTE. Joining needs the same protocol on your game; Steam handles the update.
Is TESTE up, and what does its uptime show?
TESTE is offline at this refresh; the last response came 12 days 1 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 30 September 2026.
Which location does TESTE run from?
No region is published by TESTE. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 160.238.154.229:28015.
Map and rules
Which settings and rules does TESTE run?
No gather rate appears in the name: TESTE. The group limit sits at the default of 8 players. 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 Oxide. VAC, Valve's anti-cheat, is enabled.
Wipe schedule
On what schedule does TESTE wipe?
Irregular wipe times on TESTE leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 12 days 11 hours ago.
What is wipe day on TESTE like?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags and filters
Which lists on Rust Data hold TESTE, and which filters?
These Rust Data lists include TESTE: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on TESTE?
Read by the game's server browser, the tags TESTE publishes are: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join TESTE?
Enter client.connect 160.238.154.229:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.