Telegram RegisterThe public register of Telegram
Telegram profile photo for 野寻·长沙活动公告

Channel

野寻·长沙活动公告

@chasecs_hdgg

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

8,882subscribers

+3,278 since we began measuring on 25 September 2026

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

Register entry

Telegram ID-1002341814232
TypeChannel
Username@chasecs_hdgg
Description👤 唯一管理: @chase_jz 🤖 作业投稿: @chasecsxc_bot ——————————— 长沙野寻 · 群组目录 狼友大群: @chasecs_jlq 老师榜单: @chasecs_lsda 精选榜单: @chasecs_lsjx 报告榜单: @chasecs_zypj 榜单导航: @chasecs_bddh ❤️一键关注所有频道: https://t.me/addlist/-vR7658WWxY5OTVh
Created18 December 2024 — measured — dated from the channel’s first post
First recorded25 September 2026
Last confirmed live9 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/chasecs_hdgg

Topic

Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 12 October 2026 and assigned it the closest of 31 fixed categories, at 77% 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 in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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
@chasecs_hdgg/1100 · this entry25 Sept 2026, 10:07 UTC@chasecs_lsda/163425 Sept 2026, 10:07 UTC1.00under a minute
@chasecs_hdgg/1190 · this entry1 Nov 2026, 08:13 UTC@chasecs_lsda/24131 Nov 2026, 08:13 UTC1.00under a minute
@chasecs_hdgg/1191 · this entry2 Nov 2026, 08:00 UTC@chasecs_lsda/24262 Nov 2026, 08:00 UTC1.00under a minute
@chasecs_hdgg/1192 · this entry3 Nov 2026, 08:00 UTC@chasecs_lsda/24333 Nov 2026, 08:00 UTC1.00under a minute
@chasecs_hdgg/1193 · this entry4 Nov 2026, 08:00 UTC@chasecs_lsda/24404 Nov 2026, 08:00 UTC1.00under a minute
@chasecs_hdgg/1196 · this entry6 Nov 2026, 07:18 UTC@chasecs_lsda/24726 Nov 2026, 07:18 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@chasecs_lsda9 (8/8 hand-verifiable sample passed)1.00under a minute@chasecs_lsda (6–3)

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. 6 of the 6 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 37 comparable posts for this entry, running 10 September 2026 to 12 November 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @chasecs_hdgg — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 13 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

5,6049,1417,372.525 September 2026 — 5,604 subscribers4 October 2026 — 5,666 subscribers10 October 2026 — 6,713 subscribers14 October 2026 — 8,691 subscribers17 October 2026 — 9,141 subscribers20 October 2026 — 9,098 subscribers23 October 2026 — 9,078 subscribers27 October 2026 — 9,046 subscribers30 October 2026 — 9,001 subscribers2 November 2026 — 8,976 subscribers6 November 2026 — 8,972 subscribers9 November 2026 — 8,882 subscribers8,88225 September 20269 November 2026
12 measurements spanning 45 days, net +3,278. 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 5,073–9,672 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Nov 2026, 09:398,882-90
6 Nov 2026, 05:408,972-4
2 Nov 2026, 18:478,976-25
30 Oct 2026, 13:369,001-45
27 Oct 2026, 05:119,046-32
23 Oct 2026, 19:419,078-20
20 Oct 2026, 10:289,098-43
17 Oct 2026, 11:169,141+450
14 Oct 2026, 04:218,691+1,978
10 Oct 2026, 09:376,713+1,047
4 Oct 2026, 02:385,666+62
25 Sept 2026, 17:225,604first reading

Engagement

42 posts held, back to 18 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 22 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.52%
avg views ÷ 8,882 subscribers
Avg views / post
401
36 posts measured
Reaction rate
0.19%
reactions ÷ views · ER floor
Posts in window
36
of 42 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 4 of 36 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 13 November 2026
Posts held42 (18 December 2024 – 13 November 2026)
Views total14,452
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 13:13 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
110
Links
101

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

Reaction mix

3 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3100.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 4 of the 42 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 42 most recent posts we hold, published 18 December 2024 to 13 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: 1 of 36 posts held from the last 30 days (2.78%) 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).

13 Nov 2026, 08:00 UTC54 viewsread 13 November 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H179380241728 🎰 甜辣辣不限次数P半价来了哦 ⚠️ 抽奖说明: 中奖后请24小时内联系可爱的野寻•橘子( @chase_jz )无出击意向不要参与 在3天内完成出击 作业报告向 @chasecsxc_bot 提交,请大家用心,真诚交流!别爬楼!别刷屏! 💁 参与情况:72达标 / 96报名 🔋 人品加成:190票 ⚡️× 9 🎅 联系领奖:野寻·橘子 1. Jibo⚡️⚡️⚡️ 奖品:甜辣椒P半价卷 祝大家心想事成好运连连!

13 Nov 2026, 07:09 UTC60 viewsread 13 November 2026
Photo

