RustServer_11987
Online 160.251.253.229:28015 checked 8m ago
Server instruments
last reading Thu 21:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 97 · below 20 is lag, below 10 is badEntities
48 h range 41,592–44,225 · memory 1,584 MBUptime
2 days 8 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 66% 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, 16 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 14:25 UTC27d ago | 2 | – | running | 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- 143/250
- 182/250
- 553/675
- 30/100
- 623/775
- 533/625
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on RustServer_11987?
An average of 2 players came at the busiest on its recent wipes. 16 hours after the wipe, the crowd peaked on the latest wipe.
What wipe timing does RustServer_11987 follow?
Its rhythm cannot be told from the wipes of RustServer_11987 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 27 days 8 hours ago.
Tag meanings
How should you read the tags on RustServer_11987?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from RustServer_11987. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does RustServer_11987 appear in Rust Metrics lists and filters?
On Rust Metrics, RustServer_11987 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 RustServer_11987 hold among Rust servers?
Ranking for RustServer_11987: #14,809 on seven-day player hours, top 66% of all ranked servers.
How full does RustServer_11987 get?
Current headcount on RustServer_11987: 0 players, 50 slots available. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 14:00 UTC, 0 players on average.
Server
Which location does RustServer_11987 run from?
Reading: location. RustServer_11987 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 160.251.253.229:28015.
What Rust version is RustServer_11987 on?
Reading: RustServer_11987, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.
What is the performance reading for RustServer_11987?
Reading: 128 server fps on average across the last 48 hours. It never dropped below 97. Check: entities. The peak was 44,225, counting buildings, deployables and the rest of the world. Memory peak: 1,820 MB. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on RustServer_11987, and is it online?
Check: connection. RustServer_11987 is online at this moment. Check: restart. The uptime it reports puts the last restart about 2 days 8 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Rules and settings
How is RustServer_11987 configured, and what rules are in force?
Check: gather rate. The name RustServer_11987 does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on RustServer_11987?
Check: map. Procedural, size 3,000, seed 28916, generated by the game on RustServer_11987. The map repeats when size and seed match. Open it on RustMaps from this page.
Join
How do you connect to RustServer_11987?
Press F1 in Rust and enter client.connect 160.251.253.229:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.