Rust Server TrendsSeismic network · station log
Recording Stations11,879 Players98,401 Active3,904 Wipes · 3 h400 48 h

Station XX-15379 · no signal

1v1v1v1 by motiega

Offline 212.164.27.211:28015 checked 35d ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,379
top 71%
Last wipe
36d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15379 · 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 10 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
15k10k15k20k23 Sep24 Sep26 Sep27 Sep29 Sep30 Sep

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

Expected events

Wipe schedule

too few wipes seen yet

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

wipe-day peak
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 23 Sep, 11:24 UTC36d ago M0.0steady 1 – running 1

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
ShockRust | Blue | NoLimit no group limit · 150 on average
154/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
131/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average
183/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 94 on average
98/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 87 on average
239/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 84 on average
348/ 350
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on 1v1v1v1 by motiega?

1v1v1v1 by motiega uses a procedural map, which the game generates.

Which settings and rules apply on 1v1v1v1 by motiega?

No gather rate appears in the name of 1v1v1v1 by motiega. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on 1v1v1v1 by motiega?

No players are recorded on 1v1v1v1 by motiega at this moment; it is offline, and the last sighting was 35 days 23 hours ago.

How does 1v1v1v1 by motiega rank against other Rust servers?

The last seven days of player hours place 1v1v1v1 by motiega at #15,379, in the top 71% of all ranked servers.

Operator and location

How reliably does 1v1v1v1 by motiega stay online?

No contact with 1v1v1v1 by motiega right now, and the last recorded contact was 35 days 23 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 23 September 2026.

Which region does 1v1v1v1 by motiega run from?

No region is published by 1v1v1v1 by motiega. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 212.164.27.211:28015.

What build of Rust does 1v1v1v1 by motiega use?

1v1v1v1 by motiega is running Rust network protocol 2633 and build 165217 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on 1v1v1v1 by motiega?

1 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.

How often does 1v1v1v1 by motiega wipe, and on which days?

The rhythm of 1v1v1v1 by motiega cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 36 days 5 hours.

Server tags

What do the server tags on 1v1v1v1 by motiega mean?

Tags published by 1v1v1v1 by motiega and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): Game build: 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does 1v1v1v1 by motiega appear?

The Rust Server Trends lists that take in 1v1v1v1 by motiega are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Join the server

How do you connect to 1v1v1v1 by motiega?

To join, enter client.connect 212.164.27.211: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 mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode You'll find standard Rust survival here.
mp10
Max players The server has 10 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol To connect, your game must be on the same protocol, 2633.
cs165217
Build Game build: 165217.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

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.