RUST METRICSFlight deck · live data
Data live Servers11,649 Players43,286 Populated3,030 Fresh wipes 3 h94 Scan5 min
‹ All servers38.186.116.2:43013
Offline Full Queue Fresh wipe Wipe due No query

FNS TEMP benchmark

Offline 38.186.116.2:43013 checked 34d 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#16,224top 71%
Last wipe34d 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
15k10k15k20k25 Sep26 Sep28 Sep29 Sep1 Oct2 Oct

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

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 25 Sep, 05:53 UTC34d ago 0 – running 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 FNS TEMP benchmark when wipe day comes?

The busiest point of its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does FNS TEMP benchmark wipe, and when?

The rhythm of FNS TEMP benchmark's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 34 days 2 hours ago the current world was made.

Tag meanings

How should you read the tags on FNS TEMP benchmark?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from FNS TEMP benchmark. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does FNS TEMP benchmark appear in Rust Metrics lists and filters?

These Rust Metrics lists carry FNS TEMP benchmark: 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.

Population

Where does FNS TEMP benchmark sit in the rankings?

Ranking for FNS TEMP benchmark: #16,224 on seven-day player hours, top 71% of all ranked servers.

What is the population on FNS TEMP benchmark?

Status for FNS TEMP benchmark: offline. Last seen 34 days 2 hours ago.

Server details

Which location does FNS TEMP benchmark run from?

No region comes from FNS TEMP benchmark. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 38.186.116.2:43013.

What Rust version is FNS TEMP benchmark on?

Reading: FNS TEMP benchmark, Rust network protocol 2633 and build 165217, Linux. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is FNS TEMP benchmark, and is it online now?

Reading: offline. FNS TEMP benchmark last answered 34 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 25 September 2026.

Map and rules

What rules does FNS TEMP benchmark enforce, and what are its settings?

Check: gather rate. The name FNS TEMP benchmark does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is FNS TEMP benchmark on?

The game generates a procedural map for FNS TEMP benchmark.

How to join

What do you do to join FNS TEMP benchmark?

Check: join. Open Rust, press F1, then enter client.connect 38.186.116.2:43013. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 165217.
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.