Offline 219.248.160.167:28515 checked 27d ago
mococo test
Connect
srv = rust.server("219.248.160.167:28516")
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 69% 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)| wiped | peak | crowd | lasted | players_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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 219.248.160.167:28515
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 23:21 UTC
- hostname
- –
- first seen
- 1 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 126/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 197/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 77/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 226/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 349/350 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does mococo test rank?
Over the last seven days mococo test sits at #16,006 on player hours, in the top 69% of ranked servers.
What population does mococo test carry?
mococo test returns no live count at this refresh, having last been seen 27 days 19 hours ago.
About the server
What is the Rust version on mococo test?
Rust network protocol 2634 and build 166494 on Windows is what mococo test runs. Joining needs the same protocol on your game; Steam handles the update.
Is mococo test up, and what does its uptime show?
mococo test is offline at this refresh; the last response came 27 days 19 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 1 October 2026.
In which location is mococo test hosted?
There is no region published for mococo test. 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 219.248.160.167:28515.
Map and rules
What rules and settings are recorded for mococo test?
The name mococo test carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has mococo test loaded?
A procedural map runs on mococo test, generated by the game.
Wipe schedule
On what schedule does mococo test wipe?
Too few wipes are on record for mococo test 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. The world it runs now was generated 27 days 19 hours ago.
Tags and filters
Which lists on Rust Data hold mococo test, and which filters?
On Rust Data, mococo test appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on mococo test?
The game's server browser reads these tags from mococo test: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): The server runs build 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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 mococo test?
In Rust, F1 opens the console: type client.connect 219.248.160.167:28515. Launch Rust on this page does the same by opening the game through Steam and connecting.