RUST METRICSFlight deck · live data
Data live Servers11,699 Players51,000 Populated3,284 Fresh wipes 3 h143 Scan5 min
‹ All servers178.25.3.67:28015
Offline Full Queue Fresh wipe Wipe due No query

Weimar

Offline 178.25.3.67:28015 checked 10d ago

moddedoxide
COM 1 · connect

Server instruments

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

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#13,821top 64%
Last wipe10d 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
15k10k15k20k10 Oct13 Oct16 Oct18 Oct21 Oct24 Oct

Top 64% 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 16:48 UTC10d ago 1 – running 1

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

Reset cycle

What should you expect from wipe day on Weimar?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

When does Weimar wipe?

To tell the rhythm of Weimar, too few of its wipes are on record. 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 10 days 7 hours ago.

Tag meanings

How should you read the tags on Weimar?

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): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from Weimar. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Weimar?

Rust Metrics lists featuring Weimar: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

What position does Weimar hold among Rust servers?

Player hours over seven days put Weimar at #13,821, in the top 64% of all ranked servers.

What is the population on Weimar?

Status for Weimar: offline. Last seen 10 days 6 hours ago.

Server details

Which location does Weimar run from?

Reading: location. Weimar gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 178.25.3.67:28015.

What Rust version is Weimar on?

Reading: Weimar, Rust network protocol 2634 and build 167781, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is Weimar up, and how often does it stay up?

Reading: offline. Weimar last answered 10 days 6 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 10 October 2026.

Rules and settings

What rules does Weimar enforce, and what are its settings?

Check: gather rate. The name Weimar does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Connection

What do you do to join Weimar?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

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 Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.