Offline 138.64.100.50:28015 checked 35m ago
Test server
Connect
srv = rust.server("138.64.100.50: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
Top 59% 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 12:51 UTC11h ago | NaN | NaN | running | 1 |
| 1 | Sun 18 Oct, 06:16 UTC10d ago | 1 | NaN | 10.3 days | 1 |
| 2 | Sun 11 Oct, 14:02 UTC17d ago | 1 | NaN | 6.7 days | 0 |
| 3 | Sat 10 Oct, 12:37 UTC18d ago | 1 | NaN | 1.1 days | 0 |
| 4 | Fri 2 Oct, 05:58 UTC26d ago | 1 | halved by day 2 | 8.3 days | 0 |
| 5 | Sat 26 Sep, 11:25 UTC32d ago | 3 | halved by day 1 | 5.8 days | 2 |
| 6 | Fri 25 Sep, 12:57 UTC33d ago | 3 | NaN | 0.9 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
- 138.64.100.50:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 06:16 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 560 on average | 238/275 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 159/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 | 16/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 | 45/200 |
Quick answers
From the figures on this page.
Population
What position does Test server take in the server rankings?
Rank #13,116 on seven-day player hours for Test server, within the top 59% of all ranked servers.
How full does Test server run?
Test server returns no live count at this refresh, having last been seen 35 minutes ago. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 13:00 UTC, averaging 1 players.
Server facts
What Rust version does Test server run?
Rust network protocol 2635 and build 168909 on Windows is what Test server runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Test server, and is it up?
Offline now for Test server, last seen 35 minutes ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 25 September 2026.
In which location is Test server hosted?
For Test server, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 138.64.100.50:28015.
Settings and map
What rules and settings are recorded for Test server?
You will not find a gather rate in the string Test server. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.
Which map has Test server selected?
Test server runs a procedural map, which the game generates.
Wipe data
When does Test server wipe, and on what schedule?
No next wipe can be predicted for Test server, which wipes at irregular times. 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 10 days 18 hours ago.
What is wipe day on Test server like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The drop under half arrived by day 1.5 in the other cases.
Lists and tags
Which Rust Data filters and lists contain Test server?
These Rust Data lists include Test server: 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; Last wipe: In the last 2 weeks.
How should you read the server tags on Test server?
The game's server browser reads these tags from Test server: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. 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.
How to join
What is the way to join Test server?
In Rust, F1 opens the console: type client.connect 138.64.100.50:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.