RUST METRICSFlight deck · live data
Data live Servers11,682 Players54,903 Populated3,147 Fresh wipes 3 h122 Scan5 min
‹ All servers176.119.111.113:28015
Offline Full Queue Fresh wipe Wipe due No query

Crowd Control Server

Offline 176.119.111.113:28015 checked 46d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#14,590no region published
Last wipe46d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
No rank history yet.
PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

How often does Crowd Control Server wipe, and when?

Its rhythm cannot be told from the wipes of Crowd Control Server on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 46 days 9 hours ago.

Lists and filters

How should you read the tags on Crowd Control Server?

Tags published by Crowd Control Server, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Crowd Control Server appear in Rust Metrics lists and filters?

On Rust Metrics, Crowd Control Server sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Crowd Control Server hold among Rust servers?

Ranking for Crowd Control Server: #14,590 on seven-day player hours, top – of all ranked servers.

What player count does Crowd Control Server carry?

Reading for Crowd Control Server: offline at this moment; last seen 46 days 9 hours ago.

Operator and location

Where does Crowd Control Server sit?

No region comes from Crowd Control Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 176.119.111.113:28015.

What Rust version is Crowd Control Server on?

Reading: Crowd Control Server, Rust network protocol 2633 and build 163794, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is Crowd Control Server up, and how often does it stay up?

Crowd Control Server reports offline. The last reading came 46 days 9 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

What rules does Crowd Control Server enforce, and what are its settings?

Reading the name gives no gather rate for Crowd Control Server. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

How to join

How do you connect to Crowd Control Server?

Check: join. Open Rust, press F1, then enter client.connect 176.119.111.113:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build The server runs game build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.