Statistical profileOffline
gen-timing-test
195.213.66.4:28215 checked 16d ago
Connect to this server
1. Main points
Players now
0/ 1
0% full
7-day average
0
peak –
Rank
#15,441
top 71%
Last wipe
16d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 1 slots.
- It ranks #15,441 of all ranked servers, the top 71%, on player hours over the last seven days.
- Its current map went up 16d ago.
2. Players
Figure 1: Players on gen-timing-test
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo 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
0
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 22:59 UTC16d ago | 0 | – | running | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of gen-timing-test
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of gen-timing-test
What the server publishes and what was recorded
| Address | 195.213.66.4:28215 |
|---|---|
| Region | – |
| Max players | 1 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 12 Oct 2026, 23:47 UTC |
| Hostname | – |
| First seen | 12 Oct 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 513 on average | 507 / 550 |
| Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 422 / 450 |
| Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 63 / 250 |
| Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 67 / 250 |
| Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 55 / 100 |
| Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 238 on average | 169 / 200 |
10. Quick answers
From the figures on this page.
Wipe schedule
This release records the wipe timetable for gen-timing-test: what is it?
Too few wipes of gen-timing-test are on record to establish its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. This world was generated 16 days 13 hours ago.
On gen-timing-test, what happens on wipe day?
The average busiest point of its recent wipes drew 0 players. The peak of the latest wipe's crowd came 0 hours after it began.
Server details
Is gen-timing-test up, and how well has it held up?
The latest count records gen-timing-test as offline, last seen 16 days 13 hours ago. A total of 0 of 168 hours were up over 7 full days, which is 0% of the time. It was first seen by Rust Census on 12 October 2026.
Which location does gen-timing-test run from?
No region is given by gen-timing-test. Rust Census does not look up where the machine stands; it shows where a server says it is. At 195.213.66.4:28215 it is addressed.
What version of Rust has been recorded on gen-timing-test?
This release lists gen-timing-test on Rust network protocol 2634 and build 167584, running on Linux. To join, your game has to be on the same protocol; Steam handles the update.
Population
How many players does gen-timing-test carry?
gen-timing-test is offline at present; its last recording was 16 days 13 hours ago.
How does gen-timing-test compare with other servers in the rankings?
The rank for gen-timing-test is #15,441 on seven-day player hours, in the top 71% of ranked servers.
Tags, lists
Where does gen-timing-test appear among the Rust Census lists and filters?
These Rust Census lists include gen-timing-test: Community servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
The tags on gen-timing-test: what do they indicate?
Read by the game's server browser, gen-timing-test publishes these tags: gmrust (Game mode): Survival play, in the standard Rust format; mp1 (Max players): Slots: 1; ts8 (Group limit): 8 per team, which is the game's default limit; v2634 (Protocol): Protocol 2634 is required; a different version cannot join; cs167584 (Build): Build 167584 is installed; ptrak (Networking): RakNet is used, the standard network layer of the game; $r? (Region code): A region code has not been set. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.
Map and rules
Which map is in use on gen-timing-test?
The game generates the procedural map on gen-timing-test.
How is gen-timing-test configured, and what rules does it keep?
The name of gen-timing-test carries no gather rate. The group cap stands at 8 players, the default for the game. survival is the game mode recorded, the standard game: gather, build, raid. Fighting other players and raiding are allowed. Community is its section in the server browser. VAC, Valve's anti-cheat, is disabled.
How to join
How can you connect to gen-timing-test?
You can open the console in Rust with F1 and enter client.connect 195.213.66.4:28215; or press Launch Rust and join on this page, and you are connected through Steam.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp1,ptrak,$r?,v2634,gmrust,cs167584,ts8
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp1 | Max players Slots: 1. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2634 | Protocol Protocol 2634 is required; a different version cannot join. |
cs167584 | Build Build 167584 is installed. |
ptrak | Networking RakNet is used, the standard network layer of the game. |
$r? | Region code A region code has not been 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.