Chernobyl
rust.chernobyl.in:28015
Status
—
—
Population
—
—
Server FPS
—
Target 30
Entities
—
—
Alerts
—
| Time | Severity | Type | Detail |
|---|---|---|---|
| Loading… | |||
Anti-cheat flags and network/DDoS anomalies — most recent 5, same feed as Administration → Cheating alerts.
Live console — RCON
● streaming
rcon>
Players
Online roster, live chat, kill feed, and kick/ban tools
Chat — Global, Team & Clan
rcon>
Kill feed
Online
Offline
| Player | Steam ID | Ping | Playtime | |
|---|---|---|---|---|
| Loading players… | ||||
Administration
Combat-log lookup and cheat alerts — all vanilla RCON, no framework
Cheating alerts
—
| Time | Severity | Player | Detail | Source | |
|---|---|---|---|---|---|
| Loading… | |||||
Flagged from Rust's own anti-cheat violation levels, EAC/AntiHack console lines, and a kill-rate heuristic. Rolling 7-day history.
Combat-log lookup
Combat log is only kept while a player is connected. Columns: time, attacker, target, weapon, ammo, area, distance, HP before/after, and the hit result.
| Enter a player and fetch their recent combat log. |
Raw output
Player Reports
In-game F7 reports — cheating, abuse, bugs, and feedback, with reporter/target Steam64 IDs. Persisted indefinitely, not on a rolling window.
All reports
—
| Time | Category | Reporter | Target | Message | |
|---|---|---|---|---|---|
| Loading… | |||||
Captured live from Rust's F7 report menu via the RCON console stream. Cheating/Abuse reports (which target a player) always reach here; Bug/General/Feedback reports need server.printreportstoconsole enabled, which it now is.
Player Metrics Config
Opt-out and alias controls for the public Survivor Metrics & Wipe Highlights pages. Stats are never deleted — only hidden or renamed at display time, and changes apply immediately, no restart needed.
Exclude list
Steam ID can't be searched on Survivor Metrics (looks exactly like an unrecorded player — no "private" signal) and is filtered out of every Wipe Highlights leaderboard entirely. Their stats stay in the database untouched; removing them from this list restores everything immediately.
| Steam ID | Name (at time added) | Added | Added by | |
|---|---|---|---|---|
| Loading… | ||||
Alias list
Steam ID shows under the chosen alias everywhere on Wipe Highlights (leaderboards, First Blood, kill streak). Survivor Metrics still shows their real name on a direct Steam ID search — the alias only masks the Wipe Highlights page.
| Steam ID | Real name (at time added) | Alias | Added | Added by | |
|---|---|---|---|---|---|
| Loading… | |||||
Logs & Metrics
Moderation history and server performance over time
Server FPS
Poll every
Population
CPU usage
System CPU is averaged across all cores and can look fine even when the game is struggling — Rust's tick loop is effectively single-threaded, so "RustDedicated busiest thread" (the single hottest thread under RustDedicated, as % of one core) is the number that actually predicts tick-rate trouble/rubberbanding.
RAM usage
Disk I/O
Network throughput
Moderation log — kicks & bans
| Date & time | Action | Player | Steam ID | Admin | Reason |
|---|---|---|---|---|---|
| Loading… | |||||
Server Controls
Lifecycle actions and scheduled automation
Lifecycle
Graceful restart
Warns players, restarts in 30s
Start
Start the server if it's stopped
Stop
Disconnects all players
Wipes
Map wipe
New seed, keeps blueprints
Force wipe
New map + blueprints reset
Schedules
| Label | When | Tasks | Last run | Status | |
|---|---|---|---|---|---|
| Loading… | |||||
Server Map
Current map, and candidates queued for the next wipe
Current map — live player positions
—
Loading map…
Scroll/pinch to zoom · drag to pan · dbl-click to reset
Dots update every ~1s from a live playerlist poll. Red = elevated anti-cheat violation level (matches the Administration tab's alerts).
Next-wipe candidates (max 3)
File Manager
Scoped to the Rust server's own directory — cfg, logs, saves, maps
| Name | Size | Modified | |
|---|---|---|---|
| Loading… | |||
—