RUST METRICSFlight deck · live data
Data live Servers11,803 Players71,182 Populated3,639 Fresh wipes 3 h205 Scan5 min
‹ All servers188.113.132.39:28015
Offline Full Queue Fresh wipe Wipe due No query

Toyohara2

Offline 188.113.132.39:28015 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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,959top 70%
Last wipe27d 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
15k10k15k20k1 Oct3 Oct4 Oct6 Oct7 Oct9 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 gap0.7 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 02:16 UTC27d ago 1 – running 0
Thu 1 Oct, 09:08 UTC28d ago 1 – 0.7 days 1

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 Toyohara2 when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

How often does Toyohara2 wipe, and when?

The rhythm of Toyohara2'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 27 days 11 hours ago.

Tags

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Toyohara2. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Toyohara2 appear in Rust Metrics lists and filters?

On Rust Metrics, Toyohara2 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.

Player count

Where does Toyohara2 sit in the rankings?

Ranking for Toyohara2: #15,959 on seven-day player hours, top 70% of all ranked servers.

What player count does Toyohara2 carry?

Reading for Toyohara2: offline at this moment; last seen 26 days 14 hours ago.

Server details

Which location does Toyohara2 run from?

Reading: location. Toyohara2 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 188.113.132.39:28015.

What Rust version is Toyohara2 on?

Reading: Toyohara2, Rust network protocol 2634 and build 166652, Windows. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. Toyohara2 is offline at this moment. Last contact was 26 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 1 October 2026, recorded by Rust Metrics.

Settings and map

What rules does Toyohara2 enforce, and what are its settings?

No gather rate appears in the name: Toyohara2. 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. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is Toyohara2 on?

Procedural map on Toyohara2, made by the game's generator.

How to join

How do you connect to Toyohara2?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166652
Build Game build reading: 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.