RustServer_22027
Online 160.251.136.57:28015 checked 8m ago
Server instruments
last reading Thu 03:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 76 · below 20 is lag, below 10 is badEntities
48 h range 44,486–123,258 · memory 3,715 MBUptime
12 h 20 min 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 5 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 44% 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 1, 1 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 28 Oct, 14:42 UTC14h ago | – | – | running | 0 |
| Tue 27 Oct, 22:56 UTC1d ago | – | – | – | 0 |
| Tue 27 Oct, 16:31 UTC1d ago | – | – | – | 0 |
| Wed 14 Oct, 14:25 UTC14d ago | 1 | halved by day 4 | 13.1 days | 0 |
| Tue 13 Oct, 17:15 UTC15d ago | 1 | – | 0.9 days | 0 |
| Thu 8 Oct, 00:37 UTC21d ago | 1 | halved by day 1 | 5.7 days | 0 |
| Tue 6 Oct, 04:18 UTC23d ago | 1 | – | 1.8 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- 38/500
- 126/100
- 62/225
- 14/700
- 2/200
- 3/1000
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on RustServer_22027?
An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 1 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. It fell below half by day 2.5 when it didn't.
When does RustServer_22027 wipe?
There is no next wipe to predict: RustServer_22027 wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 14 hours ago the current world was made.
Lists and filters
How should you read the tags on RustServer_22027?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp70 (Max players): The server holds 70 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game from RustServer_22027. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does RustServer_22027 appear in Rust Metrics lists and filters?
On Rust Metrics, RustServer_22027 sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
Occupancy
What position does RustServer_22027 hold among Rust servers?
Player hours over seven days put RustServer_22027 at #9,857, in the top 44% of all ranked servers.
How full does RustServer_22027 get?
Current headcount on RustServer_22027: 0 players, 70 slots available. Seven-day check: 0 players on average. Peak reading: 1. The last 48 hours peaked at 15:00 UTC, averaging 1 players at that hour.
Operator and location
What location is RustServer_22027 hosted in?
Reading: location. RustServer_22027 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 160.251.136.57:28015.
What Rust version is RustServer_22027 on?
Reading: RustServer_22027, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.
What is the performance reading for RustServer_22027?
Check: fps. Average 151 server fps over the last 48 hours, low of 76. Within range. Peak entity count: 123,258. Buildings, deployables and all else included. Check: memory. Peak use was 3,715 MB. Expect lag when fps falls and entities climb.
What is the uptime on RustServer_22027, and is it online?
Check: connection. RustServer_22027 is online at this moment. Check: restart. The uptime it reports puts the last restart about 12 hours ago. Uptime for the last 7 full days: 25 of 168 hours, or 15%. Reading: first seen 5 October 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on RustServer_22027?
Reading the name gives no gather rate for RustServer_22027. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
Which map is live on RustServer_22027?
Size 4,500 and seed 1337: the game generates the procedural map on RustServer_22027 from them. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: Custom Map.
Connection
What do you do to join RustServer_22027?
Press F1 in Rust and enter client.connect 160.251.136.57:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.