RUST METRICSFlight deck · live data
Data live Servers11,848 Players93,384 Populated3,880 Fresh wipes 3 h381 Scan5 min
‹ All servers160.251.213.151:28015
Offline Full Queue Fresh wipe Wipe due No query

RustServer_670

Offline 160.251.213.151:28015 checked 4d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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#15,344top 69%
Last wipe26d 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, measured since 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct8 Oct13 Oct19 Oct24 Oct29 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

When does RustServer_670 wipe?

To tell the rhythm of RustServer_670, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 26 days 4 hours ago.

Tags

How should you read the tags on RustServer_670?

These are the tags RustServer_670 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does RustServer_670 appear in Rust Metrics lists and filters?

On Rust Metrics, RustServer_670 sits in these lists: 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.

Population

What position does RustServer_670 hold among Rust servers?

Ranking for RustServer_670: #15,344 on seven-day player hours, top 69% of all ranked servers.

How full does RustServer_670 get?

RustServer_670 is not responding; status offline, last seen 4 days 5 hours ago. Check: player average. 0 over the last seven days.

Server details

Where does RustServer_670 sit?

No region tag on RustServer_670. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 160.251.213.151:28015.

What Rust version is RustServer_670 on?

Version check: Rust network protocol 2634 and build 166652 on Linux, run by RustServer_670. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is RustServer_670, and is it online now?

RustServer_670 reports offline. The last reading came 4 days 5 hours ago. Reading: 49% uptime over the last 7 full days. It was up 83 of 168 hours. Check: first contact. Rust Metrics logged it on 3 October 2026.

Map and rules

How is RustServer_670 configured, and what rules are in force?

Reading the name gives no gather rate for RustServer_670. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is RustServer_670 on?

Size 3,000 and seed 30230: the game generates the procedural map on RustServer_670 from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

How can you get onto RustServer_670?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as 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.