RUST METRICSFlight deck · live data
Data live Servers11,695 Players39,471 Populated2,990 Fresh wipes 3 h89 Scan5 min
‹ All servers185.77.218.218:28015
Offline Full Queue Fresh wipe Wipe due No query

memzserver

Offline 185.77.218.218:28015 checked 43d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 0 /15

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,416no region published
Last wipe43d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep
PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What wipe timing does memzserver follow?

Its rhythm cannot be told from the wipes of memzserver on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 43 days 15 hours ago.

Tag meanings

Which tags does memzserver carry, and what do they mean?

Tags published by memzserver, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp15 (Max players): 15 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show memzserver?

On Rust Metrics, memzserver 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.

Population

Where does memzserver sit in the rankings?

Player hours over seven days put memzserver at #15,416, in the top – of all ranked servers.

How full does memzserver get?

Reading for memzserver: offline at this moment; last seen 43 days 12 hours ago.

Operator and location

What location is memzserver hosted in?

No region comes from memzserver. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 185.77.218.218:28015.

What Rust version is memzserver on?

Rust network protocol 2633 and build 163794 on Windows is the build memzserver runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on memzserver, and is it online?

Check: connection. memzserver is offline at this moment. Last contact was 43 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 15 September 2026.

Map and rules

How is memzserver configured, and what rules are in force?

Check: gather rate. The name memzserver does not state one. 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. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on memzserver?

Check: map. Procedural, generated by the game, on memzserver.

How to join

What do you do to join memzserver?

Press F1 in Rust and enter client.connect 185.77.218.218:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp15,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp15
Max players 15 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build The server runs game build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.