RUST METRICSFlight deck · live data
Data live Servers11,878 Players98,796 Populated3,935 Fresh wipes 3 h404 Scan5 min
‹ All servers195.213.66.4:28215
Offline Full Queue Fresh wipe Wipe due No query

gen-timing-test

Offline 195.213.66.4:28215 checked 16d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

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#15,441top 71%
Last wipe16d 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
15k10k15k20k12 Oct13 Oct15 Oct16 Oct18 Oct19 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

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 22:59 UTC16d 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

Wipe timing

What should you expect from wipe day on gen-timing-test?

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

What wipe timing does gen-timing-test follow?

To tell the rhythm of gen-timing-test, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 16 days 17 hours ago the current world was made.

Tag meanings

How should you read the tags on gen-timing-test?

These are the tags gen-timing-test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167584 (Build): Game build reading: 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. 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 gen-timing-test?

These Rust Metrics lists carry gen-timing-test: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does gen-timing-test sit in the rankings?

Ranking for gen-timing-test: #15,441 on seven-day player hours, top 71% of all ranked servers.

What is the population on gen-timing-test?

Reading for gen-timing-test: offline at this moment; last seen 16 days 16 hours ago.

Server

Which location does gen-timing-test run from?

No region comes from gen-timing-test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 195.213.66.4:28215.

What Rust version is gen-timing-test on?

Rust network protocol 2634 and build 167584 on Linux is the build gen-timing-test runs. Check: protocol. To join, your game must match; Steam handles the update.

Is gen-timing-test up, and how often does it stay up?

Reading: offline. gen-timing-test last answered 16 days 16 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 12 October 2026.

Map and rules

What settings and rules apply on gen-timing-test?

Check: gather rate. The name gen-timing-test does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.

What map is gen-timing-test on?

Procedural map on gen-timing-test, made by the game's generator.

Connection

What do you do to join gen-timing-test?

To join: start Rust, press F1 and type client.connect 195.213.66.4:28215. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167584
Build Game build reading: 167584.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.