Rust Server TrendsSeismic network · station log
Recording Stations11,684 Players38,205 Active2,919 Wipes · 3 h95 48 h

Station XX-16013 · no signal

WM3_SERVER

Offline 94.75.213.107:28015 checked 27d ago

Connect
Players now
0/ 3
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,013
top 69%
Last wipe
27d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-16013 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 3 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 560 on average
168/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
121/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
17/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 288 on average
15/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
17/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 250 on average
25/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on WM3_SERVER?

WM3_SERVER uses a procedural map, which the game generates.

Which settings and rules apply on WM3_SERVER?

The name of WM3_SERVER gives no gather rate. At the game's default, groups can have up to 8 players. It plays in survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched off.

Population

What is the current population on WM3_SERVER?

WM3_SERVER is not responding at this moment and is offline, last seen 27 days 4 hours ago.

How does WM3_SERVER rank against other Rust servers?

Over the last seven days, WM3_SERVER recorded enough player hours to reach #16,013 worldwide, placing it in the top 69% of all ranked servers.

Server details

How reliably does WM3_SERVER stay online?

No contact with WM3_SERVER right now, and the last recorded contact was 27 days 4 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 1 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is WM3_SERVER hosted?

No region is published by WM3_SERVER. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 94.75.213.107:28015 is the address it uses.

What build of Rust does WM3_SERVER use?

WM3_SERVER is running Rust network protocol 2634 and build 166494 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

On what timetable does WM3_SERVER run its wipes?

On record so far are too few of WM3_SERVER's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 27 days 4 hours is how long the current world has been running.

Lists and tags

What do the server tags on WM3_SERVER mean?

These are the tags WM3_SERVER publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp3 (Max players): 3 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166494 (Build): It runs game build 166494; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does WM3_SERVER appear?

These Rust Server Trends lists include WM3_SERVER: Rust community servers without the side modes. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Connecting

What steps get you onto WM3_SERVER?

To join, enter client.connect 94.75.213.107:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp3
Max players 3 slots are available.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs166494
Build It runs game build 166494.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.