Rust Server TrendsSeismic network · station log
Recording Stations11,622 Players37,258 Active2,894 Wipes · 3 h80 48 h

Station XX-16224 · no signal

FNS TEMP benchmark

Offline 38.186.116.2:43013 checked 34d ago

Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,224
top 71%
Last wipe
34d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-16224 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

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.

Channel 3 · rank movement

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.

Expected events

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 peak
0players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 25 Sep, 05:53 UTC34d ago M0.0steady 0 – – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 531 on average
226/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
33/ 225
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
20/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 280 on average
15/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 275 on average
18/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 248 on average
35/ 200
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on FNS TEMP benchmark?

The map on FNS TEMP benchmark is procedural, produced by the game.

Which settings and rules apply on FNS TEMP benchmark?

No gather rate appears in the name of FNS TEMP benchmark. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on FNS TEMP benchmark right now?

No players are recorded on FNS TEMP benchmark at this moment; it is offline, and the last sighting was 34 days 1 hours ago.

How does FNS TEMP benchmark rank against other Rust servers?

Over the last seven days, FNS TEMP benchmark recorded enough player hours to reach #16,224 worldwide, placing it in the top 71% of all ranked servers.

Server details

How reliably does FNS TEMP benchmark stay online?

FNS TEMP benchmark is down at the moment; the last recorded contact was 34 days 1 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 25 September 2026 is when Rust Server Trends first recorded it.

Where in the world is FNS TEMP benchmark hosted?

No region is published by FNS TEMP benchmark. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 38.186.116.2:43013 is the address it uses.

What build of Rust does FNS TEMP benchmark use?

Rust network protocol 2633 and build 165217 on Linux is what FNS TEMP benchmark runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on FNS TEMP benchmark?

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

On what timetable does FNS TEMP benchmark run its wipes?

On record so far are too few of FNS TEMP benchmark's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 34 days 1 hours.

Server tags

What do the server tags on FNS TEMP benchmark mean?

The game's server browser reads the tags FNS TEMP benchmark publishes: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): Game build: 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does FNS TEMP benchmark appear?

These Rust Server Trends lists include FNS TEMP benchmark: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

What steps get you onto FNS TEMP benchmark?

To join, enter client.connect 38.186.116.2:43013 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players Slots: 10.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2633
Protocol Game protocol 2633: to join, your game must match this version.
cs165217
Build Game build: 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is set for this server.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.