Online 104.143.2.186:28015 checked 2h ago
Trents Test Server
Connect
srv = rust.server("104.143.2.186: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, measured since 14 Oct. 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
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())
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 · 552 on average | 636/675 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 485/525 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 299 on average | 59/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 298 on average | 36/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 270 on average | 138/200 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 256 on average | 255/300 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Trents Test Server rank?
Rank #15,373 on seven-day player hours for Trents Test Server, within the top 69% of all ranked servers.
How full does Trents Test Server run?
Current row: 0 players on Trents Test Server, against 50 slots. Over the last seven days it averaged 0 players.
Server facts
How smoothly does Trents Test Server run?
Averaged over 48 hours: 231 server fps, never under 188. Entity numbers reached 12,444, and that includes buildings, deployables and the rest. Memory peaked at 2,296 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does Trents Test Server run?
Rust network protocol 2634 and build 167781 on Windows is what Trents Test Server runs. The protocol has to match before you can join, and Steam does the updating.
Is Trents Test Server up, and what does its uptime show?
Online is the state at the latest refresh for Trents Test Server. Count back 14 days 13 hours from its reported uptime to get the last restart. Uptime of 100% across the last 7 full days: 168 hours of 168. The first row Rust Data holds for it is dated 14 October 2026.
In which location is Trents Test Server hosted?
No region is published by Trents Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. 104.143.2.186:28015 is its address.
Settings and map
Which settings and rules does Trents Test Server run?
The name Trents Test Server carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Community is its browser category. VAC is running: Valve's anti-cheat is on.
Which map has Trents Test Server selected?
The game generates the map on Trents Test Server: procedural, size 2,400, seed 1337. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.
Wipe data
When does Trents Test Server wipe, and on what schedule?
A rhythm cannot be read from the wipes of Trents Test Server on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 14 days 17 hours ago, and that is the one in play.
Lists and tags
Which lists on Rust Data hold Trents Test Server, and which filters?
These Rust Data lists include Trents Test Server: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on Trents Test Server?
The game's server browser reads these tags from Trents Test Server: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. 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 to join Trents Test Server?
The manual route: launch Rust, F1, then client.connect 104.143.2.186:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.