Offline 104.28.237.74:28015 checked 21d ago
TeddyServer
Connect
srv = rust.server("104.28.237.74: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 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Saturday 31 October, 04:05 UTC, in 2d 7h. # Its biweekly schedule tag · low confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 2d 7h | Sat 31 Oct, 04:05 UTC | wipe |
| 1 | 7d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 16d 7h | Sat 14 Nov, 04:05 UTC | wipe |
| 3 | 30d 7h | Sat 28 Nov, 04:05 UTC | wipe |
| 4 | 35d 22h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 5 | 44d 7h | Sat 12 Dec, 04:05 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 04:05 UTC25d ago | NaN | NaN | running | 1 |
# 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
- 104.28.237.74:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 3 Oct 2026, 04:05 UTC
- hostname
- –
- first seen
- 1 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 | Friendly Seattle: No KOS | Chill | Noob Friendly | NA · groups of 8+ · biweekly · 39 on average | 30/100 |
| 1 | ［JP］初心者PVPサーバー｜RaidTime・ Events | EA · groups of 10+ · biweekly · 17 on average | 0/100 |
| 2 | СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10 | EU · groups of 50+ · biweekly · 9 on average | 5/200 |
| 3 | RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ | EU · groups of 8+ · biweekly · 8 on average | 16/200 |
| 4 | Rust Empires II - Roleplay/RP friendly, Cities, PVE, No KOS out | groups of 8+ · biweekly · 5 on average | 5/50 |
| 5 | [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 | EA · no group limit · biweekly · 4 on average | 0/20 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TeddyServer rank?
Player hours over seven days put TeddyServer at #13,668, in the top 62% of the ranked set.
How full does TeddyServer run?
TeddyServer returns no live count at this refresh, having last been seen 21 days ago.
About the server
Which Rust version is TeddyServer on?
Rust network protocol 2634 and build 167058 on Windows is what TeddyServer runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TeddyServer, and is it up?
The latest sample has TeddyServer offline, with a last sighting 21 days ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 1 October 2026.
Where does TeddyServer sit?
There is no region published for TeddyServer. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 104.28.237.74:28015.
Settings and map
What rules and settings are recorded for TeddyServer?
You will not find a gather rate in the string TeddyServer. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has TeddyServer loaded?
TeddyServer runs a procedural map, which the game generates.
Wipe data
On what schedule does TeddyServer wipe?
The tag sets the prediction: TeddyServer has too few wipes on record to confirm its schedule. The schedule puts the next wipe on Saturday 31 October at 04:05 UTC. The world it runs now was generated 25 days 16 hours ago. A fortnightly wipe schedule is published in its tags.
Tags, lists
Which Rust Data filters and lists contain TeddyServer?
These Rust Data lists include TeddyServer: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks.
How should you read the server tags on TeddyServer?
Read by the game's server browser, the tags TeddyServer publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs167058 (Build): Build number: 167058; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^b (Biweekly): The cycle is fourteen days; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join TeddyServer?
Enter client.connect 104.28.237.74:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.