Offline 2.63.25.148:28015 checked 42d ago
TEST
Connect
srv = rust.server("2.63.25.148: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 best
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
- 2.63.25.148:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Sep 2026, 10:34 UTC
- hostname
- –
- first seen
- 16 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 · 554 on average | 395/500 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 242/300 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 295 on average | 41/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 294 on average | 31/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 273 on average | 69/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 252 on average | 80/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does TEST rank?
Player hours over seven days put TEST at #13,352, in the top – of the ranked set.
What population does TEST carry?
TEST returns no live count at this refresh, having last been seen 42 days 10 hours ago.
Server facts
Which Rust version is TEST on?
The build is Rust network protocol 2633 and build 163794 on Windows, run by TEST. The protocol has to match before you can join, and Steam does the updating.
How reliable is TEST, and is it up?
Offline now for TEST, last seen 42 days 10 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 16 September 2026.
Where does TEST sit?
For TEST, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 2.63.25.148:28015.
Map and rules
What rules and settings are recorded for TEST?
You will not find a gather rate in the string TEST. 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. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.
Which map has TEST selected?
A procedural map runs on TEST, generated by the game.
Wipe schedule
On what schedule does TEST wipe?
Too few wipes are on record for TEST to reveal its rhythm. 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 42 days 12 hours ago.
Lists and tags
Which lists on Rust Data hold TEST, and which filters?
On Rust Data, TEST appears in these lists: Rust community servers, unfiltered. It appears under these filters 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 TEST?
The game's server browser reads these tags from TEST: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): The server runs build 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to TEST?
In Rust, F1 opens the console: type client.connect 2.63.25.148:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.