Telegram RegisterThe public register of Telegram
Telegram profile photo for 杭州嫩妹馆新人工兵

Channel

杭州嫩妹馆新人工兵

@hznmx

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

21,761subscribers

+8,123 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-1003814128064
TypeChannel
Username@hznmx
Description主群聊天群 @hznmg23 合作 @hznmg22_bot
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/hznmx

Topic

Other / unclassifiable — 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 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
@hznmx/1544 · this entry7 Aug 2026, 05:04 UTC@hznenmei2/49558 Aug 2026, 09:51 UTC1.0029 hours
@hznmx/1602 · this entry10 Aug 2026, 10:06 UTC@hznenmei2/499910 Aug 2026, 10:06 UTC1.00under a minute
@hznenmei2/527918 Aug 2026, 18:18 UTC@hznmx/1758 · this entry18 Aug 2026, 18:18 UTC1.00under a minute
@hznenmei2/557930 Aug 2026, 06:35 UTC@hznmx/1915 · this entry30 Aug 2026, 06:35 UTC1.00under a minute
@hznenmei2/56432 Sept 2026, 07:33 UTC@hznmx/1949 · this entry2 Sept 2026, 07:36 UTC1.003 minutes
@hznmx/3159 · this entry2 Nov 2026, 14:10 UTC@hznenmei2/76853 Nov 2026, 16:54 UTC1.0027 hours
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
@hznenmei228 (8/8 hand-verifiable sample passed)1.00under a minute@hznenmei2 (25–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. 25 of the 25 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 135 comparable posts for this entry, running 6 August 2026 to 13 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 @hznmx — 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 14 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

13,63821,76117,699.57 August 202612 November 2026
64 measurements spanning 97 days, net +8,123. 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 12,420–22,979 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
12 Nov 2026, 21:4521,761+204
10 Nov 2026, 15:1921,557+144
9 Nov 2026, 02:0021,413+92
7 Nov 2026, 15:5821,321+32
6 Nov 2026, 13:5821,289+31
5 Nov 2026, 16:1521,258+45
4 Nov 2026, 17:0121,213+93
3 Nov 2026, 17:0921,120+118
2 Nov 2026, 16:1921,002+61
1 Nov 2026, 15:4020,941-1
31 Oct 2026, 18:5020,942+301
30 Oct 2026, 21:5620,641+97
30 Oct 2026, 00:0620,544+54
28 Oct 2026, 22:4120,490+96
28 Oct 2026, 00:2120,394+52
27 Oct 2026, 03:0720,342+18
26 Oct 2026, 06:2520,324+73
25 Oct 2026, 07:1020,251+137
24 Oct 2026, 05:0920,114+129
23 Oct 2026, 04:0619,985first reading

Engagement

173 posts held, back to 6 August 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 78 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.04%
avg views ÷ 21,761 subscribers
Avg views / post
662
70 posts measured
Reaction rate
0.141%
reactions ÷ views · ER floor
Posts in window
70
of 173 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 40 of 70 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 14 November 2026
Posts held173 (6 August 2026 – 14 November 2026)
Views total46,359
Reactions total40
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 16:29 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
≈1,580
Videos
≈637
Links
≈600

Lifetime counters from Telegram’s own channel header, read 14 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
12m 18s
Average length
6s

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

106 reactions across 69 posts, in 3 distinct kinds. The most used accounts for 94.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤10094.3%
👍54.72%
👏10.943%

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

Measured over the 173 most recent posts we hold, published 6 August 2026 to 14 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: 4 of 70 posts held from the last 30 days (5.71%) 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).

14 Nov 2026, 12:20 UTC415 views2 reactionsread 14 November 2026
Photo

【花名】#橘子 【联系】@xiaojuz8 【频道】https://t.me/Juzi170 【位置】#拱墅 【标签】#嫩妹 #舌吻 【价格】#900p 1700pp 【报告】 新人开课 🛫群组链接 📌认证频道 📍新人频道 👀上榜咨询 😀高颜精选 😀报告提交 【工兵优惠】:剩0名,共2名6折500p/1000pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

❤2

Signed 名字好难i虎牙(主页频道超多美食😋)

14 Nov 2026, 11:32 UTC470 viewsread 14 November 2026
Photo

【花名】#小雪宝宝 【联系】@hzxuexue07 【频道】@babyxue07 【位置】#上城 【标签】#嫩妹 #舌吻 #六九 【价格】#1200p 2300pp 【报告】 萝莉,小东西,好菜无脑冲 🛫群组链接 📌认证频道 📍新人频道 👀上榜咨询 😀高颜精选 😀报告提交 【工兵优惠】:剩0名 6折700p/1400pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

Signed 名字好难i虎牙(主页频道超多美食😋)

14 Nov 2026, 11:22 UTC402 viewsread 14 November 2026
Photo

【花名】#小雨 【联系】@h486231 【频道】https://t.me/a72v1 【位置】#拱墅 【标签】#嫩妹 #舌吻 #六九 【价格】#1000p 1900pp 【报告】报告1 🛫群组链接 📌认证频道 📍新人频道 👀上榜咨询 😀高颜精选 😀报告提交 【工兵优惠】:剩0名,共2名6折600p/1100pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

Signed iuu(岸)

14 Nov 2026, 10:46 UTC448 views0 reactionsread 14 November 2026
Photo

【花名】#angelababy 【联系】@zs80809 【频道】@zs66776 【位置】#拱墅 【标签】#御姐 #舌吻 #六九 #一字马 #双飞 【价格】#1600p 3000pp 【报告】 三点粉嫩,可以一字马 🛫群组链接 📌认证频道 📍新人频道 👀上榜咨询 😀高颜精选 😀报告提交 【工兵优惠】:剩0名,共1名6折1000p/1800pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

