Offline 5.166.162.207:28015 checked 26d ago
GENESYS_COMMUNITY
Connect
srv = rust.server("5.166.162.207:28016")
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, measured since 24 Sep. 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 64% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 11h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 11h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 36d 11h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 17:55 UTC FW26d ago | 1 | NaN | running | 1 |
# 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
4250 · seed 275337
- map
- Procedural Map
- size
- 4250
- seed
- 275337
Server
srv.info()- address
- 5.166.162.207:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:55 UTC
- hostname
- –
- first seen
- 22 Sep 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 · 535 on average | 343/350 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 320 on average | 14/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 319 on average | 24/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 158/225 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 277 on average | 92/225 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 265 on average | 32/100 |
Quick answers
From the figures on this page.
Population data
How does GENESYS_COMMUNITY compare in the rankings?
Rank #14,786 on seven-day player hours for GENESYS_COMMUNITY, within the top 64% of all ranked servers.
How full does GENESYS_COMMUNITY run?
Offline now for GENESYS_COMMUNITY, with the last sample 26 days 11 hours ago.
About the server
Which Rust version is GENESYS_COMMUNITY on?
The build is Rust network protocol 2634 and build 166494 on Windows, run by GENESYS_COMMUNITY. Steam updates your game for you, but the protocol must match to join.
Is GENESYS_COMMUNITY up, and what does its uptime show?
GENESYS_COMMUNITY is offline at this refresh; the last response came 26 days 11 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 22 September 2026.
Where does GENESYS_COMMUNITY sit?
No region is published by GENESYS_COMMUNITY. Rust Data does not look up where the machine stands; it shows where a server says it is. 5.166.162.207:28015 is its address.
Map and rules
Which settings and rules does GENESYS_COMMUNITY run?
No gather rate appears in the name: GENESYS_COMMUNITY. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Community is its browser category. Anti-cheat status: VAC on.
Which map has GENESYS_COMMUNITY loaded?
Size 4,250, seed 275337: the procedural map on GENESYS_COMMUNITY, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does GENESYS_COMMUNITY wipe, and on what schedule?
Once a month GENESYS_COMMUNITY wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 26 days 13 hours ago.
What is wipe day on GENESYS_COMMUNITY like?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 1 hours in.
Tags and filters
Which lists on Rust Data hold GENESYS_COMMUNITY, and which filters?
These Rust Data lists include GENESYS_COMMUNITY: 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.
Which meanings do the tags on GENESYS_COMMUNITY hold?
These tags are published by GENESYS_COMMUNITY and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way to join GENESYS_COMMUNITY?
Enter client.connect 5.166.162.207:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.