Online 103.236.54.209:28015 checked 13m ago
TestServer
Connect
srv = rust.server("103.236.54.209: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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 08:36 UTC12d ago | 0 | NaN | running | 0 |
| 1 | Wed 14 Oct, 19:15 UTC14d ago | 0 | NaN | 1.6 days | 0 |
| 2 | Sun 11 Oct, 08:18 UTC17d ago | 0 | NaN | 3.5 days | 0 |
| 3 | Wed 16 Sep, 19:41 UTC42d ago | 0 | NaN | 24.5 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
2300 · seed 12345
- map
- Procedural Map
- size
- 2300
- seed
- 12345
Server
srv.info()- address
- 103.236.54.209:28015
- region
- –
- max players
- 1000
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 19:15 UTC
- hostname
- –
- first seen
- 14 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 560 on average | 236/275 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 153/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 292 on average | 27/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 291 on average | 15/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 32/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 251 on average | 42/200 |
Quick answers
From the figures on this page.
Population
How does TestServer compare in the rankings?
Rank #15,349 on seven-day player hours for TestServer, within the top 69% of all ranked servers.
What population does TestServer carry?
TestServer reports 0 players at this refresh, with 1,000 slots configured. Over the last seven days it averaged 0 players.
About the server
How smoothly does TestServer run?
Averaged over 48 hours: 242 server fps, never under 227. Entity numbers reached 22,207, and that includes buildings, deployables and the rest. Memory peaked at 2,912 MB. Low fps plus an entity count on the way up is the lag players report.
What is the Rust version on TestServer?
The build is Rust network protocol 2633 and build 163794 on Linux, run by TestServer. Steam updates your game for you, but the protocol must match to join.
How reliable is TestServer, and is it up?
TestServer reports itself online at the current refresh. Count back 14 days 3 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 144 of 168, 86%. Rust Data logged it first on 14 September 2026.
In which location is TestServer hosted?
For TestServer, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 103.236.54.209:28015 is its address.
Rules, settings, map
Which rules apply on TestServer, and what settings?
No gather rate appears in the name: TestServer. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.
What is the map on TestServer?
The game generates the map on TestServer: procedural, size 2,300, seed 12345. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does TestServer wipe, and on what schedule?
Irregular wipe times on TestServer leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 14 days 5 hours ago.
On TestServer, what happens on wipe day?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which lists on Rust Data hold TestServer, and which filters?
On Rust Data, TestServer appears in these lists: 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.
Which meanings do the tags on TestServer hold?
The game's server browser reads these tags from TestServer: gmrust (Game mode): Rust survival in its standard form; mp1000 (Max players): Slot count: 1,000; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs163794 (Build): The server runs build 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not 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 TestServer?
Enter client.connect 103.236.54.209:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.