Online 5.182.207.231:11000 checked 9m ago
TESTTTTT
Connect
srv = rust.server("5.182.207.231:11001")
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 17 Sep. 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 24% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 8h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 22h | Thu 12 Nov, 08:53 UTC | wipe |
| 2 | 27d 22h | Thu 26 Nov, 08:53 UTC | wipe |
| 3 | 35d 8h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 41d 22h | Thu 10 Dec, 08:53 UTC | 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 29 Oct, 08:53 UTC1h ago | NaN | NaN | running | 0 |
| 1 | Sat 10 Oct, 19:22 UTC18d ago | 1 | NaN | NaN | 1 |
| 2 | Thu 1 Oct, 18:23 UTC FW27d ago | 1 | halved by day 1 | 9 days | 0 |
| 3 | Tue 29 Sep, 17:59 UTC29d ago | 1 | held half | 2 days | 0 |
| 4 | Mon 28 Sep, 19:01 UTC30d ago | 1 | NaN | 1 days | 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
4500 · seed 2234235
- map
- Custom Map
- size
- 4500
- seed
- 2234235
Server
srv.info()- address
- 5.182.207.231:11000
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 29 Oct 2026, 08:53 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Alias RPG Season 10 [PVE,RU] | EU · groups of 8+ · biweekly · 11 on average | 12/100 |
| 1 | RustNK - Custom Hardcore PvE, NPCs, Events & Quests | NA · no group limit · biweekly · 4 on average | 3/50 |
| 2 | Primal Earth PvE | Hardcore Progression | Rock to AK | groups of 8+ · biweekly · 3 on average | 4/25 |
| 3 | HARD PVE TOP | Classic PvE | RaidBases | Custom Events | No VIP | groups of 8+ · biweekly · 3 on average | 4/50 |
| 4 | #2 RUSTMAX PVE HARD x1/ZOMBIE/BASE/EVENTS | EU · no group limit · 1x · biweekly · 2 on average | 1/50 |
| 5 | RustAria#1 [PvE/QUEST/RPG/CRAFT/HARD] | groups of 50+ · biweekly · 2 on average | 0/200 |
Quick answers
From the figures on this page.
Population
What position does TESTTTTT take in the server rankings?
Rank #5,367 on seven-day player hours for TESTTTTT, within the top 24% of all ranked servers.
How full does TESTTTTT run?
1 is the count in the players field for TESTTTTT at this refresh. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 10:00 UTC, averaging 1 players.
Server data
How well does TESTTTTT perform?
Averaged over 48 hours: 297 server fps, never under 184. The entity count peaked at 371,300, covering buildings, deployables and the rest of the world. Memory peaked at 9,874 MB. Low fps plus an entity count on the way up is the lag players report.
What Rust version does TESTTTTT run?
Rust network protocol 2635 and build 168909 on Windows is what TESTTTTT runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is TESTTTTT, and is it online now?
The current sample puts TESTTTTT online. The uptime it reports puts the last restart about 3 days 2 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does TESTTTTT run from?
There is no region published for TESTTTTT. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 5.182.207.231:11000.
Map and rules
Which rules apply on TESTTTTT, and what settings?
You will not find a gather rate in the string TESTTTTT. Eight players per group: that is the game's default, and it applies here. Game mode hardcore, with this note: The hardest mode Facepunch ships. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on TESTTTTT?
Size 4,500, seed 2234235: the procedural map on TESTTTTT, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Under map name you will find: Custom Map.
Wipes and dates
On what schedule does TESTTTTT wipe?
Too few wipes are on record for TESTTTTT to confirm its schedule, so the tag drives the prediction. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 1 hours ago. The tags list a two-weekly wipe cycle.
What is wipe day on TESTTTTT like?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began. Half the peak or more was held to the next wipe in 33% of recent wipes. In the wipes where it did not hold, half was lost by day 1.
Tags and filters
Which lists on Rust Data hold TESTTTTT, and which filters?
On Rust Data, TESTTTTT appears in these lists: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE and Hardcore; Server tag: Biweekly ^b, Hardcore ^h, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.
How should you read the server tags on TESTTTTT?
These tags are published by TESTTTTT and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp0 (Max players): Slot count: 0; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): Two weeks between wipes; ^h (Hardcore): Hardcore mode from Facepunch: harsher survival, fewer helpers; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join TESTTTTT?
In Rust, F1 opens the console: type client.connect 5.182.207.231:11000. Launch Rust on this page does the same by opening the game through Steam and connecting. https://rust-z.gamestores.app/ is the website recorded for it.