Telegram RegisterThe public register of Telegram
Telegram profile photo for 🅥武汉老师报告🅥

Channel

🅥武汉老师报告🅥

@wuhanhua2

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

17,644subscribers

-305 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002356991138
TypeChannel
Username@wuhanhua2
Description老师榜 @wuhanhua1 主群 @wuhanlou 聊天技术 @whlou6 报告频道 @wuhanhua2 投诉 @millyne1 修车驾校 @carlugui 黑车曝光 @hijackcar
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/wuhanhua2

Topic

Adult — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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 2 other registered channels. This entry also sits inside a group of 6 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@whlou4/500220 Aug 2026, 12:08 UTC@wuhanhua2/18602 · this entry20 Aug 2026, 12:08 UTC1.00under a minute
@wuhanhua2/18613 · this entry22 Aug 2026, 15:49 UTC@whlou4/530022 Aug 2026, 22:32 UTC1.006.7 hours
@whlou4/620231 Aug 2026, 11:09 UTC@wuhanhua2/18637 · this entry31 Aug 2026, 11:10 UTC1.0072 seconds
@whlou4/63151 Sept 2026, 14:40 UTC@wuhanhua2/18643 · this entry1 Sept 2026, 14:43 UTC1.003 minutes
@whlou4/63862 Sept 2026, 09:17 UTC@wuhanhua2/18649 · this entry2 Sept 2026, 09:18 UTC1.00under a minute
@whlou4/97704 Oct 2026, 07:39 UTC@wuhanhua2/19057 · this entry2 Nov 2026, 05:49 UTC1.0029 days
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
@whlou48 (8/8 hand-verifiable sample passed)1.003 minutes@whlou4 (6–2)
@wuhanhua117 (8/8 hand-verifiable sample passed)1.005 minutes@wuhanhua1 (16–1)

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. 4 of the 4 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 48 comparable posts for this entry, running 25 July 2026 to 15 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 6 channels, the one whose matching posts we hold earliest is @wuhanhua2 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 16 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 6 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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

17,24417,94917,596.517,6447 August 202616 November 2026
65 measurements spanning 101 days, net -305. 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 17,138–18,055 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
16 Nov 2026, 10:0217,644+7
12 Nov 2026, 20:4017,637+28
10 Nov 2026, 12:5017,609+37
8 Nov 2026, 22:5517,572+6
7 Nov 2026, 18:0917,566+6
6 Nov 2026, 18:2617,560+15
5 Nov 2026, 15:2017,545+14
4 Nov 2026, 18:0017,531-2
3 Nov 2026, 19:3017,533+25
2 Nov 2026, 20:3717,508+1
1 Nov 2026, 17:3617,507+3
31 Oct 2026, 15:3917,504+3
30 Oct 2026, 17:4617,501-1
29 Oct 2026, 18:4617,502+9
28 Oct 2026, 18:4917,493+10
27 Oct 2026, 19:0117,483+14
26 Oct 2026, 21:2517,469+5
25 Oct 2026, 20:5717,464-6
24 Oct 2026, 19:0817,470-11
23 Oct 2026, 20:0117,481first reading

Engagement

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

ERR · 30 days
2.81%
avg views ÷ 17,644 subscribers
Avg views / post
496
27 posts measured
Reaction rate
0.365%
reactions ÷ views · ER floor
Posts in window
27
of 60 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 11 of 27 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 17 November 2026
Posts held60 (25 July 2026 – 17 November 2026)
Views total13,380
Reactions total17
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 06:43 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
≈8,460
Videos
≈1,320
Links
≈8,920

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
4m 49s
Average length
14s

Measured directly from 21 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

58 reactions across 30 posts, in 3 distinct kinds. The most used accounts for 91.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤5391.4%
👍46.90%
🥰11.72%

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 33 of the 60 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 58 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 60 most recent posts we hold, published 25 July 2026 to 17 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 27 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).

17 Nov 2026, 01:56 UTC133 views1 reactionsread 17 November 2026
Photo

📱#微微(维族) 🌐#光谷 💴【学费】 #7p #12pp 🛫【联系】@Kalbenur0987654 🥂【双向】 📱【频道】 t.me/weiwei52011314 🍑【硬件】D/162cm/60kg/18 🫦【标签】#新人 #大胸 #嫩妹 #7p #舌 #光谷 ❓上榜管理 @millyne1 🛍技术交流 @whlou6 🕯武汉东湖 @whlou 🎉工兵优惠 @whlou7 💫学生群 @whbbb6 报告车评查找机器人:@vlchattbot

👍1

15 Nov 2026, 15:08 UTC441 views1 reactionsread 17 November 2026
Photo

