RustServer_25919
Online 160.251.169.111:28015 checked 10m ago
Server instruments
last reading Thu 20:00 UTCPlayers now
2% full 7-day avg7-day peakServer fps
48 h low 129 · below 20 is lag, below 10 is badEntities
48 h range 45,013–47,353 · memory 3,200 MBUptime
4 days 21 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 19 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 16% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. 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 3, 1 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 19 Oct, 14:18 UTC10d ago | 3 | – | running | 2 |
| Thu 8 Oct, 14:50 UTC21d ago | 3 | held half | 11 days | 0 |
| Sat 26 Sep, 03:42 UTC33d ago | 2 | halved by day 1 | 12.5 days | 1 |
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- 45/500
- 125/100
- 94/225
- 36/700
- 85/700
- 322/350
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on RustServer_25919?
An average of 3 players came at the busiest on its recent wipes. 1 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 50% of its recent wipes. By day 1 it fell below half when it didn't.
What wipe timing does RustServer_25919 follow?
There is no next wipe to predict: RustServer_25919 wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 10 days 7 hours ago.
Tag meanings
How should you read the tags on RustServer_25919?
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): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game from RustServer_25919. 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_25919?
Rust Metrics lists featuring RustServer_25919: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Population
What position does RustServer_25919 hold among Rust servers?
Ranking for RustServer_25919: #3,668 on seven-day player hours, top 16% of all ranked servers.
What player count does RustServer_25919 carry?
Current headcount on RustServer_25919: 1 players, 50 slots available. Seven-day check: 1 players on average. Peak reading: 4. The last 48 hours peaked at 14:00 UTC, averaging 2 players at that hour.
Server
Where does RustServer_25919 sit?
Reading: location. RustServer_25919 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 160.251.169.111:28015.
What Rust version is RustServer_25919 on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by RustServer_25919. Matching protocol is required to join. Let Steam update your game.
What is the performance reading for RustServer_25919?
Check: fps. Average 166 server fps over the last 48 hours, low of 129. Within range. Check: entities. The peak was 47,353, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 3,241 MB. Lag, as players feel it, is low fps plus a climbing entity count.
How reliable is RustServer_25919, and is it online now?
Reading: online. RustServer_25919 answers right now. Check: restart. The uptime it reports puts the last restart about 4 days 21 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 19 September 2026, recorded by Rust Metrics.
Settings and map
What rules does RustServer_25919 enforce, and what are its settings?
No gather rate appears in the name: RustServer_25919. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.
Which map is live on RustServer_25919?
Check: map. Procedural, size 3,000, seed 15754, generated by the game on RustServer_25919. The map repeats when size and seed match. Open it on RustMaps from this page.
Connection
What do you do to join RustServer_25919?
To join: start Rust, press F1 and type client.connect 160.251.169.111:28015. Or press Launch Rust here and Steam opens the game and connects you.