Online 91.200.13.51:28015 checked 11m ago
TEST SERVER
Connect
srv = rust.server("91.200.13.51: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 27 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 48% 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())Map
1000 · seed 12345
- map
- Procedural Map
- size
- 1000
- seed
- 12345
Server
srv.info()- address
- 91.200.13.51:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 18:42 UTC
- hostname
- –
- first seen
- 26 Oct 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.
Player counts
How does TEST SERVER compare in the rankings?
Over the last seven days TEST SERVER sits at #10,568 on player hours, in the top 48% of ranked servers.
How many players does TEST SERVER hold at once?
The sample now reads 0 players for TEST SERVER, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 08:00 UTC, mean 0 players.
Server data
How well does TEST SERVER perform?
The 48-hour average is 240 server fps, with a low of 240. Buildings, deployables and all else in the world took the count as high as 2,185 entities. The memory field tops out at 604 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on TEST SERVER?
The build is Rust network protocol 2635 and build 168909 on Linux, run by TEST SERVER. Joining needs the same protocol on your game; Steam handles the update.
Is TEST SERVER up, and what does its uptime show?
TEST SERVER reports itself online at the current refresh. The uptime it reports puts the last restart about 5 hours ago. Uptime of 50% across the last 2 full days: 24 hours of 48. Its earliest recorded date in Rust Data is 26 October 2026.
In which location is TEST SERVER hosted?
No region is published by TEST SERVER. 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 91.200.13.51:28015.
Settings and map
Which settings and rules does TEST SERVER run?
You will not find a gather rate in the string TEST SERVER. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC off.
What is the map on TEST SERVER?
TEST SERVER runs a procedural map of size 1,000 with seed 12345, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
On what schedule does TEST SERVER wipe?
The record for TEST SERVER holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 2 days 6 hours ago.
Tags, lists
Which lists on Rust Data hold TEST SERVER, and which filters?
The Rust Data lists that TEST SERVER fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
Which meanings do the tags on TEST SERVER hold?
These tags are published by TEST SERVER and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; 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): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into TEST SERVER?
In Rust, F1 opens the console: type client.connect 91.200.13.51:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.