🎰 柚子的半价福利 📮 参与条件: 🌏️ 归属地 湖南,湖北 🪪 必须设置用户名 🎫 加入-柚子的世界 🎫 加入-野寻·长沙学生交流群 └ 🎟️ 发言数大于 38 条 🎫 加入-野寻·长沙活动公告 🎫 加入-野寻·长沙修车档案 🎫 加入-野寻 长沙打卡通告群 └ 🔑 发送口令﹝野寻长沙福利多多﹞ ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 柚子P半价卷 × 1 ⚠️ 抽奖说明: 中奖后请24小时内联系可爱的野寻•橘子( @chase_jz )无出击意向不要参与 在3天内完成出击 作业报告向 @chasecsxc_bot 提交,请大家用心,真诚交流!别爬楼!别刷屏! 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年11月25日 16时00分00秒

12 Nov 2026, 10:06 UTC346 viewsread 13 November 2026
Photo

🎰 苍老师的半价福利哦 📮 参与条件: 🌏️ 归属地 湖南,湖北 🪪 必须设置用户名 🎫 加入-苍老师的频道 🎫 加入-野寻·长沙学生交流群 └ 🎟️ 发言数大于 38 条 🎫 加入-野寻·长沙活动公告 🎫 加入-野寻·长沙修车档案 🎫 加入-野寻 长沙打卡通告群 └ 🔑 发送口令﹝野寻长沙福利多多﹞ ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 苍老师P半价 × 1 ⚠️ 抽奖说明: 中奖后请24小时内联系可爱的野寻•橘子( @chase_jz )无出击意向不要参与 在3天内完成出击 作业报告向 @chasecsxc_bot 提交,请大家用心,真诚交流!别爬楼!别刷屏! 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年11月23日 16时00分00秒

11 Nov 2026, 08:00 UTC310 views0 reactionsread 13 November 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H179345066335 🎰 野寻长沙携宋婉儿老师双11白嫖现金福利大放送 ⚠️ 抽奖说明: 中奖后请24小时内联系可爱的野寻•橘子( @chase_jz )无出击意向不要参与 在3天内完成出击 作业报告向 @chasecsxc_bot 提交,请大家用心,真诚交流!别爬楼!别刷屏! 💁 参与情况:76达标 / 144报名 🔋 人品加成:640票 ⚡️× 9 🎅 联系领奖:野寻·橘子 1. Xkqvyt Htcko⚡️× 9 奖品:现金红包88.8CNY 2. 浔野⚡️× 9 奖品:现金红包68.8CNY 3. 小橘同学(岸版)⚡️× 9 奖品:现金红包18.8CNY 4. Tina Hickman⚡️× 9 奖品:现金红包18.8CNY 5. 梦芸hn⚡️× 9 奖品:现金红包18.8CNY 6. D zyyyyyyyy⚡️× 9 奖品:长沙热门🔥老师宋婉儿P半价卷 7.…

10 Nov 2026, 13:32 UTC326 viewsread 13 November 2026
Photo

