TeddyServer

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 13d ago · 117.5.142.30:28015

Abstract

We describe the public Rust server TeddyServer, reached at 117.5.142.30:28015. It is offline at the last check, against a seven-day mean of 0¹. It ranks #12,874 of all servers, the top 60%. It last wiped 13d ago on a published biweekly schedule; the next wipe is expected Thursday 29 October, 12:34 UTC, its biweekly schedule tag.

Keywordsbiweekly wipes modded carbon

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	1/100	1% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#12,874	top 60%
Last wipe	13d ago	biweekly schedule
Next wipe³	5h	Thu 29 Oct, 12:34 UTC

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 memory⁴. 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

The server stands in the top 60% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: from its schedule tag

The next wipe is expected Thursday 29 October, 12:34 UTC, in 5h. Its biweekly schedule tag (low confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Usual gap	7.5 days	between real wipes
On rhythm	0%	of its recent wipes
Wipe-day peak	1	players, last three wipes
Crowd held	0%	else halves by day 10

Table 3: Coming wipes, as expected.

When (UTC)	In	Kind
Thu 29 Oct, 12:34	5h	its own schedule
Thu 5 Nov, 19:00	7d 11h	force wipefw
Thu 12 Nov, 12:34	14d 5h	its own schedule
Thu 26 Nov, 12:34	28d 5h	its own schedule
Thu 3 Dec, 19:00	35d 11h	force wipefw
Thu 10 Dec, 12:34	42d 5h	its own schedule

Thu 15 OctMon 12 OctFri 9 Oct

Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

5.2History

Table 4: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Thu 15 Oct, 12:3413d ago	1	–	running	1
Mon 12 Oct, 11:2116d ago	1	–	3.1 d	1
Fri 9 Oct, 09:2519d ago	1	–	3.1 d	1
Fri 25 Sep, 13:4033d ago	1	–	13.8 d	0
Sun 13 Sep, 16:1945d ago	1	halved by day 10	11.9 d	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. 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 5: The map: Procedural Map.

Table 5: The server's published settings.

Address	`117.5.142.30:28015`
Region	–
Max players	100
Group limit	8, the default
Wipe schedule	biweekly
Last wipe	15 Oct 2026, 12:34 UTC
Hostname	–
First seen	13 Sep 2026
Map	Procedural 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 browse modded Rust servers [2] and next Rust wipe times [3].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
Friendly Seattle: No KOS \| Chill \| Noob FriendlyNA · groups of 8+ · biweekly · 42 on average	30/100
［JP］初心者PVPサーバー｜RaidTime・ EventsEA · groups of 10+ · biweekly · 16 on average	8/100
СЛАБЫЕ РЫЦАРИ \|Vanilla+\|Events\|FPS+\|26.10EU · groups of 50+ · biweekly · 9 on average	3/200
RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮEU · groups of 8+ · biweekly · 8 on average	5/200
Rust Empires II - Roleplay/RP friendly, Cities, PVE, No KOS outgroups of 8+ · biweekly · 5 on average	4/50
Fudge Begynderserver(Casual Beta:Ticket on discord for access)groups of 8+ · biweekly · 4 on average	0/50

Appendix AQuick answers

From the figures on this page.

About the server

A.1In which location is TeddyServer based?

There is no region published for TeddyServer. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 117.5.142.30:28015.

A.2What is the online status and reliability of TeddyServer?

TeddyServer is currently offline, with the last sighting 13 days 15 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 13 September 2026.

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

Rust network protocol 2634 and build 167781 is the version that TeddyServer runs, on Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.4What schedule does TeddyServer follow for wipes?

The prediction follows the tag, as TeddyServer's recorded wipes are too few to confirm its schedule. On Thursday 29 October at 12:34 UTC the next wipe is expected. 13 days 18 hours have passed since the current world was generated. A fortnightly wipe schedule appears in its tags.

A.5How would you describe wipe day on TeddyServer?

Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 1 hours after the latest wipe. For 0% of recent wipes, the population did not fall below half the peak before the next wipe. In the other cases, the population fell below half by day 10.

Population

A.6What position does TeddyServer occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts TeddyServer at #12,874, within the top 60% of ranked servers.

A.7What is the population level of TeddyServer?

At this moment TeddyServer is offline, having last been seen 13 days 15 hours ago.

Tags and filters

A.8What is the meaning of the tags on TeddyServer?

Tags from TeddyServer, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): 100 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs167781 (Build): The game build is 167781; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^b (Biweekly): Wipes take place once a fortnight; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; ^y (Carbon): The plugin framework is Carbon. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can TeddyServer be found among the Rust Statistics lists and filters?

The Rust Statistics lists that TeddyServer fits are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Rules, settings, map

A.10Under what rules and settings does TeddyServer operate?

No gather rate appears in the name of TeddyServer. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gather, build and raid: the standard game. Players may raid and fight one another. Plugins or settings change the game; the browser files it under Modded. Carbon plugins are running. VAC is active: that is Valve's anti-cheat.

A.11On which map does TeddyServer take place?

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

Connection

A.12What is the process for joining TeddyServer?

Enter client.connect 117.5.142.30: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 mp100,ptrak,$r?,v2634,^z,^y,^b,gmrust,cs167781,ts8.

Table 7: The server's tags and their meanings.

Tag	Meaning
Game
`gmrust`	Game mode. Survival on standard Rust rules.
`mp100`	Max players. 100 slots are available.
`ts8`	Group limit. The team cap is 8, which is the game default.
`v2634`	Protocol. The game protocol is 2634; your client must match it to join.
`cs167781`	Build. The game build is 167781.
`ptrak`	Networking. Networking runs on RakNet, the game's standard layer.
`$r?`	Region code. No region code is set.
Wipe schedule
`^b`	Biweekly. Wipes take place once a fortnight.
Mods and access
`^z`	Modded. The game is altered by plugins or settings, so it is listed as Modded.
`^y`	Carbon. The plugin framework is Carbon.

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]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.