Offline 109.192.68.108:28015 checked 27d ago
ccdray staging test
Connect
srv = rust.server("109.192.68.108:28017")
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 best
Top 69% 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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 09:55 UTC28d ago | 1 | 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
- 109.192.68.108:28015
- region
- –
- max players
- 8
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 09:55 UTC
- hostname
- –
- first seen
- 20 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 · 513 on average | 575/625 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 413/450 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 78/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 74/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 54/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 238 on average | 188/225 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does ccdray staging test rank?
Over the last seven days ccdray staging test sits at #16,413 on player hours, in the top 69% of ranked servers.
What population does ccdray staging test carry?
The current row shows ccdray staging test offline; the last response was 27 days 22 hours ago.
About the server
Which Rust version is ccdray staging test on?
Version Rust network protocol 2634 and build 166465 on Linux is reported by ccdray staging test. The protocol has to match before you can join, and Steam does the updating.
How reliable is ccdray staging test, and is it up?
The latest sample has ccdray staging test offline, with a last sighting 27 days 22 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 20 September 2026.
Which location does ccdray staging test run from?
For ccdray staging test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 109.192.68.108:28015.
Map and rules
What rules and settings are recorded for ccdray staging test?
You will not find a gather rate in the string ccdray staging test. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.
What is the map on ccdray staging test?
A procedural map runs on ccdray staging test, generated by the game.
Wipes and dates
On what schedule does ccdray staging test wipe?
Too few wipes are on record for ccdray staging test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 28 days 3 hours ago.
On ccdray staging test, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 1 hours in.
Lists and tags
Which Rust Data filters and lists contain ccdray staging test?
On Rust Data, ccdray staging test appears in these lists: 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 ccdray staging test?
The game's server browser reads these tags from ccdray staging test: gmrust (Game mode): Rust survival in its standard form; mp8 (Max players): 8 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166465 (Build): Build number: 166465; ptrak (Networking): Standard network layer for Rust: RakNet; $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.
Join steps
How can I connect to ccdray staging test?
Enter client.connect 109.192.68.108:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.