Furka Rust (ARM test)
Online 130.61.136.113:28015 checked 17m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 64% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 277/ 300
- 589/ 600
- 474/ 500
- 136/ 200
- 479/ 525
- 215/ 250
Quick answers
Tags and filters
Where does Furka Rust (ARM test) appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Furka Rust (ARM test): Rust community servers, going deep. The server list shows it under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
What's the meaning of the tags on Furka Rust (ARM test)?
gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): It holds 10 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs167781 (Build): The build number is 167781; ptrak (Networking): Standard RakNet networking; $r? (Region code): The region field is empty — that is the tag list Furka Rust (ARM test) puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
Where can you find Furka Rust (ARM test)?
There is no published region for Furka Rust (ARM test). Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 130.61.136.113:28015.
What's the uptime like for Furka Rust (ARM test)?
Right now Furka Rust (ARM test) is online. Over the past full 2 days it stayed up for 48 of 48 hours, or 100%. 15 October 2026 is when Rust Going Deep first saw it.
What is the Rust version for Furka Rust (ARM test)?
On Linux, Furka Rust (ARM test) runs Rust network protocol 2634 and build 167781. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
How often does Furka Rust (ARM test) wipe?
The wipes recorded for Furka Rust (ARM test) are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 2 days 15 hours is how long ago this world came into being.
Map and rules
Which rules and settings is Furka Rust (ARM test) running?
Its name does not state a gather rate for Furka Rust (ARM test). 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. It sits under Community in the server browser: a community server. VAC, Valve's anti-cheat, is enabled.
Which map is active on Furka Rust (ARM test)?
Furka Rust (ARM test) uses a game-generated procedural map.
Population
How many players are on Furka Rust (ARM test)?
Out of 10 slots, 0 are filled on Furka Rust (ARM test) right now. For the past week, players averaged 0 with a high of 1.
Where does Furka Rust (ARM test) sit in the rankings?
Over the last seven days, Furka Rust (ARM test) is #14,150 by player hours, among the top 64% of all ranked servers.
How to join
What's the process to join Furka Rust (ARM test)?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 130.61.136.113:28015.