Rust StatisticsWorking papers on every public Rust server · 34,406 players now

JohnDaWalrus

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 39d ago · 69.43.66.35:28015

Abstract

We describe the public Rust server JohnDaWalrus, reached at 69.43.66.35:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,305 of all servers. It last wiped 39d ago.

Keywordsrust server

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/5000% full
In the queue0no queue
Seven-day mean0peak –
Rank2#13,305no region published
Last wipe39d agono schedule published
Next wipe3–no wipe seen yet

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 4: The map: Procedural Map.
Table 3: The server's published settings.
Address69.43.66.35:28015
Region–
Max players500
Group limit8, the default
Wipe schedule–
Last wipe18 Sep 2026, 21:53 UTC
Hostname–
First seen18 Sep 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are busiest community rust servers [2] and Rust wipe forecast [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 534 on average248/275
Rustoria.co - EU MainEU · groups of 16+ · weekly · 322 on average21/250
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 321 on average16/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average170/200
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 277 on average64/200
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average37/100

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is JohnDaWalrus based?

A region is not published by JohnDaWalrus. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 69.43.66.35:28015.

A.2How reliable is JohnDaWalrus, and is it currently online?

Right now, JohnDaWalrus is offline, and the last time it was seen was 39 days 7 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. Its first appearance in Rust Statistics's records is 18 September 2026.

A.3What version of Rust is run on JohnDaWalrus?

Rust network protocol 2633 and build 164530 is the version that JohnDaWalrus runs, on Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.4On what cycle does JohnDaWalrus wipe?

Too few wipes by JohnDaWalrus have been recorded to determine the pattern. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. The current world has been running for 39 days 8 hours.

Population

A.5What position does JohnDaWalrus occupy in the ranking of Rust servers?

Ranked by player hours across seven days, JohnDaWalrus holds #13,305, in the top – of all ranked servers.

A.6How would you characterise the player activity on JohnDaWalrus?

The last recorded sighting of JohnDaWalrus was 39 days 7 hours ago; it is offline now.

Tags and filters

A.7What do the tags associated with JohnDaWalrus signify?

gmrust (Game mode): This is survival as standard Rust plays; mp500 (Max players): 500 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2633 (Protocol): Joining requires the same game version: protocol 2633; cs164530 (Build): The game build is 164530; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set: these are the tags JohnDaWalrus publishes, and the server browser reads them. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.8Where can JohnDaWalrus be found among the Rust Statistics lists and filters?

Rust community servers, measured are the Rust Statistics lists that JohnDaWalrus fits. You will find it on the server list filtered by: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Settings and map

A.9Under what rules and settings does JohnDaWalrus operate?

The name of JohnDaWalrus states no gather rate. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. It is a community server, as the browser's Community listing shows. VAC is active: that is Valve's anti-cheat.

A.10On which map does JohnDaWalrus take place?

A procedural map, generated by the game, is what JohnDaWalrus runs.

How to join

A.11How do you connect to JohnDaWalrus?

Enter client.connect 69.43.66.35:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp500,ptrak,$r?,v2633,gmrust,cs164530,ts8.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp500Max players. 500 slots are available.
ts8Group limit. The team cap is 8, which is the game default.
v2633Protocol. Joining requires the same game version: protocol 2633.
cs164530Build. The game build is 164530.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. No region code is set.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Busiest community rust servers. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.