Offline 81.202.131.235:28015 checked 13d ago
Mi Servidor Solo
Connect
srv = rust.server("81.202.131.235:28016")
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 · 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 | Mon 12 Oct, 19:38 UTC15d ago | 1 | NaN | running | 0 |
| 1 | Mon 12 Oct, 13:25 UTC15d ago | 1 | NaN | 0.3 days | 1 |
| 2 | Fri 9 Oct, 21:04 UTC18d ago | 1 | held half | 2.7 days | 1 |
| 3 | Tue 6 Oct, 10:28 UTC21d ago | 1 | held half | 3.4 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 81.202.131.235:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 19:38 UTC
- hostname
- –
- first seen
- 4 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 · 534 on average | 268/300 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 322 on average | 21/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 321 on average | 16/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 167/200 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 277 on average | 87/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 264 on average | 22/100 |
Quick answers
From the figures on this page.
Population
How does Mi Servidor Solo compare in the rankings?
Over the last seven days Mi Servidor Solo sits at #12,972 on player hours, in the top 60% of ranked servers.
How full does Mi Servidor Solo run?
The current row shows Mi Servidor Solo offline; the last response was 13 days 16 hours ago.
Server data
What Rust version does Mi Servidor Solo run?
Version Rust network protocol 2634 and build 166652 on Windows is reported by Mi Servidor Solo. Steam updates your game for you, but the protocol must match to join.
How reliable is Mi Servidor Solo, and is it up?
Mi Servidor Solo is offline at this refresh; the last response came 13 days 16 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 4 October 2026.
Which location does Mi Servidor Solo run from?
No region is published by Mi Servidor Solo. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 81.202.131.235:28015.
Map and rules
What rules and settings are recorded for Mi Servidor Solo?
No gather rate appears in the name: Mi Servidor Solo. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.
Which map has Mi Servidor Solo selected?
The game generates its map: procedural, on Mi Servidor Solo.
Wipe data
When does Mi Servidor Solo wipe, and how often?
No next wipe can be predicted for Mi Servidor Solo, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 15 days 10 hours ago.
What is wipe day on Mi Servidor Solo like?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Lists and tags
Which lists on Rust Data hold Mi Servidor Solo, and which filters?
These Rust Data lists include Mi Servidor Solo: 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.
How should you read the server tags on Mi Servidor Solo?
These tags are published by Mi Servidor Solo 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): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way to join Mi Servidor Solo?
The manual route: launch Rust, F1, then client.connect 81.202.131.235:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.