Offline 38.186.116.2:43013 checked 34d ago
FNS TEMP benchmark
Connect
srv = rust.server("38.186.116.2:43016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 25 Sep, 05:53 UTC34d ago | 0 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 38.186.116.2:43013
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Sep 2026, 05:53 UTC
- hostname
- –
- first seen
- 25 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 522 on average | 338/375 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 296/325 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 28/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 21/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 42/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 246 on average | 124/200 |
Quick answers
From the figures on this page.
Player counts
How does FNS TEMP benchmark compare in the rankings?
Over the last seven days FNS TEMP benchmark sits at #16,224 on player hours, in the top 71% of ranked servers.
How many players does FNS TEMP benchmark hold at once?
Offline now for FNS TEMP benchmark, with the last sample 34 days 3 hours ago.
Server data
What is the Rust version on FNS TEMP benchmark?
The build is Rust network protocol 2633 and build 165217 on Linux, run by FNS TEMP benchmark. The protocol has to match before you can join, and Steam does the updating.
Is FNS TEMP benchmark up, and what does its uptime show?
The latest sample has FNS TEMP benchmark offline, with a last sighting 34 days 3 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 25 September 2026.
Where does FNS TEMP benchmark sit?
For FNS TEMP benchmark, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 38.186.116.2:43013 is its address.
Rules, settings, map
Which rules apply on FNS TEMP benchmark, and what settings?
You will not find a gather rate in the string FNS TEMP benchmark. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Community is its browser category. VAC is running: Valve's anti-cheat is on.
What is the map on FNS TEMP benchmark?
A procedural map runs on FNS TEMP benchmark, generated by the game.
Wipes and dates
When does FNS TEMP benchmark wipe, and on what schedule?
A rhythm cannot be read from the wipes of FNS TEMP benchmark on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 34 days 3 hours ago, and that is the one in play.
On FNS TEMP benchmark, what happens on wipe day?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags, lists
Where does FNS TEMP benchmark appear among Rust Data lists and filters?
These Rust Data lists include FNS TEMP benchmark: Rust community servers, unfiltered. 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.
How should you read the server tags on FNS TEMP benchmark?
The game's server browser reads these tags from FNS TEMP benchmark: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Recorded game build: 165217; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into FNS TEMP benchmark?
Enter client.connect 38.186.116.2:43013 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.