RustServer_21050
Online 160.251.173.186:28015 checked 12m ago
Server instruments
last reading Fri 05:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 48 · below 20 is lag, below 10 is badEntities
48 h range 67,615–71,458 · memory 4,107 MBUptime
6 days 7 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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 25% 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 3, 41 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 15:12 UTC27d ago | 3 | – | running | 0 |
| Fri 25 Sep, 16:05 UTC34d ago | 1 | halved by day 1 | 7 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- 37/500
- 135/100
- 69/225
- 20/700
- 60/700
- 52/200
Quick answers
from the figures on this pageReset cycle
What happens on RustServer_21050 when wipe day comes?
An average of 2 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 41 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 1 it fell below half.
When does RustServer_21050 wipe?
The rhythm of RustServer_21050's wipes cannot be told yet: too few are on record. 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 15 hours ago.
Lists and filters
How should you read the tags on RustServer_21050?
Tags published by RustServer_21050, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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_21050?
These Rust Metrics lists carry RustServer_21050: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
What position does RustServer_21050 hold among Rust servers?
Ranking for RustServer_21050: #5,622 on seven-day player hours, top 25% of all ranked servers.
How full does RustServer_21050 get?
0 of 50 slots are filled on RustServer_21050 right now. Seven-day check: 0 players on average. Peak reading: 3. The last 48 hours peaked at 12:00 UTC, averaging 1 players at that hour.
Server details
What location is RustServer_21050 hosted in?
No region tag on RustServer_21050. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 160.251.173.186:28015.
What Rust version is RustServer_21050 on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by RustServer_21050. Matching protocol is required to join. Let Steam update your game.
Is performance on RustServer_21050 within range?
Check: fps. Average 72 server fps over the last 48 hours, low of 48. Within range. Reading: 71,458 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 4,161 MB. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on RustServer_21050, and is it online?
Reading: online. RustServer_21050 answers right now. By its reported uptime, the last restart was roughly 6 days 7 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 24 September 2026, recorded by Rust Metrics.
Settings and map
What settings and rules apply on RustServer_21050?
Reading the name gives no gather rate for RustServer_21050. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is RustServer_21050 on?
Size 3,500 and seed 12830: the game generates the procedural map on RustServer_21050 from them. View it on RustMaps from this page: matching size and seed give an identical map.
Join
How can you get onto RustServer_21050?
Check: join. Open Rust, press F1, then enter client.connect 160.251.173.186:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.