📱#可可 🌐#洪山 #南湖 💴【学费】#10p #16pp 🛫【联系】@keke5201314888 🥂【双向】@kekexiaozhushoubot 📱【频道】 t.me/keke5201314111 ❤️【硬件】A+/167cm/49kg/22 🫦【标签】#洪山 #南湖 #10p #16pp #嫩妹 #69 #陪浴 报告车评查找机器人:@vlchattbot

👍1

15 Nov 2026, 00:55 UTC531 viewsread 17 November 2026
Forwarded from @whlou4

━━━━━━━━━━━━━━ 🌟 外围子轩评价🌟 ━━━━━━━━━━━━━━ 🏷 #外围# #2400 #御姐 👤 小琪外围: @wuqiqi9115 🔗 主页: https://t.me/whmqww123 ⭐️ 综合:★★★★★ 5/5 ├ 🎯 技能:★★★★★ 5/5 ├ 💗 情绪:★★★★★ 5/5 ├ 🏡 环境:★★★★★ 5/5 └ 📷 人照:★★★★★ 5/5 小琪外围安排的,这次想体验个车震的,小琪就安排了子轩,见面是真满意,人照对版,本人比照片好看,服务态度很好,值的一次体验。身材不错胸挺拔,逼紧致湿润,

14 Nov 2026, 09:51 UTC386 views3 reactionsread 17 November 2026
Forwarded from @wuhanhua1Photo

#高颜值 #洪山区 【熊猫】9T❤️ 🔰 武汉全裸9T会所|新店开业海选 🔰武汉全裸最大的门店海选SPA顶级服务莞式服务一条龙权威认证嫩妹 A套餐:顶级全裸9T(398/60分)🥰 全裸9T服务60分钟不限次数 💋 全场高颜值主打00后服务60分钟 🔥 多种特色服务|情趣丝袜免费提供, 🥤 茶水饮料糖果免费提供60分钟不限次 🔰 特色项目: 舌吻亲嘴、K推、毛推 阴推、鸳鸯浴、胸推、腿推、臀推、足推、制服诱惑、丝袜诱惑、角色扮演、COS、 毒龙、舔脚、抓龙筋、花式推法、指滑、舌滑、足交、乳交、艳舞、水床、按摩、冰火两重天、双飞等店铺服务:店铺服务: 漫游 过水吸皮 制服诱惑 丝袜诱惑 情趣诱惑 高跟鞋诱惑 角色扮演 cos 调情 舌吻亲嘴 接吻 毒龙 舔脚 抓龙筋 花式推法吸蛋蛋 一字马 缩阴 限时不限次 射身 舔奶头 舔鲍鱼 游龙戏水➕沐香丝竹🫰 纤纤玉手➕仙女漫游🫰 高山流水➕胯下游龙🫰 柔情毒龙➕猴子偷桃🫰 水磨拉丝➕百…

❤3

14 Nov 2026, 09:08 UTC417 viewsread 17 November 2026
Forwarded from @wuhanhua1Photo

📱#小奶猫 🌐#上门 💴【学费】#7p #12pp 🛫【联系】@xiaonaimaoo 🥂【双向】@xiaonainaidebot 📱【频道】 t.me/xiaonaimao0 ❤️【硬件】D/170cm/21 🫦【标签】#大胸 #新人 #上门 #7p #包夜 报告车评查找机器人:@vlchattbot

13 Nov 2026, 13:53 UTC584 views2 reactionsread 16 November 2026
Forwarded from @whlou4Video

━━━━━━━━━━━━━━ 🌟 外围李子评价🌟 ━━━━━━━━━━━━━━ 🏷 #外围# #2600 #御姐 👤 小琪外围: @wuqiqi9115 🔗 主页: https://t.me/whmqww123 ⭐️ 综合:★★★★★ 5/5 ├ 🎯 技能:★★★★★ 5/5 ├ 💗 情绪:★★★★★ 5/5 ├ 🏡 环境:★★★★★ 5/5 └ 📷 人照:★★★★★ 5/5 听了小琪的,选了李子,各方面很不错,情绪价值非常到位,身材颜值都很高,会聊天,深喉很到位,表情到位,会夹会吸,总之这次外围体验很爽。

❤2

13 Nov 2026, 13:45 UTC566 viewsread 16 November 2026
Forwarded from @whlou4Photo

━━━━━━━━━━━━━━ 🌟 外围小柔评价 🌟 ━━━━━━━━━━━━━━ 🏷 #外围# #2400 #御姐 👤 小琪外围: @wuqiqi9115 🔗 主页: https://t.me/whmqww123 ⭐️ 综合:★★★★★ 5/5 ├ 🎯 技能:★★★★★ 5/5 ├ 💗 情绪:★★★★★ 5/5 ├ 🏡 环境:★★★★★ 5/5 └ 📷 人照:★★★★★ 5/5 听小琪的意见选择了,小柔,胸是真的大,两只手握不下。我是颜控,颜值已经让我很满意,真实极品 BBw身材,没有多余的赘肉,屁股大,后入视觉冲击感太强。乳胶很爽。

