FPS TEST
Offline 149.34.245.12:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 bestWipe 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- 547/625
- 36/250
- 57/250
- 292/325
- 112/200
- 126/150
Quick answers
from the figures on this pageReset cycle
How often does FPS TEST wipe, and when?
Its rhythm cannot be told from the wipes of FPS TEST on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 44 days 11 hours ago.
Tag meanings
How should you read the tags on FPS TEST?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 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; cs163794 (Build): Game build reading: 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from FPS TEST. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show FPS TEST?
On Rust Metrics, FPS TEST sits in these lists: 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.
Occupancy
What player count does FPS TEST carry?
FPS TEST is not responding; status offline, last seen 44 days 10 hours ago.
Server
What location is FPS TEST hosted in?
No region comes from FPS TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 149.34.245.12:28015.
What Rust version is FPS TEST on?
Reading: FPS TEST, Rust network protocol 2633 and build 163794, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is FPS TEST up, and how often does it stay up?
FPS TEST reports offline. The last reading came 44 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Settings and map
What rules does FPS TEST enforce, and what are its settings?
No gather rate appears in the name: FPS 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. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.
What map is FPS TEST on?
Check: map. Procedural, generated by the game, on FPS TEST.
Connection
How can you get onto FPS TEST?
Press F1 in Rust and enter client.connect 149.34.245.12:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.