RustServer_22027
Online 160.251.136.57:28015 checked 9m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 44% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 28 Oct, 14:42 UTC11h 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 UTC22d 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on RustServer_22027?
The average peak across its recent wipes is 1 players. 1 hours into the latest wipe, player numbers topped out. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. By day 2.5 it was below half in the wipes that did not hold.
What is the wipe schedule on RustServer_22027?
No next wipe can be predicted: RustServer_22027 wipes when it chooses, at irregular times. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. 11 hours ago the server made the world it is on now.
Population
How busy is RustServer_22027?
RustServer_22027 currently has 0 of its 70 slots filled. A seven-day average of 0 players, with a peak of 1. Look at 15:00 UTC for the last 48 hours: that hour averaged 1 players.
How does RustServer_22027 rank against other Rust servers?
The top 44% of ranked servers includes RustServer_22027, at #9,857 for player hours over the last seven days.
Settings and rules
Which map does RustServer_22027 run?
The map on RustServer_22027 is procedural, size 4,500 with seed 1337, generated by the game. The map is the same for a given size and seed, so RustMaps can show it from this page. The name of the map is: Custom Map.
What are the rules and settings on RustServer_22027?
A gather rate is not given in the name RustServer_22027. 8 players is the default group size, and that is the limit here. survival is the game mode, gather, build and raid in the standard game. Combat between players and raiding are both possible. In the server browser it is Modded, meaning plugins or settings modify the game. Oxide plugins run on this server. VAC is on, which is Valve's anti-cheat.
Server details
Which version of Rust does RustServer_22027 run?
Rust network protocol 2635 and build 168909 on Linux is what RustServer_22027 runs. Steam updates your game for you, and the protocol has to match for you to join.
Is RustServer_22027 online, and how reliable is it?
The server is up at the moment: RustServer_22027 is online. About 9 hours ago is when it last restarted, by its own uptime figure. 25 of 168 hours up over the last 7 full days, which is 15%. Rust Heatmap has had it on record since 5 October 2026.
Where is RustServer_22027 located?
A region is not published for RustServer_22027. Rust Heatmap shows the location a server states. It does not look up the machine's location. You can reach it at 160.251.136.57:28015.
Does RustServer_22027 run smoothly?
It averaged 160 server fps over the last 48 hours, with a low of 76. Buildings, deployables and the rest of the world came to as much as 122,892 entities. Memory use reached 3,446 MB at most. Players feel lag when fps falls and the entity count climbs.
Lists and filters
Which Rust Heatmap lists and filters include RustServer_22027?
The Rust Heatmap lists that RustServer_22027 fits are: Modded Rust servers, by live population. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
What do the server tags on RustServer_22027 mean?
The game's server browser reads the tags RustServer_22027 publishes: gmrust (Game mode): Survival in the standard Rust form; mp70 (Max players): The slot count is 70; ts8 (Group limit): At most 8 per team: the default the game ships with; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): This build is 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): The region code is blank; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Settings or plugins alter the game, which puts it under Modded. Also in the tags, shown at the top of this page: players now, the queue and the time the world was made.
Connect
How do I join RustServer_22027?
To join by console, open it with F1 in Rust and enter client.connect 160.251.136.57:28015. Or press Launch Rust on this page, which connects you through Steam.