RUST METRICSFlight deck · live data
Data live Servers11,806 Players70,052 Populated3,612 Fresh wipes 3 h182 Scan5 min
‹ All servers185.53.90.32:38400
Offline Full Queue Fresh wipe Wipe due No query

ICE Map Forge local verification

Offline 185.53.90.32:38400 checked 11d 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,324top 70%
Last wipe11d 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 timing

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. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 11 days ago.

Lists and filters

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

These are the tags ICE Map Forge local verification publishes, and the server browser reads them: 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): Your game must run protocol 2634 to get in; cs167781 (Build): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

What position does ICE Map Forge local verification hold among Rust servers?

Player hours over seven days put ICE Map Forge local verification at #15,324, in the top 70% of all ranked servers.

How full does ICE Map Forge local verification get?

Reading for ICE Map Forge local verification: offline at this moment; last seen 11 days ago.

Server

Where does ICE Map Forge local verification sit?

No region tag on ICE Map Forge local verification. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 185.53.90.32:38400.

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?

Check: connection. ICE Map Forge local verification is offline at this moment. Last contact was 11 days 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 18 October 2026.

Map and rules

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

Reading the name gives no gather rate for ICE Map Forge local verification. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Join

How do you connect to ICE Map Forge local verification?

Check: join. Open Rust, press F1, then enter client.connect 185.53.90.32:38400. Alternatively, use Launch Rust on this page: Steam opens Rust 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 Your game must run protocol 2634 to get in.
cs167781
Build The server runs game build 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

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.