RUST METRICSFlight deck · live data
Data live Servers11,614 Players34,171 Populated2,816 Fresh wipes 3 h69 Scan5 min
‹ All servers212.164.27.133:28015
Offline Full Queue Fresh wipe Wipe due No query

1v1v1v1 by motiega

Offline 212.164.27.133:28015 checked 22d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% 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#13,779top 62%
Last wipe22d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 Oct

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

PLAN

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 peak1players, 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 6 Oct, 13:58 UTC22d 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.

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 should you expect from wipe day on 1v1v1v1 by motiega?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 1 hours in.

When does 1v1v1v1 by motiega wipe?

Its rhythm cannot be told from the wipes of 1v1v1v1 by motiega on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 22 days 11 hours ago.

Tags

How should you read the tags on 1v1v1v1 by motiega?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): The server runs game build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from 1v1v1v1 by motiega. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does 1v1v1v1 by motiega appear in Rust Metrics lists and filters?

These Rust Metrics lists carry 1v1v1v1 by motiega: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does 1v1v1v1 by motiega sit in the rankings?

Player hours over seven days put 1v1v1v1 by motiega at #13,779, in the top 62% of all ranked servers.

What player count does 1v1v1v1 by motiega carry?

1v1v1v1 by motiega is not responding; status offline, last seen 22 days 10 hours ago.

Server

Where does 1v1v1v1 by motiega sit?

No region tag on 1v1v1v1 by motiega. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 212.164.27.133:28015.

What Rust version is 1v1v1v1 by motiega on?

Rust network protocol 2634 and build 166652 on Windows is the build 1v1v1v1 by motiega runs. Matching protocol is required to join. Let Steam update your game.

Is 1v1v1v1 by motiega up, and how often does it stay up?

1v1v1v1 by motiega reports offline. The last reading came 22 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 6 October 2026.

Rules and settings

How is 1v1v1v1 by motiega configured, and what rules are in force?

No gather rate appears in the name: 1v1v1v1 by motiega. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is 1v1v1v1 by motiega on?

The game generates a procedural map for 1v1v1v1 by motiega.

Join

How can you get onto 1v1v1v1 by motiega?

Press F1 in Rust and enter client.connect 212.164.27.133: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 mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build The server runs game build 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.