Telegram RegisterThe public register of Telegram
Telegram profile photo for 122体育-福利频道

Channel

122体育-福利频道

@QSTY9777

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry

6,807subscribers

-4,083 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002395903795
TypeChannel
Username@QSTY9777
Description专属客服 @qsty999999 双向联系 @qs999999bot 注册网址 1221966.com
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 November 2026
Measurements held42
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/QSTY9777

Topic

Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 6 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@qs79999/99419 Jul 2026, 09:16 UTC@QSTY9777/1186 · this entry19 Jul 2026, 09:16 UTC1.00under a minute
@qs79999/99522 Jul 2026, 09:02 UTC@QSTY9777/1187 · this entry22 Jul 2026, 09:02 UTC1.00under a minute
@qs79999/99925 Jul 2026, 09:20 UTC@QSTY9777/1191 · this entry25 Jul 2026, 09:20 UTC1.00under a minute
@qs79999/100328 Jul 2026, 08:19 UTC@QSTY9777/1195 · this entry28 Jul 2026, 08:19 UTC1.00under a minute
@qs79999/100430 Jul 2026, 09:34 UTC@QSTY9777/1196 · this entry30 Jul 2026, 09:34 UTC1.00under a minute
@qs79999/10071 Aug 2026, 10:11 UTC@QSTY9777/1199 · this entry1 Aug 2026, 10:11 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@qs799997 (7/7 hand-verifiable sample passed)1.00under a minute@qs79999 (4–3)
@qsty7797 (7/7 hand-verifiable sample passed)1.00under a minute@qsty779 (4–3)
@qs79997 (7/7 hand-verifiable sample passed)1.00under a minute@qs7999 (4–3)
@qs779997 (7/7 hand-verifiable sample passed)1.00under a minute@qs77999 (4–3)
@qsty7997 (7/7 hand-verifiable sample passed)1.00under a minute@qsty799 (7–0)
@qsty79997 (7/7 hand-verifiable sample passed)1.00under a minute@qsty7999 (7–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 30 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 8 comparable posts for this entry, running 19 July 2026 to 5 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 7, the earliest publisher we hold is @qs77999. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 6 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

6,80710,8908,848.56 August 2026 — 10,890 subscribers7 August 2026 — 10,885 subscribers8 August 2026 — 10,845 subscribers9 August 2026 — 10,817 subscribers10 August 2026 — 10,799 subscribers11 August 2026 — 10,763 subscribers12 August 2026 — 10,733 subscribers13 August 2026 — 10,704 subscribers14 August 2026 — 10,681 subscribers15 August 2026 — 10,661 subscribers17 August 2026 — 10,613 subscribers18 August 2026 — 10,594 subscribers19 August 2026 — 10,593 subscribers20 August 2026 — 10,586 subscribers21 August 2026 — 10,583 subscribers23 August 2026 — 10,563 subscribers24 August 2026 — 10,523 subscribers25 August 2026 — 10,514 subscribers27 August 2026 — 10,507 subscribers28 August 2026 — 10,503 subscribers29 August 2026 — 10,471 subscribers30 August 2026 — 10,408 subscribers31 August 2026 — 10,384 subscribers1 September 2026 — 10,364 subscribers2 September 2026 — 10,323 subscribers3 September 2026 — 10,303 subscribers5 September 2026 — 10,248 subscribers8 September 2026 — 10,135 subscribers11 September 2026 — 9,803 subscribers15 September 2026 — 9,214 subscribers25 September 2026 — 7,997 subscribers4 October 2026 — 7,513 subscribers10 October 2026 — 7,358 subscribers14 October 2026 — 7,234 subscribers17 October 2026 — 7,176 subscribers20 October 2026 — 7,137 subscribers23 October 2026 — 7,041 subscribers26 October 2026 — 6,964 subscribers29 October 2026 — 6,914 subscribers31 October 2026 — 6,886 subscribers4 November 2026 — 6,838 subscribers6 November 2026 — 6,807 subscribers6 August 20266 November 2026
42 measurements spanning 92 days, net -4,083. 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 6,195–11,502 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)SubscribersChange
6 Nov 2026, 23:096,807-31
4 Nov 2026, 03:546,838-48
31 Oct 2026, 18:596,886-28
29 Oct 2026, 04:316,914-50
26 Oct 2026, 00:386,964-77
23 Oct 2026, 05:397,041-96
20 Oct 2026, 01:417,137-39
17 Oct 2026, 00:567,176-58
14 Oct 2026, 08:507,234-124
10 Oct 2026, 21:547,358-155
4 Oct 2026, 23:167,513-484
25 Sept 2026, 21:567,997-1,217
15 Sept 2026, 14:199,214-589
11 Sept 2026, 12:159,803-332
8 Sept 2026, 22:3810,135-113
5 Sept 2026, 15:0010,248-55
3 Sept 2026, 15:2110,303-20
2 Sept 2026, 06:5310,323-41
1 Sept 2026, 04:4610,364-20
31 Aug 2026, 02:5710,384first reading

