RUST METRICSFlight deck · live data
Data live Servers11,680 Players38,014 Populated2,926 Fresh wipes 3 h94 Scan5 min
‹ All servers94.75.213.107:28015
Offline Full Queue Fresh wipe Wipe due No query

WM3_SERVER

Offline 94.75.213.107:28015 checked 27d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 0 /3

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#16,013top 69%
Last wipe27d 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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

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 timing

What wipe timing does WM3_SERVER follow?

Its rhythm cannot be told from the wipes of WM3_SERVER on record: there are too few. 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 27 days 4 hours ago.

Tag meanings

How should you read the tags on WM3_SERVER?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): 3 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166494 (Build): Game build reading: 166494; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from WM3_SERVER. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does WM3_SERVER appear in Rust Metrics lists and filters?

On Rust Metrics, WM3_SERVER sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does WM3_SERVER sit in the rankings?

Player hours over seven days put WM3_SERVER at #16,013, in the top 69% of all ranked servers.

How full does WM3_SERVER get?

Reading for WM3_SERVER: offline at this moment; last seen 27 days 4 hours ago.

Operator and location

Which location does WM3_SERVER run from?

No region comes from WM3_SERVER. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 94.75.213.107:28015.

What Rust version is WM3_SERVER on?

Version check: Rust network protocol 2634 and build 166494 on Windows, run by WM3_SERVER. Matching protocol is required to join. Let Steam update your game.

How reliable is WM3_SERVER, and is it online now?

Reading: offline. WM3_SERVER last answered 27 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 1 October 2026.

Rules and settings

What settings and rules apply on WM3_SERVER?

Reading the name gives no gather rate for WM3_SERVER. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on WM3_SERVER?

The game generates a procedural map for WM3_SERVER.

How to join

How do you connect to WM3_SERVER?

To join: start Rust, press F1 and type client.connect 94.75.213.107:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp3,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp3
Max players 3 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166494
Build Game build reading: 166494.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

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.