RUST METRICSFlight deck · live data
Data live Servers11,652 Players47,233 Populated3,140 Fresh wipes 3 h114 Scan5 min
‹ All servers185.53.90.32:36240
Offline Full Queue Fresh wipe Wipe due No query

ICE Map Forge local verification

Offline 185.53.90.32:36240 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,253top 69%
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 69% 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

Reset cycle

What wipe timing does ICE Map Forge local verification follow?

Its rhythm cannot be told from the wipes of ICE Map Forge local verification 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 in play was created 10 days 15 hours ago.

Tags

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): The game mode is plain Rust survival; mp0 (Max players): Slots: 0; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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.

Occupancy

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

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

What player count does ICE Map Forge local verification carry?

Status for ICE Map Forge local verification: offline. Last seen 10 days 15 hours ago.

Operator and location

Which location does ICE Map Forge local verification run from?

Reading: location. ICE Map Forge local verification gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 185.53.90.32:36240.

What Rust version is ICE Map Forge local verification on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by ICE Map Forge local verification. Matching protocol is required to join. Let Steam update your game.

How reliable is ICE Map Forge local verification, and is it online now?

Reading: offline. ICE Map Forge local verification last answered 10 days 15 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 18 October 2026.

Settings and map

What rules does ICE Map Forge local verification enforce, and what are its settings?

Check: gather rate. The name ICE Map Forge local verification 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: Community server. VAC is on. That is Valve's anti-cheat.

Connection

How do you connect to ICE Map Forge local verification?

Check: join. Open Rust, press F1, then enter client.connect 185.53.90.32:36240. 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 The game mode is plain Rust survival.
mp0
Max players Slots: 0.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.