RUST METRICSFlight deck · live data
Data live Servers11,841 Players73,926 Populated3,704 Fresh wipes 3 h221 Scan5 min
‹ All servers196.119.77.132:28025
Offline Full Queue Fresh wipe Wipe due No query

hamza2

Offline 196.119.77.132:28025 checked 22d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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,236top 64%
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 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, 4 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 6 Oct, 20:55 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 schedule

What happens on hamza2 when wipe day comes?

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

What wipe timing does hamza2 follow?

The rhythm of hamza2's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 22 days 13 hours ago the current world was made.

Tags

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

These are the tags hamza2 publishes, and the server browser reads them: gmvanilla (Game mode): Check: mode. Vanilla survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^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 hamza2 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring hamza2: 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

Where does hamza2 sit in the rankings?

Player hours over seven days put hamza2 at #14,236, in the top 64% of all ranked servers.

What player count does hamza2 carry?

Reading for hamza2: offline at this moment; last seen 22 days 12 hours ago.

Server details

Where does hamza2 sit?

No region comes from hamza2. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 196.119.77.132:28025.

What Rust version is hamza2 on?

Version check: Rust network protocol 2634 and build 166652 on Windows, run by hamza2. Matching protocol is required to join. Let Steam update your game.

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

hamza2 reports offline. The last reading came 22 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 6 October 2026.

Map and rules

What settings and rules apply on hamza2?

Reading the name gives no gather rate for hamza2. 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. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

What map is hamza2 on?

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

Connection

What do you do to join hamza2?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmvanilla,cs166652,ts8,^o^z

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

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.