RustServer_19396
Online 160.251.202.139:28015 checked 10m ago
Server instruments
last reading Thu 21:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 50 · below 20 is lag, below 10 is badEntities
48 h range 65,082–67,598 · memory 2,635 MBUptime
5 days 23 hours since its last restart, at the last readingPlayers
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 51% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot 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 2, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 05:08 UTC27d ago | 2 | – | running | 0 |
| Fri 18 Sep, 01:38 UTC41d ago | 1 | halved by day 8 | 14.1 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 140/250
- 173/250
- 535/675
- 29/100
- 619/775
- 523/625
Quick answers
from the figures on this pageWipe timing
What happens on RustServer_19396 when wipe day comes?
The busiest point of its recent wipes drew 2 players on average. After the latest wipe, numbers topped out at 0 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 8 it fell below half.
What wipe timing does RustServer_19396 follow?
Its rhythm cannot be told from the wipes of RustServer_19396 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. 27 days 18 hours ago the current world was made.
Tags
How should you read the tags on RustServer_19396?
Tags published by RustServer_19396, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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 RustServer_19396?
These Rust Metrics lists carry RustServer_19396: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
What position does RustServer_19396 hold among Rust servers?
Ranking for RustServer_19396: #11,458 on seven-day player hours, top 51% of all ranked servers.
What player count does RustServer_19396 carry?
Current headcount on RustServer_19396: 0 players, 20 slots available. Seven-day check: 0 players on average. Peak reading: 1. Average at the busiest hour was 0 players, at 09:00 UTC over the last 48 hours.
Operator and location
Which location does RustServer_19396 run from?
No region tag on RustServer_19396. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 160.251.202.139:28015.
What Rust version is RustServer_19396 on?
Rust network protocol 2635 and build 168909 on Linux is the build RustServer_19396 runs. To get in, your game needs the same protocol; Steam applies the update.
Is performance on RustServer_19396 within range?
Reading: 71 server fps on average across the last 48 hours. It never dropped below 50. Reading: 67,598 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 2,905 MB. Lag, as players feel it, is low fps plus a climbing entity count.
Is RustServer_19396 up, and how often does it stay up?
Check: connection. RustServer_19396 is online at this moment. Check: restart. The uptime it reports puts the last restart about 5 days 23 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
What rules does RustServer_19396 enforce, and what are its settings?
Reading the name gives no gather rate for RustServer_19396. 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. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is RustServer_19396 on?
Check: map. Procedural, size 3,550, seed 1495466692, generated by the game on RustServer_19396. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Connection
How do you connect to RustServer_19396?
To join: start Rust, press F1 and type client.connect 160.251.202.139:28015. Or press Launch Rust here and Steam opens the game and connects you.