Channel
@SHCTTY
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Domains linked from posts · Cite this entry
34,787subscribers
-9,431 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1003053766793 |
|---|---|
| Type | Channel |
| Username | @SHCTTY |
| Description | ➖➖➖➖➖➖➖➖➖➖➖ 永久冠名：山海财团 @SSSHHH 频道 @SHCTTTT 域名 SSSHHH.CC 🏆🏆【山海财团】🏆🏆 🏆🏆诚邀代理加入🏆🏆 🏆携手共进，扬帆起航🏆 九台｜开云｜爱游戏｜华体会｜乐鱼 米兰｜星空｜九 游｜ O D ｜MK ➖➖➖➖➖➖➖➖➖➖➖ |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/SHCTTY |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 00:43 | 34,787 | -371 |
| 10 Aug 2026, 21:23 | 35,158 | -2,934 |
| 10 Aug 2026, 00:02 | 38,092 | -6,054 |
| 8 Aug 2026, 20:31 | 44,146 | -47 |
| 7 Aug 2026, 23:51 | 44,193 | -8 |
| 7 Aug 2026, 00:43 | 44,201 | -17 |
| 6 Aug 2026, 19:46 | 44,218 | first reading |
31 posts held, back to 28 July 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 18 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 3 of 31 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 31 (28 July 2026 – 12 August 2026) |
| Views total | 556 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 20:59 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
2 reactions across 2 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 3 of the 31 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 28 July 2026 to 12 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
晚场⚽️精选 #推单 ————————— 欧洲超级杯 03:00 巴黎圣日耳曼 vs. 阿斯顿维拉 推荐：巴黎圣日耳曼 -0.5/1 ❤️ 南美解放者杯 06:00 帕尔梅拉斯 vs. 波特诺山丘 推荐：帕尔梅拉斯 -1/1.5 南美解放者杯 06:00 普拉腾斯 vs. 科金博联合 推荐：大 1.5/2 😀😀😀😀😀😀😀 🔈【九台导航】 SSSHHH.CC 🔈【招商热线】 @SSSHHH 🔈【官方频道】 @SHCTTTT
昨天推荐赛事，六中五！！！
晚场⚽️精选 #推单 ————————— 欧洲冠军联赛-资格赛 00:00 博多格林特 vs. 圣吉罗斯 推荐：圣吉罗斯 +1 欧洲冠军联赛-资格赛 00:00 萨巴赫 vs. 奥胡斯 推荐：萨巴赫 -0.5 欧洲冠军联赛-资格赛 02:15 布拉迪斯拉发 vs. 米亚尔比 推荐：布拉迪斯拉发 -0.5 ❤️ 欧洲冠军联赛-资格赛 02:15 采列 vs. 阿拉特亚美尼亚 推荐：采列 -1/1.5 欧洲冠军联赛-资格赛 02:30 格拉茨风暴 vs. 费内巴切 推荐：格拉茨风暴 +0.5/1 欧洲冠军联赛-资格赛 03:00 里昂 vs. 布拉格斯巴达 推荐：里昂 -1.5 ❤️ 😀😀😀😀😀😀😀 🔈【九台导航】 SSSHHH.CC 🔈【招商热线】 @SSSHHH 🔈【官方频道】 @SHCTTTT
昨天推荐赛事，三中二！！
晚场⚽️精选 #推单 ————————— 瑞典超级联赛 01:00 天狼星 vs. 布洛马波卡纳 推荐：天狼星 -1.5 ❤️ 瑞典超级联赛 01:00 瓦斯特拉斯 vs. 佐加顿斯 推荐：瓦斯特拉斯 +0.5/1 葡萄牙超级联赛 03:15 圣克拉拉 vs. 葡萄牙国民 推荐：大 2 😀😀😀😀😀😀😀 🔈【九台导航】 SSSHHH.CC 🔈【招商热线】 @SSSHHH 🔈【官方频道】 @SHCTTTT
昨晚推荐赛事，六中三！！
晚场⚽️精选 #推单 ————————— 葡萄牙超级联赛 01:00 波尔图 vs. 艾华卡 推荐：波尔图 -1.5/2 ❤️ 挪威超级联赛 01:15 克里斯蒂安松 vs. 莫尔德 推荐：莫尔德 -0.5/1 葡萄牙超级联赛 03:30 本菲卡 vs. 维塞乌 推荐：本菲卡 -2.5 葡萄牙超级联赛 03:30 吉维森特 vs. 里奥阿维 推荐：里奥阿维 +0.5 葡萄牙超级联赛 03:30 莫雷伦斯 vs. 布拉加 推荐：莫雷伦斯 +1 巴西甲级联赛 06:30 弗拉门戈 vs. 维多利亚 推荐：弗拉门戈 -1.5/2 ❤️ 😀😀😀😀😀😀😀 🔈【九台导航】 SSSHHH.CC 🔈【招商热线】 @SSSHHH 🔈【官方频道】 @SHCTTTT
晚场⚽️精选 #推单 ————————— 荷兰甲级联赛 00:45 前进之鹰 vs. 威廉二队 推荐：前进之鹰 -1 葡萄牙超级联赛 01:00 维多利亚吉马良斯 vs. 阿罗卡 推荐：维多利亚吉马良斯 -0.5 荷兰甲级联赛 02:00 PSV 埃因霍温 vs. 福图纳锡塔德 推荐：PSV 埃因霍温 -2/2.5 ❤️ 荷兰甲级联赛 03:00 阿尔克马尔 vs. 海牙 推荐：海牙 +1.5 巴西甲级联赛 03:00 格雷米奥 vs. 圣保罗 推荐：小 2/2.5 巴西甲级联赛 08:00 博塔弗戈RJ vs. 弗鲁米嫩塞RJ 推荐：小 2.5 ❤️ 😀😀😀😀😀😀😀 🔈【九台导航】 SSSHHH.CC 🔈【招商热线】 @SSSHHH 🔈【官方频道】 @SHCTTTT
昨天推荐赛事，六中五！！！
晚场⚽️精选 #推单 ————————— 挪威超级联赛 01:00 桑德菲杰 vs. KFUM奥斯陆 推荐：KFUM奥斯陆 +0.5 荷兰甲级联赛 02:00 坎布尔 vs. SBV精英 推荐：大 2.5/3 ❤️ 荷兰乙级联赛 02:00 埃门 vs. 罗达JC 推荐：大 3 德国乙级联赛 02:30 波鸿 vs. 柏林赫塔 推荐：柏林赫塔 +0/0.5 英格兰联赛杯 03:00 米德尔斯堡 vs. 雷克斯汉姆 推荐：米德尔斯堡 -0.5/1 ❤️ 葡萄牙超级联赛 03:15 埃斯托里尔 vs. 法马利康 推荐：法马利康 0 😀😀😀😀😀😀😀 🔈【九台导航】 SSSHHH.CC 🔈【招商热线】 @SSSHHH 🔈【官方频道】 @SHCTTTT
❤1
昨天推荐赛事，三中二！
晚场⚽️精选 #推单 ————————— 欧足联欧洲联赛-资格赛 01:45 PAOK沙朗历基 vs. 安德莱赫特 推荐：PAOK沙朗历基 -0.5/1 欧足联欧洲联赛-资格赛 03:00 本菲卡 vs. 哈茨 推荐：本菲卡 -2.5/3 ❤️ 巴西杯 07:00 维多利亚 vs. 巴拉纳竞技 推荐：维多利亚 0 😀😀😀😀😀😀😀 🔈【九台导航】 SSSHHH.CC 🔈【招商热线】 @SSSHHH 🔈【官方频道】 @SHCTTTT
Showing the 12 most recent of 31 posts we hold for @SHCTTY. 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.
Citation-graph rank — 53,332 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 14 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
One domainthis channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“世界杯｜五大联赛｜足球推单” (@SHCTTY), 34,787 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SHCTTY.
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.