Offline NA 72.182.170.3:28019 checked 1d ago
DT TEST SERVER
Connect
srv = rust.server("72.182.170.3:28021")
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, top 83% in NA, and #199 of the solo servers (top 90%). Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 8d 20h. # The force wipe
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 72.182.170.3:28019
- region
- NA
- max players
- 10
- group limit
- solo
- wipe schedule
- monthly
- last wipe
- 1 Oct 2026, 21:14 UTC
- hostname
- –
- first seen
- 25 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 | Lone Wolf Rust | Solo Only, Monthly, Vanilla, No BP Wipes | NA · solo · monthly · 37 on average | 40/100 |
| 1 | RustLands | Monthly | Solo | No BP Wipe | Active Admins | NA · solo · monthly · 7 on average | 9/225 |
| 2 | MIGHTYRUST.GG|Solo Only|Monthly|No BP Wipes|Low Upkeep | NA · solo · monthly · 2 on average | 3/50 |
| 3 | US Limitless 2x Monthly Solo Only|No BP Wipes|Noob Friendly | NA · solo · 2x · monthly · 32 on average | 35/200 |
| 4 | DOPERUST.COM – 2X US Solo Only – 50% Upkeep|Noob Friendly | NA · solo · 2x · monthly · 6 on average | 8/100 |
| 5 | Old Dad's 2X Solo Only 2.0 | NA · solo · 2x · monthly · 5 on average | 5/50 |
Quick answers
From the figures on this page.
Population data
What position does DT TEST SERVER take in the server rankings?
On seven-day player hours DT TEST SERVER is #15,404 overall and #1,550 in North America, inside the top 69% of all ranked servers. The solo group places it at #199.
What population does DT TEST SERVER carry?
DT TEST SERVER returns no live count at this refresh, having last been seen 41 hours ago. Over the last seven days it averaged 0 players.
Server data
What is the Rust version on DT TEST SERVER?
The build is Rust network protocol 2635 and build 168909 on Windows, run by DT TEST SERVER. Joining needs the same protocol on your game; Steam handles the update.
How reliable is DT TEST SERVER, and is it up?
DT TEST SERVER is offline at this refresh; the last response came 41 hours ago. Uptime of 21% across the last 1 full day: 5 hours of 24. Its earliest recorded date in Rust Data is 25 October 2026.
In which location is DT TEST SERVER hosted?
The NA tag is what DT TEST SERVER uses to list itself in North America. Rust Data does not look up where the machine stands; it shows where a server says it is. 72.182.170.3:28019 is its address.
Settings and map
Which settings and rules does DT TEST SERVER run?
No gather rate appears in the name: DT TEST SERVER. No teams here: solo only. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. The VAC field reads off.
Which map has DT TEST SERVER loaded?
The game generates its map: procedural, on DT TEST SERVER.
Wipe data
On what schedule does DT TEST SERVER wipe?
The next wipe for DT TEST SERVER is an estimate, drawn from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 26 days ago. Its tags carry a monthly wipe schedule.
Tags, lists
Which Rust Data filters and lists contain DT TEST SERVER?
On Rust Data, DT TEST SERVER appears in these lists: Modded Rust servers, Solo Rust servers, group limit 1 and North America Rust servers. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Monthly.
How should you read the server tags on DT TEST SERVER?
These tags are published by DT TEST SERVER and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts1 (Group limit): Team size tops out at 1; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; NA (North America): In the server browser it sits under North America. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into DT TEST SERVER?
Enter client.connect 72.182.170.3:28019 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.