Engagement

31 posts held, back to 19 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 49 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.2%
avg views ÷ 6,807 subscribers
Avg views / post
895
9 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
9
of 31 held

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 1 of 9 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 November 2026
Posts held31 (19 July 2026 – 4 November 2026)
Views total8,057
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 01:19 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.

What this channel posts

Photos
53
Videos
4
Links
19

Lifetime counters from Telegram’s own channel header, read 7 November 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.

Video runtime
12m 30s
Average length
1m 47s

Measured directly from 7 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 reactions 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 19 July 2026 to 4 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 9 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

4 Nov 2026, 15:59 UTC15 viewsread 7 November 2026
Photo

电子区再传喜讯! 以为是一份,结果直接 双份 会员 "ys***11" 霸气开启 #PG电子 ❌ #PP电子 跨场馆双线收割,两头开花! 😀【 #日月星辰】 极速爆奖,欧气满格! 😀 【#麻将大胜3 - 黑金龙耀】 斩获 3x Black Scatter,爆发 🎰🎰🎰🎰❌ 超高倍率! 最终 🧐😒😏😀 惊喜顺利入袋! 大王牌场馆同时放大招,彩池彻底被洗劫!这哪里是玩游戏,简直是在提款! 😀 专属客服: @qsty999999 😀 双向联系: @qs999999bot 🌐注册网址: 1221966.com 免实名 免绑卡 免手机号 每日提款无上限 巨额无忧 😀😀😀😀😀😀😀😀😀😀

31 Oct 2026, 10:29 UTC815 viewsread 7 November 2026
Photo

充值 4110 人民币 出款 65230 USDT #PP电子 #极速糖果超级闪耀 20一拉 爆了 🙂☹️🙂😢😃 ▪️▪️▫️▪️▫️ 倍 盈利🧐😢🙂🙂😃 😀 专属客服: @qsty999999 😀 双向联系: @qs999999bot 🌐注册网址: 1221966.com 免实名 免绑卡 免手机号 每日提款无上限 巨额无忧 😀😀😀😀😀😀😀😀😀😀

31 Oct 2026, 10:28 UTC784 viewsread 7 November 2026
Photo

拒绝内卷,保持松弛感 还在被“压力”、“内卷”、“焦虑”追着跑吗? 那些加不完的班、甩不掉的焦虑、放不下的压力…… 不如统统打包,扔进垃圾桶!! 既然世界太吵,那就给自己按下📱 “暂停键” 来 😀😀😀😀😀的「快乐贩卖机」,没有繁琐的操作,不必费心研究复杂策略。 😀 随手一点,极速响应,让简单的快乐触手可及。 🥺👍⚡️🤯👍😞😳😀 无拘无束,想停就停,想玩就玩。这才是属于你的自由节奏。 🌐注册网址: 1221966.com 免实名 免绑卡 免手机号 每日提款无上限 巨额无忧 😀😀😀😀😀😀😀😀😀😀

