gen-timing-test
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 16d ago · 195.213.66.4:28215
Abstract
We describe the public Rust server gen-timing-test, reached at 195.213.66.4:28215. It is offline at the last check, against a seven-day mean of 01. It ranks #15,441 of all servers, the top 71%. It last wiped 16d ago.
Keywordsrust server
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 71% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: 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.
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 0 | players, last three wipes |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Mon 12 Oct, 22:5916d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| 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 |
| Map | Procedural Map |
| Size | – |
| Seed | – |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are busiest community rust servers [2] and servers wiping soon [3].
| Server | Players |
|---|---|
| Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 522 on average | 338/375 |
| Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average | 296/325 |
| Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average | 28/250 |
| Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average | 21/250 |
| Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average | 42/100 |
| Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 246 on average | 124/200 |
Appendix AQuick answers
From the figures on this page.
Server details
A.1In which location is gen-timing-test based?
A region is not published by gen-timing-test. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 195.213.66.4:28215.
A.2How reliable is gen-timing-test, and is it currently online?
At the present moment, gen-timing-test is offline; it was last seen 16 days 9 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. Its first appearance in Rust Statistics's records is 12 October 2026.
A.3What version of Rust is run on gen-timing-test?
The version of Rust on gen-timing-test is network protocol 2634 and build 167584, and the operating system is Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.
Wipe schedule
A.4What schedule does gen-timing-test follow for wipes?
The record of gen-timing-test's wipes is not yet sufficient to establish its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The current world has been running for 16 days 9 hours.
A.5How would you describe wipe day on gen-timing-test?
The average busiest point of recent wipes was 0 players. The crowd reached its maximum 0 hours after the latest wipe.
Player count
A.6What position does gen-timing-test occupy in the ranking of Rust servers?
Ranked by player hours across seven days, gen-timing-test holds #15,441, in the top 71% of all ranked servers.
A.7At what level does gen-timing-test operate in terms of players?
At this moment gen-timing-test is offline, having last been seen 16 days 9 hours ago.
Tags and filters
A.8What is the meaning of the tags on gen-timing-test?
gmrust (Game mode): This is survival as standard Rust plays; mp1 (Max players): The slot count is 1; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs167584 (Build): Build 167584 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set: these are the tags gen-timing-test publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.
A.9Where can gen-timing-test be found among the Rust Statistics lists and filters?
Rust community servers, measured are the Rust Statistics lists that gen-timing-test fits. These filters on the server list return it: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules, settings, map
A.10Which settings and rules are in force on gen-timing-test?
No gather rate appears in the name of gen-timing-test. At 8 players, the group limit equals the game's default. The mode is survival, which means gather, build and raid: the standard game. Combat and raiding against other players are allowed. It is a community server, as the browser's Community listing shows. The server has VAC off, Valve's anti-cheat.
A.11On which map does gen-timing-test take place?
A procedural map, generated by the game, is what gen-timing-test runs.
How to join
A.12What steps are required to join gen-timing-test?
Enter client.connect 195.213.66.4:28215 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.
Appendix BServer tags
What each of the server's tags means. Published as mp1,ptrak,$r?,v2634,gmrust,cs167584,ts8.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. This is survival as standard Rust plays. |
mp1 | Max players. The slot count is 1. |
ts8 | Group limit. The team cap is 8, which is the game default. |
v2634 | Protocol. The game protocol is 2634; your client must match it to join. |
cs167584 | Build. Build 167584 is the one running. |
ptrak | Networking. Networking runs on RakNet, the game's standard layer. |
$r? | Region code. No region code is 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.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Busiest community rust servers. ruststatistics.org/top-rust-community-servers.
- [3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.