RUST METRICSFlight deck · live data
Data live Servers11,626 Players39,326 Populated2,997 Fresh wipes 3 h100 Scan5 min
‹ All servers92.203.85.51:28015
Offline Full Queue Fresh wipe Wipe due No query

Iwamoto Local Solo

Offline 92.203.85.51:28015 checked 10d ago

COM 1 · connect

Server instruments

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

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#15,210top 70%
Last wipe15d 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
15k10k15k20k20 Sep27 Sep4 Oct10 Oct17 Oct24 Oct

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

usual gap19.4 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Tue 13 OctWed 23 Sep
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 13 Oct, 04:04 UTC15d ago 0 – running 0
Wed 23 Sep, 18:15 UTC34d ago 0 – 19.4 days 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

Reset cycle

What happens on Iwamoto Local Solo when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

How often does Iwamoto Local Solo wipe, and when?

Its rhythm cannot be told from the wipes of Iwamoto Local Solo 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. 15 days 3 hours ago the current world was made.

Tags

Which tags does Iwamoto Local Solo carry, and what do they mean?

Tags published by Iwamoto Local Solo, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): Build 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $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.

Which lists and filters on Rust Metrics show Iwamoto Local Solo?

Rust Metrics lists featuring Iwamoto Local Solo: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does Iwamoto Local Solo hold among Rust servers?

Ranking for Iwamoto Local Solo: #15,210 on seven-day player hours, top 70% of all ranked servers.

What player count does Iwamoto Local Solo carry?

Iwamoto Local Solo is not responding; status offline, last seen 10 days 14 hours ago.

Server

Which location does Iwamoto Local Solo run from?

No region tag on Iwamoto Local Solo. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 92.203.85.51:28015.

What Rust version is Iwamoto Local Solo on?

Version check: Rust network protocol 2634 and build 167584 on Linux, run by Iwamoto Local Solo. Matching protocol is required to join. Let Steam update your game.

How reliable is Iwamoto Local Solo, and is it online now?

Check: connection. Iwamoto Local Solo is offline at this moment. Last contact was 10 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does Iwamoto Local Solo enforce, and what are its settings?

Check: gather rate. The name Iwamoto Local Solo does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is Iwamoto Local Solo on?

Procedural map on Iwamoto Local Solo, made by the game's generator.

Connection

What do you do to join Iwamoto Local Solo?

Press F1 in Rust and enter client.connect 92.203.85.51: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 mp1,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167584
Build Build 167584.
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.