29 Oct 2026, 16:08 UTC≈1,480 viewsread 7 November 2026
Photo

看懂好路,路不再难走! 🙈😁😁😁 总是看不懂牌路?长龙、单跳、辅助路,看得眼花缭乱❓ 精选三大看路技巧,轻松解读真人牌路! ❓ 长龙怎么追? ❓ 单跳怎么抓? ❓ 辅助路怎么看? 好路不难懂,关键是看对方法! ☺️☺️☺️ 好路帮你理清局势,理性判断才是常胜之道! 😀 专属客服: @qsty999999 😀 双向联系: @qs999999bot 🌐注册网址: 1221966.com 免实名 免绑卡 免手机号 每日提款无上限 巨额无忧 😀😀😀😀😀😀😀😀😀😀

29 Oct 2026, 15:54 UTC≈1,480 viewsread 7 November 2026
Photo

😄 风起时顺势,风平时沉淀 会员“15***97”在BG真人转战《骰宝》与《百家乐》,稳扎稳打 喜提 😀😀😀😀 真正的赢家,从来懂得让时间变现 🥰 在真人视讯的桌台前,没有浮躁,只有对节奏的精准把握 😀 《骰宝》 布局掌控 😀 《百家乐》 顺势追赢 😀 专属客服: @qsty999999 😀 双向联系: @qs999999bot 🌐注册网址: 1221966.com 免实名 免绑卡 免手机号 每日提款无上限 巨额无忧 😀😀😀😀😀😀😀😀😀😀

27 Oct 2026, 19:19 UTC714 viewsread 7 November 2026

神秘彩金已派发! 您的账号收到神秘彩金,快登录账号领取属于你的奖励吧! 请及时登录领取,以免彩金过期,谢谢!

27 Oct 2026, 19:11 UTC≈1,380 views0 reactionsread 7 November 2026
Photo

宝刀未老!经典 #老虎机 《#虎虎生财》大破金库! 🤯 谁说旧游戏没有新惊喜?事实证明,经典永远是经典! 😰恭喜会员 "ga***88" 在 《虎虎生财》一把拉出“百搭满屏”,猛虎发威! 🥺 🍓🍓🍓🍓🍓🍓🍓 巨额奖金直接入账! “老”玩法,新突破,财富密码依旧稳固! 🌟 无论新老玩家,只要敢玩,下一个被财神爷“点名”的可能就是你! 😀 专属客服: @qsty999999 😀 双向联系: @qs999999bot 🌐注册网址: 1221966.com 免实名 免绑卡 免手机号 每日提款无上限 巨额无忧 😀😀😀😀😀😀😀😀😀😀

27 Oct 2026, 19:10 UTC695 viewsread 4 November 2026
Photo

如果在波胆竞猜中,每一次尝试都有“底线保障”,会是怎样一种体验? 💵 答案就是:放开手脚,玩得更纯粹、更过瘾! 🔓每个注单都像上了“双保险”,无论输赢都有单单回馈: 💵盈利加码 ▪️▪️ 彩金照拿 💵亏损补贴 ▪️▫️▪️ 不必灰心,平台直接补贴 😋 告别提心吊胆!不拼运气,只拼心态! 🌐注册网址: 1221966.com

27 Oct 2026, 19:10 UTC694 viewsread 4 November 2026
Photo

谁说免费才能爆? 好运说来就来! 谁能想到,一次超级游转竟然能带来这么大的惊喜! 会员「nb***4k」仅凭😉😉😉开启超级游转,直接爆赢😀😀😀 超级倍数火力全开,中奖画面瞬间刷屏!最终狂获 ▪️▪️▪️▫️▫️▫️▫️ 小额开局也能留下惊人战绩!每一次游戏都有不同的结果,幸运无法预测,但这份惊喜值得记录! 好运总有意想不到的打开方式,极速糖果的惊喜不止于此! 😀 专属客服: @qsty999999 😀 双向联系: @qs999999bot 🌐注册网址: 1221966.com 免实名 免绑卡 免手机号 每日提款无上限 巨额无忧 😀😀😀😀😀😀😀😀😀😀