🎰 野寻长沙水群现金红包大放送 📮 参与条件: 🌏️ 归属地 湖南,湖北 🪪 必须设置用户名 🎫 加入-野寻·长沙学生交流群 └ 🎟️ 发言数大于 388 条 🎫 加入-野寻·长沙活动公告 🎫 加入-野寻·长沙修车档案 🎫 加入-野寻 长沙打卡通告群 └ 🔑 发送口令﹝野寻长沙福利多多﹞ ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 现金红包188CNY × 1 💰️ 现金红包28CNY × 3 💰️ 现金红包388CNY × 1 💰️ 现金红包66CNY × 1 💰️ 现金红包88CNY × 1 ⚠️ 抽奖说明: 一周水群福利大放送只要发言388有机会中388现金大奖,请大家用心,真诚交流!别爬楼!别刷屏!禁止灌水 三字经 发现取消抽奖资格(可互相监督向我举报哈),中奖后请24小时内联系可爱的野寻•橘子( @chase_jz )领取奖励 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(…

10 Nov 2026, 13:04 UTC303 viewsread 13 November 2026
Photo

🎰 桃桃紫琪双飞福利大放送 📮 参与条件: 🌏️ 归属地 湖南,湖北 🪪 必须设置用户名 🎫 加入-紫琪的花园 🎫 加入-桃桃的秘密花园 🎫 加入-野寻·长沙学生交流群 └ 🎟️ 发言数大于 28 条 🎫 加入-野寻·长沙活动公告 🎫 加入-野寻·长沙修车档案 🎫 加入-野寻 长沙打卡通告群 └ 🔑 发送口令﹝野寻长沙福利多多﹞ ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 桃桃紫琪双飞300优惠卷 × 3 ⚠️ 抽奖说明: 中奖后请24小时内联系可爱的野寻•橘子( @chase_jz )无出击意向不要参与 在3天内完成出击 作业报告向 @chasecsxc_bot 提交,请大家用心,真诚交流!别爬楼!别刷屏! 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年11月20日 16时00分00秒

9 Nov 2026, 07:04 UTC401 viewsread 13 November 2026
Photo

🎰 可可半价福利来咯 📮 参与条件: 🌏️ 归属地 湖南,湖北 🪪 必须设置用户名 🎫 加入-野寻·长沙学生交流群 └ 🎟️ 发言数大于 28 条 🎫 加入-野寻·长沙活动公告 🎫 加入-野寻·长沙修车档案 🎫 加入-野寻 长沙打卡通告群 └ 🔑 发送口令﹝野寻长沙福利多多﹞ 🎫 加入-小可的外卖空间 ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 可可P的半价卷 × 1 ⚠️ 抽奖说明: 中奖后请24小时内联系可爱的野寻•橘子( @chase_jz )无出击意向不要参与 在3天内完成出击 作业报告向 @chasecsxc_bot 提交,请大家用心,真诚交流!别爬楼!别刷屏! 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年11月21日 16时00分00秒

8 Nov 2026, 14:41 UTC429 viewsread 13 November 2026
Photo

🎰 小草神艺欣半价福利来咯 📮 参与条件: 🌏️ 归属地 湖南,湖北 🪪 必须设置用户名 🎫 加入-长沙COS SM 三通(有房可上门) 🎫 加入-野寻·长沙学生交流群 └ 🎟️ 发言数大于 28 条 🎫 加入-野寻·长沙活动公告 🎫 加入-野寻·长沙修车档案 🎫 加入-野寻 长沙打卡通告群 └ 🔑 发送口令﹝野寻长沙福利多多﹞ ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 艺欣1小时不限次数半价卷(🉑三通🉑SM) × 1 ⚠️ 抽奖说明: 中奖后请24小时内联系可爱的野寻•橘子( @chase_jz )无出击意向不要参与 在3天内完成出击 作业报告向 @chasecsxc_bot 提交,请大家用心,真诚交流!别爬楼!别刷屏! 🔋 人品加成:⚡️× 9 规则 📅 开奖日期:(北京时间) 2026年11月19日 16时00分00秒

8 Nov 2026, 08:00 UTC381 viewsread 13 November 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H179325782462 🎰 诺浠半价福利来咯 ⚠️ 抽奖说明: 中奖后请24小时内联系可爱的野寻•橘子( @chase_jz )无出击意向不要参与 在3天内完成出击 作业报告向 @chasecsxc_bot 提交,请大家用心,真诚交流!别爬楼!别刷屏! 💁 参与情况:67达标 / 86报名 🔋 人品加成:289票 ⚡️× 9 🎅 联系领奖:野寻·橘子 1. 番茄 炒蛋⚡️× 9 奖品:诺浠P半价卷 祝大家心想事成好运连连!

7 Nov 2026, 15:52 UTC564 viewsread 13 November 2026
Photo

👑 野寻 HM 银河厅 👑 🌐 全球华人一站式品质赌场娱乐厅 🎰 热门电子游戏,丰富主题自由选择 🎲 多种经典玩法,加拿大28 ⚽️ 体育赛事同步,热门项目精彩不断 📱 手机电脑均可进入,操作简单、畅快体验 👤 专属客服在线,及时处理相关问题 🔥 好局开场,精彩翻牌 💎 高端场面,每一局都充满期待 👑 牌桌有输赢,野寻有排面 🥳🔥🔥🔥🤡 野寻 HM 银河厅 🐶🔥🔥💪🐶 野寻 hm7.cc 🎉🐶🐶🔥🤡 野寻·拾光 😍😍😍🥳😏 HM国际-泡泡

7 Nov 2026, 15:51 UTC592 viewsread 13 November 2026
Photo

👑 野寻 HM 银河厅 👑 🌐 全球华人一站式品质赌场娱乐厅 🎰 热门电子游戏,丰富主题自由选择 🎲 多种经典玩法,加拿大28 ⚽️ 体育赛事同步,热门项目精彩不断 📱 手机电脑均可进入,操作简单、畅快体验 👤 专属客服在线,及时处理相关问题 🔥 好局开场,精彩翻牌 💎 高端场面,每一局都充满期待 👑 牌桌有输赢,野寻有排面 🥳🔥🔥🔥🤡 野寻 HM 银河厅 🐶🔥🔥💪🐶 野寻 hm7.cc 🎉🐶🐶🔥🤡 野寻·拾光 😍😍😍🥳😏 HM国际-泡泡

6 Nov 2026, 08:00 UTC401 viewsread 13 November 2026
Photo

🎉🎉🎉 开奖通知 🎉🎉🎉 🔖 防伪编号:H179301703317 🎰 洛水嫩妹的半价来咯 ⚠️ 抽奖说明: 中奖后请24小时内联系可爱的野寻•橘子( @chase_jz )无出击意向不要参与 在3天内完成出击 作业报告向 @chasecsxc_bot 提交,请大家用心,真诚交流!别爬楼!别刷屏! 💁 参与情况:93达标 / 116报名 🔋 人品加成:371票 ⚡️× 9 🎅 联系领奖:野寻·橘子 1. 一期⚡️× 9 奖品:洛水P半价卷 祝大家心想事成好运连连!

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

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

“野寻·长沙活动公告” (@chasecs_hdgg), 8,882 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/chasecs_hdgg.

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.