Offline 85.190.160.130:11300 checked 23d ago
CO - LA | PARTY
Connect
srv = rust.server("85.190.160.130:11301")
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, measured since 28 Sep. 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 71% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 17:59 UTC FW28d ago | 0 | NaN | running | 0 |
| 1 | Mon 28 Sep, 09:06 UTC31d ago | 2 | held half | 3.4 days | 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
3750 · seed 2109729187
- map
- Procedural Map
- size
- 3750
- seed
- 2109729187
Server
srv.info()- address
- 85.190.160.130:11300
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:59 UTC
- hostname
- –
- first seen
- 28 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 | 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.
Player counts
Against other Rust servers, how does CO - LA | PARTY rank?
Rank #15,984 on seven-day player hours for CO - LA | PARTY, within the top 71% of all ranked servers.
How many players does CO - LA | PARTY hold at once?
The current row shows CO - LA | PARTY offline; the last response was 23 days 2 hours ago.
Server data
What is the Rust version on CO - LA | PARTY?
The build is Rust network protocol 2634 and build 166652 on Windows, run by CO - LA | PARTY. The protocol has to match before you can join, and Steam does the updating.
How reliable is CO - LA | PARTY, and is it up?
Offline now for CO - LA | PARTY, last seen 23 days 2 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 28 September 2026.
Which location does CO - LA | PARTY run from?
There is no region published for CO - LA | PARTY. 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 85.190.160.130:11300.
Map and rules
What rules and settings are recorded for CO - LA | PARTY?
The name CO - LA | PARTY carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, 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. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has CO - LA | PARTY loaded?
Size 3,750, seed 2109729187: the procedural map on CO - LA | PARTY, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does CO - LA | PARTY wipe, and on what schedule?
The record for CO - LA | PARTY holds too few wipes to show a 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 28 days ago.
What is wipe day on CO - LA | PARTY like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Lists and tags
Which lists on Rust Data hold CO - LA | PARTY, and which filters?
The Rust Data lists that CO - LA | PARTY fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on CO - LA | PARTY hold?
The game's server browser reads these tags from CO - LA | PARTY: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; 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): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 CO - LA | PARTY?
In Rust, F1 opens the console: type client.connect 85.190.160.130:11300. Launch Rust on this page does the same by opening the game through Steam and connecting.