13 Nov 2026, 07:58 UTC605 viewsread 16 November 2026
Photo

‹ 😃😃 😀😃 📱📱 📱📱 › 😎 东方罗马高端私密会所 😎 🫥高端会所 🫥私密会所 🫥情景定制 🀄服务项目 🀄 😂莞式一条龙激情服务😂 🔴鸳鸯戏水🔴泡沫风情🔴风情按摩 🟢指尖漫游🟢波涛汹涌🟢臀臀欲动 🔴蜻蜓点水🔴过水漫游🔴舌尖漫游 🟢花式毒龙🟢海底捞月🟢跪式吹箫 ➡主题角色扮演道具服装 ➡翻云覆雨配合多种姿势 🔥依您的喜好和需求为您做专属的私人定制,满足男性所有不同需求! 🔥每个项目都有小剧情,有开头、高潮、结尾、余温。等专属场景! 🔥环境私密舒适 ,绝对给您带来飞一般的体验! 💎不收定金 💎 靠谱预约 💎到店消费 ✔ 保护隐私—安全放心✔ 🥰🥰🥰🥰🥰🥰🥰🥰 ☹ 各个spa私密服务会所打造的高端特色服务项目不同。具体以会所前台获取的服务流程为准! 联系客服: @dogggt 双

13 Nov 2026, 06:36 UTC368 views2 reactionsread 15 November 2026
Forwarded from @wuhanhua1Photo

📱#小兰 🌐#光谷 💴【学费】#6p #12pp 🛫【联系】@Asd82538 🥂【双向】@jahhbbot 📱【频道】 t.me/asdhhhbbnm8899 ❤️【硬件】165cm/51kg/21 🫦【标签】#光谷 #嫩妹 #上门 #包夜 #6p 报告车评查找机器人:@vlchattbot

👍2

11 Nov 2026, 08:11 UTC628 viewsread 14 November 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6193807804

11 Nov 2026, 08:11 UTC582 views1 reactionsread 14 November 2026
Forwarded from @whlou4

━━━━━━━━━━━━━━ 🌟 外围女天爱 🌟 ━━━━━━━━━━━━━━ 🏷 #外围# #2600 #御姐 👤 老师:琪哥 @wuqiqi9115 🔗 主页: https://t.me/whmqww123 ⭐️ 综合:★★★★★ 5/5 ├ 🎯 技能:★★★★★ 5/5 ├ 💗 情绪:★★★★★ 5/5 ├ 🏡 环境:★★★★★ 5/5 └ 📷 人照:★★★★★ 5/5 找琪哥安排一次外围,听了他的推荐,选了天爱妹子,果然不错,身材颜值顶美,颜值在线,有明星的相貌。皮肤也好,服务也相当的不错,颜值又高服务又好,这次体验很值

❤1

10 Nov 2026, 11:59 UTC483 views2 reactionsread 14 November 2026
Forwarded from @wuhanhua1Photo

🔰武汉首家光谷全裸9T会所海选🔰 🔰武汉市洪山区光谷🔰海选9T会所 🔰武汉市新店开业全场3️⃣9️⃣8️⃣🎉 🔰武汉市洪山区光谷全裸9T 🔰 🔰🏅 金牌客服:@NBG8877 🔰🏅 加入技师点评频道: t.me/GHNB6677 🔰🏅 技师频道 : t.me/ZXH8877 🔰🏅 加入群组: t.me/GHNB88 🔰地址:武汉市洪山区光谷新竹路 🔰双向机器人🤖: @NBG888bot 🔰电话预约☎️: 17670192176 🔰微信🛰1️⃣预约:rcg222888 🔰微信🛰2️⃣预约:NBNF8866 🔰QQ🐧1️⃣预约:718184041 🔰QQ🐧2️⃣预约:3225243704 🔰武汉超级全裸9T全新升级版) 🔰原价:4️⃣9️⃣9️⃣预约价3️⃣9️⃣8️⃣ 🔰免费提供各类情趣丝袜可带走 🔰服务时间60分钟时间不限次 🔰营业时间:中午12点-凌晨4点 🔰顶美多联系客服可安排隐藏服务! 🔰武汉市光谷店铺服务…

❤2

Showing the 12 most recent of 60 posts we hold for @wuhanhua2. 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 3 posts on @wuhanhua2 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
11 August 2026
Most recent seen missing
17 November 2026
Median time before seen missing
3 days
Seen missing in the last 30 days
1

Forward network

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

“🅥武汉老师报告🅥” (@wuhanhua2), 17,644 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/wuhanhua2.

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.