14 Nov 2026, 10:17 UTC438 viewsread 14 November 2026
Photo

【花名】#豆豆 【联系】@wenzong666 【频道】@wenzog666 【位置】#拱墅 【标签】#嫩妹 #舌吻 #六九 【价格】#1000p 1900pp 【报告】 新人开课 🛫群组链接 📌认证频道 📍新人频道 👀上榜咨询 😀高颜精选 😀报告提交 【工兵优惠】:剩2名,共2名6折600p/1100pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

Signed 名字好难i虎牙(主页频道超多美食😋)

13 Nov 2026, 15:46 UTC737 views1 reactionsread 14 November 2026
Photo

【花名】#婊妹 【联系】@liaoliaofa 【频道】@biaomeimei77 【位置】#拱墅 【标签】#嫩妹 #舌吻 #六九 【价格】#600p 1100pp 【报告】 BBW 🛫群组链接 📌认证频道 📍新人频道 👀上榜咨询 😀高颜精选 😀报告提交 【工兵优惠】:剩2名,共2名6折400p/700pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

❤1

13 Nov 2026, 15:19 UTC567 views3 reactionsread 14 November 2026
Photo

【花名】#诗雯 【联系】@sw1234568 【频道】@sw6868685858 【位置】#上城 【标签】#嫩妹 #舌吻 #六九 【价格】#800p 1500pp 【报告】 🛫群组链接 📌认证频道 📍新人频道 👀上榜咨询 😀高颜精选 😀报告提交 【工兵优惠】:剩2名,共2名6折500p/900pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

❤3

13 Nov 2026, 11:02 UTC709 viewsread 14 November 2026
Photo

🎰 若曦 @xxbgif 福利抽奖 📮 抽奖条件: 🎫 加入-杭州嫩妹馆 🎫 加入-杭州嫩妹馆榜单 🎫 加入-杭州嫩妹馆新人工兵 🎫 加入-杭州嫩妹馆高颜值精选 🎫 加入-若曦的后花园 🎟️ 要求活动期间群内发言数 1 🍀 每1分中奖几率加1倍 ⤷在群中输入「喜+1」 🎁 奖品内容: 若曦 @xxbgif 6折P × 2 优惠券100 × 3 优惠券200 × 3 💡 活动说明: 中奖五日内兑换,超时作废! 📅 开奖日期:(UTC+8) 2026年11月16日 16时16分16秒

Signed 嫩妹馆福利女仆

13 Nov 2026, 08:36 UTC734 views0 reactionsread 14 November 2026
Photo

【花名】#呆呆 【联系】@daidaiyy08 【频道】@daidaiy0812 【位置】#拱墅 【标签】#嫩妹 #舌吻 #六九 【价格】#900p 1700pp 【报告】 报告1 新人开课 🛫群组链接 📌认证频道 📍新人频道 👀上榜咨询 😀高颜精选 😀报告提交 【工兵优惠】:剩1名,共2名6折500p/1000pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

Signed 名字好难i虎牙(主页频道超多美食😋)

13 Nov 2026, 06:49 UTC757 viewsread 14 November 2026
Photo

【花名】#小兔 【联系】@xiaotu08 【频道】https://t.me/xiaotup1 【位置】#拱墅 【标签】#嫩妹 #舌吻 #六九 【价格】#800p 1500pp 【报告】报名1 新人开课 🛫群组链接 📌认证频道 📍新人频道 👀上榜咨询 😀高颜精选 😀报告提交 【工兵优惠】:剩0名,共2名6折500p/900pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

Signed 名字好难i虎牙(主页频道超多美食😋)

13 Nov 2026, 06:00 UTC745 views1 reactionsread 14 November 2026
Photo

【花名】#柠檬奶茶 【联系】@yinger884 【频道】@xiaoalidesirenkongjian 【位置】#西湖 【标签】#舌吻 #六九 #嫩妹 【价格】 #1000p 1800pp 【提示】嫩妹 【报告】报告1 【工兵优惠】:剩0名,共2名6折600p/1100pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

❤1

12 Nov 2026, 12:48 UTC623 viewsread 13 November 2026
Photo

【花名】#芊芊 【联系】@QIAN349 【频道】@QIAN258000 【位置】#拱墅 【标签】#嫩妹 #舌吻 #六九 【价格】#800p 1400pp 【报告】 新人开课 🛫群组链接 📌认证频道 📍新人频道 👀上榜咨询 😀高颜精选 😀报告提交 【工兵优惠】:剩0名,共2名6折500p/800pp,需出报告 ①群内发送“工兵”获取模板,填写并附嫩币200以上截图,过往报告(必要)资料不全不回复 ②发送 @hznmg22_bot 报名,回复“报名成功”有效,自行截图发送给老师 ③报名成功需两日内出击并出报告,未按时出击或出报告将被移除群聊并挂黑名单

Showing the 12 most recent of 173 posts we hold for @hznmx. 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 edited after publishing

@hznmx edited 4 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 August 2026
Most recent edit
7 November 2026

Posts recorded as deleted after publishing

We recorded 4 posts on @hznmx 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
26 August 2026
Most recent seen missing
4 November 2026
Median time before seen missing
15 hours
Seen missing in the last 30 days
2

Forward network

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.

Mentions

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

“杭州嫩妹馆新人工兵” (@hznmx), 21,761 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/hznmx.

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.