Offline 138.84.41.111:28015 checked 11d ago
MiServidorSoloTest
Connect
srv = rust.server("138.84.41.111: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 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 02:34 UTC12d ago | 1 | NaN | running | 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 138.84.41.111:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 02:57 UTC
- hostname
- –
- first seen
- 15 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 553 on average | 323/375 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 201/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 294 on average | 36/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 293 on average | 26/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 273 on average | 56/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 252 on average | 72/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does MiServidorSoloTest rank?
Over the last seven days MiServidorSoloTest sits at #14,662 on player hours, in the top 67% of ranked servers.
How many players does MiServidorSoloTest hold at once?
Offline now for MiServidorSoloTest, with the last sample 11 days 16 hours ago.
About the server
What Rust version does MiServidorSoloTest run?
Version Rust network protocol 2634 and build 167781 on Windows is reported by MiServidorSoloTest. The protocol has to match before you can join, and Steam does the updating.
How reliable is MiServidorSoloTest, and is it up?
The latest sample has MiServidorSoloTest offline, with a last sighting 11 days 16 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 15 October 2026.
Which location does MiServidorSoloTest run from?
There is no region published for MiServidorSoloTest. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 138.84.41.111:28015.
Settings and map
Which settings and rules does MiServidorSoloTest run?
No gather rate appears in the name: MiServidorSoloTest. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.
Which map has MiServidorSoloTest loaded?
MiServidorSoloTest runs a procedural map, which the game generates.
Wipes and dates
On what schedule does MiServidorSoloTest wipe?
A rhythm cannot be read from the wipes of MiServidorSoloTest on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 12 days 20 hours ago, and that is the one in play.
On MiServidorSoloTest, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in.
Tags and filters
Where does MiServidorSoloTest appear among Rust Data lists and filters?
The Rust Data lists that MiServidorSoloTest fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on MiServidorSoloTest?
These tags are published by MiServidorSoloTest and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): Slot count: 2; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. 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
How can I connect to MiServidorSoloTest?
Enter client.connect 138.84.41.111:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.