Offline 187.36.154.128:28015 checked 15d ago
TESTE_HOST
Connect
srv = rust.server("187.36.154.128:28026")
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 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 187.36.154.128:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 05:02 UTC
- hostname
- –
- first seen
- 13 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 · 150 on average | 72/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 100/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 35/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 7/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TESTE_HOST rank?
Player hours over seven days put TESTE_HOST at #13,060, in the top 60% of the ranked set.
How full does TESTE_HOST run?
TESTE_HOST returns no live count at this refresh, having last been seen 15 days 7 hours ago.
About the server
Which Rust version is TESTE_HOST on?
The build is Rust network protocol 2634 and build 167398 on Windows, run by TESTE_HOST. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TESTE_HOST, and is it online now?
The latest sample has TESTE_HOST offline, with a last sighting 15 days 7 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 13 October 2026.
In which location is TESTE_HOST hosted?
For TESTE_HOST, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 187.36.154.128:28015 is its address.
Map and rules
Which rules apply on TESTE_HOST, and what settings?
No gather rate appears in the name: TESTE_HOST. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has TESTE_HOST selected?
TESTE_HOST runs a procedural map, which the game generates.
Wipe data
When does TESTE_HOST wipe, and how often?
The record for TESTE_HOST holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 18 days 2 hours ago, and that is the one in play.
Tags and filters
Where does TESTE_HOST appear among Rust Data lists and filters?
On Rust Data, TESTE_HOST appears in these lists: 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.
How should you read the server tags on TESTE_HOST?
Read by the game's server browser, the tags TESTE_HOST publishes are: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; 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): The region field is empty; ^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.
How to join
What is the way into TESTE_HOST?
In Rust, F1 opens the console: type client.connect 187.36.154.128:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.