Offline 177.224.175.154:28015 checked 29d ago
Mi Servidor Solo x2
Connect
srv = rust.server("177.224.175.154: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 · 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 29 Sep, 17:52 UTC29d 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
- 177.224.175.154:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 29 Sep 2026, 17:52 UTC
- hostname
- –
- first seen
- 29 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 | Outpost Network #3 [ 2x Solo/Duo/Trio ] FULLWIPED 30.08 | groups of 8+ · 2x · 3 on average | 0/16 |
| 1 | Rustinity — EU | 2x Monthly | Vanilla+ | No BP Wipes | EU · groups of 8+ · 2x · 3 on average | 0/16 |
| 2 | [SEA] Lone Survivors - Medium | Solo | 2x Gather | 10/23 | EA · groups of 8+ · 2x · 3 on average | 1/60 |
| 3 | Small Brasil SOLO - 2X Quinzenal | SA · groups of 8+ · 2x · 2 on average | 0/100 |
| 4 | [LATAM] TIERRA DE NADIE 2X | SOLO/DUO | WIPE JUEVES | PVP | SA · groups of 8+ · 2x · weekly · 2 on average | 1/100 |
| 5 | [UA/EU]Ukraine x2 - Main | EU · groups of 8+ · 2x · weekly · 1 on average | 0/200 |
Quick answers
From the figures on this page.
Population data
What position does Mi Servidor Solo x2 take in the server rankings?
Player hours over seven days put Mi Servidor Solo x2 at #14,441, in the top 60% of the ranked set.
How many players does Mi Servidor Solo x2 hold at once?
The current row shows Mi Servidor Solo x2 offline; the last response was 29 days 21 hours ago.
About the server
What is the Rust version on Mi Servidor Solo x2?
Version Rust network protocol 2633 and build 163794 on Windows is reported by Mi Servidor Solo x2. The protocol has to match before you can join, and Steam does the updating.
Is Mi Servidor Solo x2 up, and what does its uptime show?
The latest sample has Mi Servidor Solo x2 offline, with a last sighting 29 days 21 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 29 September 2026.
Where does Mi Servidor Solo x2 sit?
For Mi Servidor Solo x2, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 177.224.175.154:28015 is its address.
Map and rules
Which settings and rules does Mi Servidor Solo x2 run?
Gather sits at 2x, read from the server's own name: Mi Servidor Solo x2. No custom cap; the default of 8 players per group stands. 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. VAC is running: Valve's anti-cheat is on.
Which map has Mi Servidor Solo x2 selected?
A procedural map runs on Mi Servidor Solo x2, generated by the game.
Wipe data
When does Mi Servidor Solo x2 wipe, and on what schedule?
Too few wipes are on record for Mi Servidor Solo x2 to reveal its rhythm. 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 29 days 23 hours ago.
On Mi Servidor Solo x2, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags, lists
Where does Mi Servidor Solo x2 appear among Rust Data lists and filters?
The Rust Data lists that Mi Servidor Solo x2 fits are: 2x Rust servers and 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; Gather rate: 2x.
Which meanings do the tags on Mi Servidor Solo x2 hold?
Read by the game's server browser, the tags Mi Servidor Solo x2 publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): 1 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): The server runs build 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set. 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 into Mi Servidor Solo x2?
Enter client.connect 177.224.175.154:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.