Rust Data

rustdata.spaceservers201.108.80.58:28017.ipynb

Run all rust-data · live

‹ All servers

Online 201.108.80.58:28015 checked 6m ago

Rust en casa | MX X3 | 10 jugadores

3x moddedoxide

Connect

srv = rust.server("201.108.80.58:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 2
rank #6,110 # top 28%
last wipe 3d ago # no schedule published
next wipe – # no wipe seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75123:0008:0017:0001:0010:0020:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040023:0008:0017:0001:0010:0020:00

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, measured since 25 Oct. 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 best
RankRank in region
12k4k6k8k25 Oct26 Oct27 Oct28 Oct

Top 28% 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)
wipedpeakcrowdlastedplayers_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

2500 · seed 20261024
Map of Rust en casa | MX X3 | 10 jugadores
map
Procedural Map
size
2500
seed
20261024
Open on RustMaps

Server

srv.info()
address
201.108.80.58:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
25 Oct 2026, 00:23 UTC
hostname
–
first seen
25 Oct 2026

About this server · in its own words

print(srv.description)
Santa Rosalia B.C.S., Mexico. Recursos y botin x3. Hasta 10 jugadores. Botin de muerte: 2 horas; otros jugadores pueden saquearlo.

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Atlas - EU 3x | No BPs | MondaysEU · groups of 16+ · 3x · weekly · 387 on average377/450
1Vital Rust - EU Mondays | 3x | No BPsEU · groups of 14+ · 3x · weekly · 175 on average180/225
2HollowServers.co 3x Solo/Duo |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 124 on average403/405
3HollowServers.co 3x Solo/Duo/Trio |LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 121 on average92/100
4FLAME RUST #1 [ NOLIMIT | x3 | MAGIC ] WIPE 27.10groups of 30+ · 3x · weekly · 111 on average70/350
5AceRust.com 3x Solo/Duo|LootX3|JUST FULLWIPEDNA · groups of 8+ · 3x · biweekly · 105 on average66/100

Quick answers

From the figures on this page.

Population

What position does Rust en casa | MX X3 | 10 jugadores take in the server rankings?

Over the last seven days Rust en casa | MX X3 | 10 jugadores sits at #6,110 on player hours, in the top 28% of ranked servers.

How many players does Rust en casa | MX X3 | 10 jugadores hold at once?

Rust en casa | MX X3 | 10 jugadores reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 03:00 UTC is the busiest, at 1 players.

Server facts

How well does Rust en casa | MX X3 | 10 jugadores perform?

The 48-hour average is 180 server fps, with a low of 122. Buildings, deployables and all else in the world took the count as high as 31,177 entities. A high of 2,704 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on Rust en casa | MX X3 | 10 jugadores?

Rust network protocol 2635 and build 168909 on Windows is what Rust en casa | MX X3 | 10 jugadores runs. The protocol has to match before you can join, and Steam does the updating.

How reliable is Rust en casa | MX X3 | 10 jugadores, and is it up?

The current sample puts Rust en casa | MX X3 | 10 jugadores online. Count back 22 hours from its reported uptime to get the last restart. Uptime of 100% across the last 2 full days: 48 hours of 48. The first row Rust Data holds for it is dated 25 October 2026.

In which location is Rust en casa | MX X3 | 10 jugadores hosted?

There is no region published for Rust en casa | MX X3 | 10 jugadores. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 201.108.80.58:28015 is its address.

Settings and map

What rules and settings are recorded for Rust en casa | MX X3 | 10 jugadores?

3x gather is what the name states, and the name is Rust en casa | MX X3 | 10 jugadores. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.

What is the map on Rust en casa | MX X3 | 10 jugadores?

Size 2,500, seed 20261024: the procedural map on Rust en casa | MX X3 | 10 jugadores, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

On what schedule does Rust en casa | MX X3 | 10 jugadores wipe?

Too few wipes are on record for Rust en casa | MX X3 | 10 jugadores to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 3 days 21 hours ago.

Tags, lists

Which Rust Data filters and lists contain Rust en casa | MX X3 | 10 jugadores?

On Rust Data, Rust en casa | MX X3 | 10 jugadores appears in these lists: Modded Rust servers and 3x Rust servers, filtered live. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 3x.

How should you read the server tags on Rust en casa | MX X3 | 10 jugadores?

These tags are published by Rust en casa | MX X3 | 10 jugadores and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 Rust en casa | MX X3 | 10 jugadores?

In Rust, F1 opens the console: type client.connect 201.108.80.58:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players The server lists 10 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section lists it, because plugins or settings change the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Rust Data 62,070 players 11,772 servers online