cocotomi
Offline 92.203.197.183:28015 checked 45d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 500/550
- 410/450
- 57/250
- 56/250
- 59/100
- 156/200
Quick answers
from the figures on this pageWipe schedule
How often does cocotomi wipe, and when?
The rhythm of cocotomi's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 46 days 2 hours ago the current world was made.
Tag meanings
How should you read the tags on cocotomi?
These are the tags cocotomi publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show cocotomi?
On Rust Metrics, cocotomi sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
What position does cocotomi hold among Rust servers?
Player hours over seven days put cocotomi at #15,049, in the top – of all ranked servers.
How full does cocotomi get?
Reading for cocotomi: offline at this moment; last seen 45 days ago.
Server details
Where does cocotomi sit?
Reading: location. cocotomi gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 92.203.197.183:28015.
What Rust version is cocotomi on?
Reading: cocotomi, Rust network protocol 2633 and build 163794, Windows. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on cocotomi, and is it online?
Check: connection. cocotomi is offline at this moment. Last contact was 45 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Rules and settings
What rules does cocotomi enforce, and what are its settings?
No gather rate appears in the name: cocotomi. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
Which map is live on cocotomi?
The game generates a procedural map for cocotomi.
Connection
How do you connect to cocotomi?
Press F1 in Rust and enter client.connect 92.203.197.183:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.