Offline 195.213.66.4:28215 checked 16d ago
gen-timing-test
Connect
srv = rust.server("195.213.66.4:28217")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 12 Oct, 22:59 UTC16d ago | 0 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 516 on average | 441/475 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 348/375 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 42/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 33/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 46/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 243 on average | 147/200 |
Quick answers
From the figures on this page.
Player counts
What position does gen-timing-test take in the server rankings?
Over the last seven days gen-timing-test sits at #15,441 on player hours, in the top 71% of ranked servers.
How full does gen-timing-test run?
gen-timing-test returns no live count at this refresh, having last been seen 16 days 11 hours ago.
Server facts
What Rust version does gen-timing-test run?
Rust network protocol 2634 and build 167584 on Linux is what gen-timing-test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is gen-timing-test, and is it up?
Offline now for gen-timing-test, last seen 16 days 11 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 12 October 2026.
In which location is gen-timing-test hosted?
No region is published by gen-timing-test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 195.213.66.4:28215.
Rules, settings, map
What rules and settings are recorded for gen-timing-test?
You will not find a gather rate in the string gen-timing-test. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC off.
What is the map on gen-timing-test?
A procedural map runs on gen-timing-test, generated by the game.
Wipes and dates
When does gen-timing-test wipe, and on what schedule?
The record for gen-timing-test holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 16 days 11 hours ago.
What is wipe day on gen-timing-test like?
The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does gen-timing-test appear among Rust Data lists and filters?
These Rust Data lists include gen-timing-test: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on gen-timing-test?
The game's server browser reads these tags from gen-timing-test: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167584 (Build): The server runs build 167584; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into gen-timing-test?
In Rust, F1 opens the console: type client.connect 195.213.66.4:28215. Launch Rust on this page does the same by opening the game through Steam and connecting.