Working its way up from the back of the class: #13,668 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 1,008 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 62% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Saturday 31 October, 04:05 UTC, in 3d 2h.
Its biweekly schedule tag · low confidence
Coming wipes
3d 2hSat 31 Oct, 04:05 UTC
8d 17hThu 5 Nov, 19:00 UTCFW
17d 2hSat 14 Nov, 04:05 UTC
31d 2hSat 28 Nov, 04:05 UTC
36d 17hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
No hourly players around its wipes yet.
Players each hour, from the hour of the wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 3 Oct, 04:05 UTC24d ago
–
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
TeddyServer leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 104.28.237.74:28015.
How reliable is TeddyServer, and is it up?
The server is down: TeddyServer is offline now, with the last sighting 20 days 4 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 1 October 2026, Rust Server Score saw it for the first time.
What Rust version is TeddyServer on?
You will find TeddyServer on Rust network protocol 2634 and build 167058, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does TeddyServer wipe its map?
The prediction follows its tag, because too few of TeddyServer's wipes are on record to confirm the schedule. Saturday 31 October at 04:05 UTC is the date set for its next wipe. 24 days 20 hours have passed since this world was made. Its tags say it wipes every two weeks.
Player numbers
Where does TeddyServer place in the wider field of Rust servers?
In the top 62% of all ranked servers, TeddyServer sits at #13,668 for player hours over the last seven days.
How many players does TeddyServer usually have?
TeddyServer is offline at the moment; the last time it was seen was 20 days 4 hours ago.
Tags and filters
What is meant by the tags on TeddyServer?
gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167058 (Build): Build number: 167058; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): Every two weeks it wipes; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here are the tags TeddyServer publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does TeddyServer appear in the Rust Server Score lists and filters?
These Rust Server Score lists count TeddyServer among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks.
Rules and settings
What settings and rules apply on TeddyServer?
Nothing in the name of TeddyServer states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Carbon. The server runs Valve's anti-cheat, VAC.
TeddyServer runs which map?
A procedural map, generated by the game, is what TeddyServer runs.
Connecting
How do you get onto TeddyServer?
Enter client.connect 104.28.237.74:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^z,^y,^b,gmrust,cs167058,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167058
BuildBuild number: 167058.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework here.
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.
A term to build on. Even marks across the subjects, from F to D.