RUST METRICSFlight deck · live data
Data live Servers11,726 Players49,195 Populated3,240 Fresh wipes 3 h114 Scan5 min
‹ All servers130.61.136.113:28015
Offline Full Queue Fresh wipe Wipe due No query

Furka Rust (ARM test)

Offline 130.61.136.113:28015 checked 10d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,253top 69%
Last wipe13d 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
15k10k15k20k15 Oct17 Oct19 Oct21 Oct23 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 Furka Rust (ARM test) follow?

To tell the rhythm of Furka Rust (ARM test), too few of its wipes 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 13 days 7 hours ago.

Lists and filters

Which tags does Furka Rust (ARM test) carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from Furka Rust (ARM test). Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Furka Rust (ARM test)?

Rust Metrics lists featuring Furka Rust (ARM test): 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.

Player count

What position does Furka Rust (ARM test) hold among Rust servers?

Ranking for Furka Rust (ARM test): #15,253 on seven-day player hours, top 69% of all ranked servers.

What is the population on Furka Rust (ARM test)?

Status for Furka Rust (ARM test): offline. Last seen 10 days 6 hours ago.

Server

What location is Furka Rust (ARM test) hosted in?

No region comes from Furka Rust (ARM test). Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 130.61.136.113:28015.

What Rust version is Furka Rust (ARM test) on?

Reading: Furka Rust (ARM test), Rust network protocol 2634 and build 167781, Linux. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Furka Rust (ARM test), and is it online?

Reading: offline. Furka Rust (ARM test) last answered 10 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 October 2026, recorded by Rust Metrics.

Map and rules

How is Furka Rust (ARM test) configured, and what rules are in force?

Reading the name gives no gather rate for Furka Rust (ARM test). No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Furka Rust (ARM test)?

Procedural map on Furka Rust (ARM test), made by the game's generator.

Join

How do you connect to Furka Rust (ARM test)?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 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.