When players report lag, note the time and inspect server FPS. This measures server simulation performance, not frames rendered on a player's computer. A single low reading does not identify the cause.
Step 1Locate the slowdown
Step 2Compare graphs and errors
Step 3Test one hypothesis
Build a timeline
- Find the reported period in Rust Admin server statistics.
- Compare FPS with player counts and other available metrics.
- Look for repeated exceptions or plugin changes in the console at the same time.
- Test one suspected factor and compare again under similar player load.
Interpret the evidence
| Observation | Next check |
|---|---|
| FPS falls during peak hours | Workload and hosting resources |
| Drop follows an update | Updated plugin and console errors |
| Stable server FPS; isolated complaints | Player connection and client performance |
Use the panel to narrow the search
Rust Admin brings metrics and logs into the same workflow. It does not add CPU capacity or guarantee an FPS increase. Correlation still needs testing: avoid disabling every plugin at once, preserve the configuration and compare a controlled change during a quiet period.
See the workflow in Rust Admin
The interface demonstration below uses sample data to illustrate the section. These are not measurements from your server.
Connect your server to Rust Admin to collect statistics and investigate slowdowns over time. Sign in with Steam · View plans
