Offline 67.183.238.33:28015 checked 27d ago
Adam's Test Server
Connect
srv = rust.server("67.183.238.33:27015")
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 60% 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 7d 2h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 2h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 2h | 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 17:24 UTC FW27d 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
- 67.183.238.33:28015
- region
- – · us2
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:41 UTC
- hostname
- –
- first seen
- 1 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 · 514 on average | 440/500 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 317 on average | 447/475 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 281 on average | 976/1000 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 276 on average | 63/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 992/1000 |
| 5 | Rustoria.co - US Main | NA · groups of 16+ · weekly · 236 on average | 26/250 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Adam's Test Server rank?
Over the last seven days Adam's Test Server sits at #13,897 on player hours, in the top 60% of ranked servers.
What population does Adam's Test Server carry?
The current row shows Adam's Test Server offline; the last response was 27 days 22 hours ago.
Server facts
Which Rust version is Adam's Test Server on?
Rust network protocol 2634 and build 166493 on Windows is what Adam's Test Server runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Adam's Test Server, and is it up?
The latest sample has Adam's Test Server 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 1 October 2026.
Which location does Adam's Test Server run from?
For Adam's Test Server, no region is published; the region code is us2. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 67.183.238.33:28015.
Rules, settings, map
Which rules apply on Adam's Test Server, and what settings?
No gather rate appears in the name: Adam's Test Server. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat status: VAC on.
What is the map on Adam's Test Server?
The game generates its map: procedural, on Adam's Test Server.
Wipe schedule
On what schedule does Adam's Test Server wipe?
The only wipe Adam's Test Server takes is the monthly force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 27 days 22 hours ago, and that is the one in play.
On Adam's Test Server, what happens on wipe day?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which lists on Rust Data hold Adam's Test Server, and which filters?
These Rust Data lists include Adam's Test Server: Rust community servers, unfiltered. 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.
Which meanings do the tags on Adam's Test Server hold?
Read by the game's server browser, the tags Adam's Test Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166493 (Build): The server runs build 166493; ptrak (Networking): Network traffic runs over RakNet, the game standard; $rus2 (Region code): The row gives us2 as its region code. 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.
How to join
What is the way into Adam's Test Server?
In Rust, F1 opens the console: type client.connect 67.183.238.33:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.