29 Aug 2026, 09:42 UTC≈3,120 viewsread 29 August 2026
Photo

欢迎来到 😌😳😁😞🙃 😀 真正的赢家,不赌一时之运,只赢全局之势 😀 ❤️‍🔥所谓全局,不只是眼前的一场精彩 ✨更是面对不同选择时,始终拥有自己想要的那一种。 🤣球速体育 🔝😃大真人场馆 ➡️🌟 😳🌟🌟 ➡️🌟 ❤️🌟🌟 ➡️🌟 ❤️🌟🌟 ➡️🌟 ❤️🌟🌟 ➡️🌟 ❤️🌟🌟 ➡️🌟 ❤️🌟🌟 😱 经典、人气、多元体验,一站汇聚。不同场馆,各有精彩;更多选择,只为让你找到更合心意的体验。 ✅电子, 真人无审核包出款. ✅ U存U提出款无上限 日出亿U. 1️⃣首存活动 2️⃣双重日存彩金128888+4688(每日存款每日送) 3️⃣豪礼赠送:奔驰e300,劳力士手表,高端嫩模 4️⃣大额出款额外奖励 5️⃣双重签到彩金16888+3888(天天签到,天天钱到) 6️⃣体育周流水活动 7️⃣电子周流水活动 8️⃣百家乐周流水活动 9️⃣棋牌周流水活动 🔟vip等级平移 1️⃣1️⃣好友邀请送红包 笔笔存送!每…

27 Aug 2026, 10:08 UTC≈5,880 viewsread 29 August 2026

😀球速体育永久域名: 983qs.cc 😄😄😄😄😄😄😃@qsty999999 🌐备用注册链接:https://gtrbwmx6.94qiusu.cc/r/xuet

27 Aug 2026, 06:22 UTC33 viewsread 29 August 2026
Photo

欢迎来到 😌😳😁😞🙃 🤓 甜蜜出击,好运真的会突然降临!❤️ 🌟 恭喜会员 "ls***00" 😃😄💳💳《甜心糖果大富翁》中甜蜜一路加码,惊喜一波接一波 💫单注最高爆出 🔠🤥7️⃣7️⃣2️⃣2️⃣7️⃣2️⃣🤥 💵幸运不断累积,喜提🤯⭐️⭐️⭐️⭐️⭐️⭐️⭐️🤯 💌 每一次甜蜜碰撞,都可能开启下一份惊喜,幸运时刻等你解锁! ✅电子, 真人无审核包出款. ✅ U存U提出款无上限 日出亿U. 1️⃣首存活动 2️⃣双重日存彩金128888+4688(每日存款每日送) 3️⃣豪礼赠送:奔驰e300,劳力士手表,高端嫩模 4️⃣大额出款额外奖励 5️⃣双重签到彩金16888+3888(天天签到,天天钱到) 6️⃣体育周流水活动 7️⃣电子周流水活动 8️⃣百家乐周流水活动 9️⃣棋牌周流水活动 🔟vip等级平移 1️⃣1️⃣好友邀请送红包 笔笔存送!每日存送! 不给提款的送你多少彩金也没有用📍 不管多大额度都给你出款…

Showing the 12 most recent of 31 posts we hold for @QSTY9777. 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.

Posts recorded as deleted after publishing

We recorded 4 posts on @QSTY9777 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
27 August 2026
Median time before seen missing
8 days
Seen missing in the last 30 days
0

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

Named by 69 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“122体育-福利频道” (@QSTY9777), 6,807 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/QSTY9777.

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.