Offline 107.201.49.208:28015 checked 27d ago
Test567
Connect
srv = rust.server("107.201.49.208:28016")
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 66% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 25 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 25 Sep, 16:26 UTC33d ago | 1 | NaN | running | 0 |
| 1 | Fri 25 Sep, 02:28 UTC33d ago | 1 | NaN | 0.6 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 107.201.49.208:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Sep 2026, 16:26 UTC
- hostname
- –
- first seen
- 25 Sep 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 · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Test567 rank?
Player hours over seven days put Test567 at #15,614, in the top 66% of the ranked set.
How many players does Test567 hold at once?
Test567 returns no live count at this refresh, having last been seen 27 days 19 hours ago.
Server facts
Which Rust version is Test567 on?
The build is Rust network protocol 2633 and build 165217 on Windows, run by Test567. Joining needs the same protocol on your game; Steam handles the update.
Is Test567 up, and what does its uptime show?
Offline now for Test567, last seen 27 days 19 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 25 September 2026.
Which location does Test567 run from?
There is no region published for Test567. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 107.201.49.208:28015 is its address.
Map and rules
Which rules apply on Test567, and what settings?
No gather rate appears in the name: Test567. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
Which map has Test567 loaded?
A procedural map runs on Test567, generated by the game.
Wipes and dates
On what schedule does Test567 wipe?
A rhythm cannot be read from the wipes of Test567 on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 33 days 2 hours ago.
What is wipe day on Test567 like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 25 hours after it began.
Tags and filters
Which lists on Rust Data hold Test567, and which filters?
On Rust Data, Test567 appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Test567?
These tags are published by Test567 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. 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 Test567?
In Rust, F1 opens the console: type client.connect 107.201.49.208:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.