RUST METRICSFlight deck · live data
Data live Servers11,680 Players38,014 Populated2,926 Fresh wipes 3 h94 Scan5 min
‹ All servers185.53.90.38:34472
Offline Full Queue Fresh wipe Wipe due No query

ICE Map Forge local verification

Offline 185.53.90.38:34472 checked 10d ago

COM 1 · connect

Server instruments

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

Players now

no slots published 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,255top 70%
Last wipe10d 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
RankRank in region
15k10k15k20k18 Oct19 Oct21 Oct22 Oct24 Oct25 Oct

Top 70% 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 schedule

What wipe timing does ICE Map Forge local verification follow?

The rhythm of ICE Map Forge local verification's wipes cannot be told yet: too few 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 8 hours ago.

Tags

How should you read the tags on ICE Map Forge local verification?

Tags published by ICE Map Forge local verification, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp0 (Max players): The server holds 0 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does ICE Map Forge local verification appear in Rust Metrics lists and filters?

On Rust Metrics, ICE Map Forge local verification sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

Where does ICE Map Forge local verification sit in the rankings?

Ranking for ICE Map Forge local verification: #15,255 on seven-day player hours, top 70% of all ranked servers.

How full does ICE Map Forge local verification get?

ICE Map Forge local verification is not responding; status offline, last seen 10 days 8 hours ago.

Server

What location is ICE Map Forge local verification hosted in?

No region comes from ICE Map Forge local verification. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 185.53.90.38:34472.

What Rust version is ICE Map Forge local verification on?

Rust network protocol 2634 and build 167781 on Windows is the build ICE Map Forge local verification runs. Matching protocol is required to join. Let Steam update your game.

Is ICE Map Forge local verification up, and how often does it stay up?

Reading: offline. ICE Map Forge local verification last answered 10 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 18 October 2026.

Settings and map

What settings and rules apply on ICE Map Forge local verification?

No gather rate appears in the name: ICE Map Forge local verification. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

How to join

What do you do to join ICE Map Forge local verification?

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

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp0
Max players The server holds 0 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build The server runs game build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.