Offline 90.68.182.100:28015 checked 20d ago
Mi Servidor PvE x10 con Bots
Connect
srv = rust.server("90.68.182.100: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 best
Top 62% 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 | Wed 7 Oct, 22:52 UTC20d ago | 1 | NaN | running | 0 |
# 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
- 90.68.182.100:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Oct 2026, 22:52 UTC
- hostname
- –
- first seen
- 7 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 | Atlas - EU 10x | No BPs | Kits | Shop | EU · groups of 20+ · 10x · weekly · 341 on average | 75/100 |
| 1 | TemplarGaming 10x Swift Loot++|PvP|MyMini|SkinBox|x10 JUST WIPE | NA · groups of 8+ · 10x · weekly · 177 on average | 269/350 |
| 2 | Atlas - US 10x | No BPs | Kits | Shop | NA · groups of 30+ · 10x · weekly · 175 on average | 226/250 |
| 3 | KRAKEN | X10 | EU | KITS | RP | FPS+ | EU · groups of 14+ · 10x · weekly · 149 on average | 15/400 |
| 4 | HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop] | EU · groups of 8+ · 10x · biweekly · 77 on average | 23/150 |
| 5 | HollowServers.co AU 10x No BPs [Loot++|Events|MyMini|Shop] | OC · groups of 8+ · 10x · biweekly · 70 on average | 52/150 |
Quick answers
From the figures on this page.
Population
How does Mi Servidor PvE x10 con Bots compare in the rankings?
Rank #13,707 on seven-day player hours for Mi Servidor PvE x10 con Bots, within the top 62% of all ranked servers.
What population does Mi Servidor PvE x10 con Bots carry?
Offline now for Mi Servidor PvE x10 con Bots, with the last sample 20 days 4 hours ago.
About the server
Which Rust version is Mi Servidor PvE x10 con Bots on?
Rust network protocol 2634 and build 167058 on Windows is what Mi Servidor PvE x10 con Bots runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Mi Servidor PvE x10 con Bots, and is it up?
Offline now for Mi Servidor PvE x10 con Bots, last seen 20 days 4 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 7 October 2026.
Where does Mi Servidor PvE x10 con Bots sit?
There is no region published for Mi Servidor PvE x10 con Bots. Rust Data does not look up where the machine stands; it shows where a server says it is. 90.68.182.100:28015 is its address.
Rules, settings, map
Which settings and rules does Mi Servidor PvE x10 con Bots run?
10x gather is what the name states, and the name is Mi Servidor PvE x10 con Bots. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has Mi Servidor PvE x10 con Bots selected?
The game generates its map: procedural, on Mi Servidor PvE x10 con Bots.
Wipe data
When does Mi Servidor PvE x10 con Bots wipe, and on what schedule?
Too few wipes are on record for Mi Servidor PvE x10 con Bots 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 20 days 4 hours ago.
What is wipe day on Mi Servidor PvE x10 con Bots like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 1 hours after it began.
Lists and tags
Which lists on Rust Data hold Mi Servidor PvE x10 con Bots, and which filters?
On Rust Data, Mi Servidor PvE x10 con Bots appears in these lists: Modded Rust servers and 10x Rust servers: the live sample. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 10x.
Which meanings do the tags on Mi Servidor PvE x10 con Bots hold?
These tags are published by Mi Servidor PvE x10 con Bots 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): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167058 (Build): Recorded game build: 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to Mi Servidor PvE x10 con Bots?
In Rust, F1 opens the console: type client.connect 90.68.182.100:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.