Skip to the page
Network live 11,731 servers online 65,070 players aboard 200 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

gen-timing-test

Offline 195.213.66.4:28215 checked 17d ago

Tracking number · connect
Wipe progress · wiped 17d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –too few wipes seen yet
0/ 1 players now 0% full
07-day averagepeak –
#15,441ranktop 71%
17d agolast wipeno schedule published
–next wipetoo few wipes seen yet
Delivery history

Players, performance and rank

Players

No hourly history yet.

Hourly average and peak, UTC.

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.

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.

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.

0wipe-day peakplayers, 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.

Wipes

every wipe as a delivery, newest first
  1. Mon 12 Oct, 22:59 UTC 23:59 UK · 17d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    running
    Players before
    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.

Similar parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 499 on average 110 / 250
  2. Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average 130 / 200
  3. Rusty Moose |EU Main|EU · groups of 12+ · weekly · 283 on average 482 / 575
  4. Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average 32 / 100
  5. Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average 554 / 650
  6. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 248 on average 455 / 525
Help desk

Quick answers

From the figures on this page.

Player activity

What is the ranking of gen-timing-test against other Rust servers?

In the top 71% of all ranked servers sits gen-timing-test, at #15,441 on hours played over seven days.

Is gen-timing-test busy at the moment?

At the moment gen-timing-test is offline, having last been seen 17 days ago.

Server rules

Which map is active on gen-timing-test?

The map on gen-timing-test is procedural, produced by the game.

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

No gather rate appears in the name of gen-timing-test. 8 players is the group limit, since the game's default applies. survival is the mode, gather, build and raid, as the standard game goes. Raiding and PvP are both on. You will find it listed under Community in the server browser: it is a community server. VAC, the anti-cheat from Valve, is not active.

Server details

In which region is gen-timing-test based?

No region is published by gen-timing-test. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. The address to connect to is 195.213.66.4:28215.

How reliable is gen-timing-test, and is it currently online?

gen-timing-test is offline at the moment, with the last sighting 17 days ago. 0% is the uptime for the last 7 full days, up for 0 of 168 hours. It was first seen by Rust Wipe Tracker on 12 October 2026.

What Rust version is gen-timing-test using?

Rust network protocol 2634 and build 167584 on Linux is what gen-timing-test runs. To join, your game must be on the same protocol; Steam handles that update for you.

Wipe schedule

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

At their busiest, its recent wipes drew an average of 0 players. After 0 hours the latest wipe's crowd hit its peak.

How often does gen-timing-test wipe, and at what times?

Its rhythm cannot yet be told: too few of gen-timing-test's wipes are on record. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. 17 days have passed since this world was made.

Server tags

Where does gen-timing-test appear in Rust Wipe Tracker lists and filters?

You will find gen-timing-test on the following Rust Wipe Tracker lists: Rust community servers, unmodded. 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.

What is the meaning of the server tags on gen-timing-test?

Read off the game's server browser, the tags for gen-timing-test are: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): The server has 1 slots; ts8 (Group limit): 8 per team, which is the default; v2634 (Protocol): Join only if your game runs protocol 2634; cs167584 (Build): Build number: 167584; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): A region code isn't set. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.

Connecting

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

Enter client.connect 195.213.66.4:28215 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp1
Max players The server has 1 slots.
ts8
Group limit 8 per team, which is the default.
v2634
Protocol Join only if your game runs protocol 2634.
cs167584
Build Build number: 167584.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code A region code isn't 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.