Online 73.169.101.163:28015 checked 8m ago
DLA303
Connect
srv = rust.server("73.169.101.163:28017")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))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 17 Sep. 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 · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 20h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 20h | Thu 3 Dec, 19:00 UTC | FW 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 | Thu 1 Oct, 17:36 UTC FW28d ago | 0 | NaN | running | 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
3000 · seed 2119474038
- map
- Procedural Map
- size
- 3000
- seed
- 2119474038
Server
srv.info()- address
- 73.169.101.163:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:36 UTC
- hostname
- –
- first seen
- 13 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 · 503 on average | 159/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 184/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 282 on average | 604/675 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 277 on average | 37/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 687/775 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 245 on average | 561/625 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does DLA303 rank?
Player hours over seven days put DLA303 at #15,276, in the top 69% of the ranked set.
How full does DLA303 run?
Current row: 0 players on DLA303, against 50 slots. Over the last seven days it averaged 0 players.
About the server
How smoothly does DLA303 run?
Averaged over 48 hours: 119 server fps, never under 38. Buildings, deployables and all else in the world took the count as high as 48,451 entities. A high of 2,547 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on DLA303?
Rust network protocol 2635 and build 168909 on Linux is what DLA303 runs. Steam updates your game for you, but the protocol must match to join.
Is DLA303 up, and what does its uptime show?
The current sample puts DLA303 online. A restart about 7 days 3 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 13 September 2026.
Where does DLA303 sit?
No region is published by DLA303. 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 73.169.101.163:28015.
Rules, settings, map
What rules and settings are recorded for DLA303?
The name DLA303 carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.
What is the map on DLA303?
DLA303 runs a procedural map of size 3,000 with seed 2119474038, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does DLA303 wipe, and on what schedule?
Once a month DLA303 wipes, with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 28 days 5 hours ago.
On DLA303, what happens on wipe day?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Which lists on Rust Data hold DLA303, and which filters?
On Rust Data, DLA303 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.
How should you read the server tags on DLA303?
The game's server browser reads these tags from DLA303: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into DLA303?
Enter client.connect 73.169.101.163:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.