RUST METRICSFlight deck · live data
Data live Servers11,849 Players73,470 Populated3,705 Fresh wipes 3 h219 Scan5 min
‹ All servers185.253.180.114:28015
Offline Full Queue Fresh wipe Wipe due No query

whyfry1zen

Offline 185.253.180.114:28015 checked 45d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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#14,559no region published
Last wipe45d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
No rank history yet.
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

How often does whyfry1zen wipe, and when?

Its rhythm cannot be told from the wipes of whyfry1zen 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 45 days 21 hours ago.

Lists and filters

Which tags does whyfry1zen carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp2 (Max players): Slots: 2; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game from whyfry1zen. 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 whyfry1zen?

These Rust Metrics lists carry whyfry1zen: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does whyfry1zen sit in the rankings?

Ranking for whyfry1zen: #14,559 on seven-day player hours, top – of all ranked servers.

How full does whyfry1zen get?

Reading for whyfry1zen: offline at this moment; last seen 45 days 18 hours ago.

Server details

Where does whyfry1zen sit?

No region tag on whyfry1zen. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 185.253.180.114:28015.

What Rust version is whyfry1zen on?

Reading: whyfry1zen, Rust network protocol 2633 and build 163794, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on whyfry1zen, and is it online?

Check: connection. whyfry1zen is offline at this moment. Last contact was 45 days 18 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 13 September 2026.

Map and rules

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

No gather rate appears in the name: whyfry1zen. 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. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on whyfry1zen?

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

Connection

How can you get onto whyfry1zen?

Press F1 in Rust and enter client.connect 185.253.180.114: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 mp2,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp2
Max players Slots: 2.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build Game build reading: 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (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.