Online 217.94.246.164:28015 checked 10m ago
rustctl-localtest
Connect
srv = rust.server("217.94.246.164: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 bestTop 24% 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 217.94.246.164:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 23:45 UTC
- hostname
- –
- first seen
- 24 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 · 516 on average | 486/525 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 401/450 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 52/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 276 on average | 44/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 48/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 243 on average | 161/200 |
Quick answers
From the figures on this page.
Player counts
How does rustctl-localtest compare in the rankings?
Player hours over seven days put rustctl-localtest at #5,294, in the top 24% of the ranked set.
How full does rustctl-localtest run?
rustctl-localtest reports 1 players at this refresh, with 4 slots configured. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 23:00 UTC is the busiest, at 1 players.
About the server
Which Rust version is rustctl-localtest on?
Rust network protocol 2635 and build 168909 on Windows is what rustctl-localtest runs. The protocol has to match before you can join, and Steam does the updating.
Is rustctl-localtest up, and what does its uptime show?
Online is the state at the latest refresh for rustctl-localtest. Uptime of 39% across the last 4 full days: 37 hours of 96. Its earliest recorded date in Rust Data is 24 October 2026.
Which location does rustctl-localtest run from?
For rustctl-localtest, 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 217.94.246.164:28015.
Map and rules
Which settings and rules does rustctl-localtest run?
No gather rate appears in the name: rustctl-localtest. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. The server browser lists it under Community. The VAC field reads off.
What is the map on rustctl-localtest?
A procedural map runs on rustctl-localtest, generated by the game.
Wipes and dates
When does rustctl-localtest wipe, and on what schedule?
Too few wipes are on record for rustctl-localtest to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 4 days 12 hours ago, and that is the one in play.
Tags, lists
Which lists on Rust Data hold rustctl-localtest, and which filters?
On Rust Data, rustctl-localtest appears in these lists: 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 week.
How should you read the server tags on rustctl-localtest?
The game's server browser reads these tags from rustctl-localtest: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): The default cap applies: 8 per team; 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.
Connecting
What is the way into rustctl-localtest?
In Rust, F1 opens the console: type client.connect 217.94.246.164:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.