Telegram RegisterThe public register of Telegram
Telegram profile photo for 足球⚽️救生艇✈️

Channel

足球⚽️救生艇✈️

@sadad5a5d

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

147subscribers

-5 since we began measuring on 15 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003327546546
TypeChannel
Username@sadad5a5d
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded15 August 2026
Last confirmed live12 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/sadad5a5d

Topic

Gambling & betting — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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

147152149.515 August 2026 — 152 subscribers15 August 2026 — 152 subscribers16 August 2026 — 151 subscribers31 August 2026 — 150 subscribers1 October 2026 — 148 subscribers12 October 2026 — 147 subscribers15 August 202612 October 2026
6 measurements spanning 59 days, net -5. 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 146–153 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 15:55147-1
1 Oct 2026, 03:57148-2
31 Aug 2026, 13:55150-1
16 Aug 2026, 15:46151-1
15 Aug 2026, 03:30152no change
15 Aug 2026, 03:16152first reading

Engagement

20 posts held, back to 13 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

10 Aug 2026, 00:43 UTC9 viewsread 15 August 2026

智利甲 05:30 完 卡拉雷聯 1-2 高路高路 高路高路-0.5/1✅✅✅ 巴西甲 06:30 完 法林明高 1-0 維多利亞 法林明高 上半場-0.5/1✅✅✅

9 Aug 2026, 13:03 UTC10 viewsread 15 August 2026

智利甲 05:30 卡拉雷聯 - 高路高路 高路高路-0.5/1 巴西甲 06:30 法林明高 - 維多利亞 法林明高 上半場-0.5/1

9 Aug 2026, 04:27 UTC11 viewsread 15 August 2026

香港貼士分享派錢飛🚀 關注區,跟區 連紅中 https://t.me/+RxppB9NnCrJkN2Zl

12 Jun 2026, 21:02 UTC79 viewsread 15 August 2026

世界盃 03:00 完 加拿大 1-1 波斯尼亞 全场角8.5大✅✅✅ 參考波膽0-0 0-1 1-1✅✅✅

12 Jun 2026, 13:36 UTC80 viewsread 15 August 2026

世界盃 03:00 加拿大 - 波斯尼亞 全场角8.5大 參考波膽0-0 0-1 1-1

12 Jun 2026, 04:00 UTC78 viewsread 15 August 2026

世界盃 03:00 完 墨西哥 2-0 南非 墨西哥-1/1.5✅✅✅ 世界盃 10:00 完 南韓(中) 2-1 捷克 全場角8.5大✅✅✅

11 Jun 2026, 13:09 UTC70 viewsread 15 August 2026

世界盃 03:00 墨西哥 - 南非 墨西哥-1/1.5 世界盃 10:00 南韓(中) - 捷克 全場角8.5大

20 May 2026, 22:10 UTC124 viewsread 15 August 2026

瑞典超 01:00 完 加爾斯 2-0 哈馬比 全場小2.5✅✅✅ 歐霸盃 03:00 完 費雷堡(中) 0-3 阿士東維拉 全場小2.5❌

20 May 2026, 13:43 UTC113 viewsread 15 August 2026

瑞典超 01:00 加爾斯 - 哈馬比 全場小2.5 歐霸盃 03:00 費雷堡 - 阿士東維拉 全場小2.5

18 May 2026, 21:17 UTC112 viewsread 15 August 2026

英超 03:00 完 阿仙奴 1-0 般尼 全場角10.5小✅✅✅

17 May 2026, 21:48 UTC107 viewsread 15 August 2026

西甲 01:00 完 西維爾 0-1 皇家馬德里 皇家馬德里-0/0.5✅✅✅ 法甲 03:00 完 利爾 0-2 歐塞爾 全場大2.5/3❌

Showing the 12 most recent of 20 posts we hold for @sadad5a5d. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“足球⚽️救生艇✈️” (@sadad5a5d), 147 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/sadad5a5d.

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.