RUST METRICSFlight deck · live data
Data live Servers11,692 Players37,024 Populated2,928 Fresh wipes 3 h87 Scan5 min
‹ All servers5.164.252.134:28015
Offline Full Queue Fresh wipe Wipe due No query

skin_test

Offline 5.164.252.134:28015 checked 24d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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#16,002top 71%
Last wipe24d 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
15k10k15k20k20 Sep24 Sep27 Sep4 Oct7 Oct11 Oct

Top 71% 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 peak0players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 09:19 UTC24d ago 0 – 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

Wipe timing

What should you expect from wipe day on skin_test?

At their busiest, its recent wipes drew 0 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe.

When does skin_test wipe?

Its rhythm cannot be told from the wipes of skin_test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 24 days 17 hours ago.

Tag meanings

How should you read the tags on skin_test?

These are the tags skin_test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): The server runs game build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does skin_test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry skin_test: 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.

Player count

What position does skin_test hold among Rust servers?

Ranking for skin_test: #16,002 on seven-day player hours, top 71% of all ranked servers.

How full does skin_test get?

skin_test is not responding; status offline, last seen 24 days 14 hours ago.

Server details

Which location does skin_test run from?

No region comes from skin_test. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 5.164.252.134:28015.

What Rust version is skin_test on?

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

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

Check: connection. skin_test is offline at this moment. Last contact was 24 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 20 September 2026.

Map and rules

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

Check: gather rate. The name skin_test does not state one. The group cap is 8 players, which is the default in the game. 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. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

What map is skin_test on?

Check: map. Procedural, generated by the game, on skin_test.

Join

What do you do to join skin_test?

Check: join. Open Rust, press F1, then enter client.connect 5.164.252.134:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players Slots: 100.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build The server runs game build 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Modded: plugins or settings depart from the stock 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.