Telegram RegisterThe public register of Telegram
Telegram profile photo for Noble Savage

Channel

Noble Savage

@noblesavage2023

On this record: Topic · Growth · Engagement · Citations · Cite this entry

1,787subscribers

-31 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001333964446
TypeChannel
Username@noblesavage2023
DescriptionNoble Savage Premier in 2 Weeks. Owenbenjamin.com #owenbenjamin #noblesavage #filmgrainstudios #unbearablesmedia #standup #comedy
Created11 February 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded23 September 2026
Last confirmed live23 September 2026
Measurements held13
On Telegramt.me/noblesavage2023

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 48% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

1,7871,8181,802.56 August 2026 — 1,818 subscribers9 August 2026 — 1,816 subscribers12 August 2026 — 1,812 subscribers16 August 2026 — 1,804 subscribers21 August 2026 — 1,803 subscribers25 August 2026 — 1,801 subscribers27 August 2026 — 1,800 subscribers31 August 2026 — 1,799 subscribers3 September 2026 — 1,798 subscribers7 September 2026 — 1,795 subscribers12 September 2026 — 1,789 subscribers15 September 2026 — 1,787 subscribers23 September 2026 — 1,787 subscribers6 August 202623 September 2026
13 measurements spanning 48 days, net -31. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,782–1,823 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Sept 2026, 15:591,787no change
15 Sept 2026, 21:371,787-2
12 Sept 2026, 05:411,789-6
7 Sept 2026, 21:201,795-3
3 Sept 2026, 05:581,798-1
31 Aug 2026, 04:171,799-1
27 Aug 2026, 20:331,800-1
25 Aug 2026, 04:231,801-2
21 Aug 2026, 13:441,803-1
16 Aug 2026, 01:571,804-8
12 Aug 2026, 09:021,812-4
9 Aug 2026, 16:221,816-2
6 Aug 2026, 10:471,818first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 23 September 2026 — this entry's latest reading, not the date you are reading this.

“Noble Savage” (@noblesavage2023), 1,787 subscribers as measured 23 September 2026. Telegram Register, tgregister.com/channel/noblesavage2023.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.