Offline 216.146.25.53:28015 checked 4d ago
Rust Defensive Telemetry Lab
Connect
srv = rust.server("216.146.25.53: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 bestTop 38% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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
- 216.146.25.53:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 21:03 UTC
- hostname
- –
- first seen
- 11 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 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 109/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 167/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 50/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 25/1000 |
Quick answers
From the figures on this page.
Population data
How does Rust Defensive Telemetry Lab compare in the rankings?
Rank #8,552 on seven-day player hours for Rust Defensive Telemetry Lab, within the top 38% of all ranked servers.
What population does Rust Defensive Telemetry Lab carry?
Rust Defensive Telemetry Lab returns no live count at this refresh, having last been seen 4 days 9 hours ago. Over the last seven days it averaged 1 players and peaked at 2.
About the server
Which Rust version is Rust Defensive Telemetry Lab on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Rust Defensive Telemetry Lab. Joining needs the same protocol on your game; Steam handles the update.
Is Rust Defensive Telemetry Lab up, and what does its uptime show?
Offline now for Rust Defensive Telemetry Lab, last seen 4 days 9 hours ago. Uptime of 7% across the last 7 full days: 12 hours of 168. Rust Data logged it first on 11 October 2026.
Where does Rust Defensive Telemetry Lab sit?
No region is published by Rust Defensive Telemetry Lab. Rust Data does not look up where the machine stands; it shows where a server says it is. 216.146.25.53:28015 is its address.
Rules, settings, map
Which settings and rules does Rust Defensive Telemetry Lab run?
The name Rust Defensive Telemetry Lab carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has Rust Defensive Telemetry Lab selected?
Rust Defensive Telemetry Lab runs a procedural map, which the game generates.
Wipe data
On what schedule does Rust Defensive Telemetry Lab wipe?
The record for Rust Defensive Telemetry Lab holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 17 days 12 hours ago.
Tags, lists
Where does Rust Defensive Telemetry Lab appear among Rust Data lists and filters?
The Rust Data lists that Rust Defensive Telemetry Lab fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Rust Defensive Telemetry Lab?
Read by the game's server browser, the tags Rust Defensive Telemetry Lab publishes are: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join Rust Defensive Telemetry Lab?
In Rust, F1 opens the console: type client.connect 216.146.25.53:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.