mortal.wish
Online NA 107.174.232.22:28015 checked 10m ago
Server instruments
last reading Wed 04:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 150 · below 20 is lag, below 10 is badEntities
48 h range 46,739–49,124 · memory 2,721 MBUptime
7 days 22 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 69% of all ranked servers, top 82% in NA. 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 1, 27 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 02:04 UTC26d ago | 1 | – | 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- 33/250
- 35/250
- 433/525
- 13/100
- 313/375
- 32/200
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on mortal.wish?
The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 27 hours.
When does mortal.wish wipe?
The rhythm of mortal.wish's wipes cannot be told yet: too few are on record. 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 in play was created 26 days 4 hours ago.
Tag meanings
How should you read the tags on mortal.wish?
Tags published by mortal.wish, read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^y (Carbon): Check: framework. Carbon; ^q (Premium): Check: access. Premium players only; NA (North America): The server browser files it under North America. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does mortal.wish appear in Rust Metrics lists and filters?
Rust Metrics lists featuring mortal.wish: Rust community servers: live readings, North America: server readout and Vanilla Rust servers, live. Reading: server list filters. It comes up under Region: North America; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Game mode: Premium; Server tag: Vanilla ^v, Premium ^q and Carbon ^y; Group limit: 5 or more.
Player count
What position does mortal.wish hold among Rust servers?
Top 69% of all ranked servers: mortal.wish takes #15,419 on seven-day player hours and #1,540 in North America.
What player count does mortal.wish carry?
Current headcount on mortal.wish: 0 players, 50 slots available. Check: player average. 0 over the last seven days.
Server details
Which location does mortal.wish run from?
Its NA tag places mortal.wish in North America. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 107.174.232.22:28015.
What Rust version is mortal.wish on?
Rust network protocol 2634 and build 167781 on Linux is the build mortal.wish runs. Check: protocol. To join, your game must match; Steam handles the update.
What is the performance reading for mortal.wish?
Check: fps. Average 200 server fps over the last 48 hours, low of 150. Within range. Check: entities. The peak was 49,124, counting buildings, deployables and the rest of the world. Reading: 3,198 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.
How reliable is mortal.wish, and is it online now?
Reading: online. mortal.wish answers right now. By its reported uptime, the last restart was roughly 7 days 22 hours ago. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Rules and settings
What rules does mortal.wish enforce, and what are its settings?
No gather rate appears in the name: mortal.wish. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Carbon plugins are running. Vanilla is the label it uses: the stock game: Facepunch's rates, kits and rules, unchanged. Check: access. Premium players only. VAC is on. That is Valve's anti-cheat.
What map is mortal.wish on?
Size 3,000 and seed 2024: the game generates the procedural map on mortal.wish from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Connection
How do you connect to mortal.wish?
Press F1 in Rust and enter client.connect 107.174.232.22:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. Check: access. Premium players only. https://mortalwish.net/ is where its website sits.