🏷️ ️ 御姐推荐️🏷️ 【花名】:#兔兔酱 #上城区 【水费】:#1000p #1800pp 【罩杯】:#C罩杯 【电报】:@tuy00001103 【标签】:#御姐 #舌吻 #六九 #制服 【报告】:1 2 3 *商k下海,女上桩机 ©️ yutangbazhu copyright protection 🫦点击参与 激情群聊🫦 🍑以身入局 参与计划🍑
Signed 🐟 鱼大(鱼塘HR/办公号)

Channel
@HZYT99
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
12,961subscribers
+770 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002704646149 |
|---|---|
| Type | Channel |
| Username | @HZYT99 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/HZYT99 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 01:56 | 12,961 | +185 |
| 6 Sept 2026, 15:40 | 12,776 | -142 |
| 4 Sept 2026, 07:57 | 12,918 | +46 |
| 2 Sept 2026, 17:25 | 12,872 | +25 |
| 1 Sept 2026, 19:25 | 12,847 | +27 |
| 31 Aug 2026, 21:54 | 12,820 | +31 |
| 31 Aug 2026, 01:06 | 12,789 | +53 |
| 30 Aug 2026, 02:26 | 12,736 | +23 |
| 27 Aug 2026, 23:11 | 12,713 | +22 |
| 27 Aug 2026, 02:35 | 12,691 | +62 |
| 26 Aug 2026, 02:57 | 12,629 | +37 |
| 25 Aug 2026, 02:46 | 12,592 | +21 |
| 23 Aug 2026, 18:12 | 12,571 | +64 |
| 22 Aug 2026, 00:14 | 12,507 | +42 |
| 20 Aug 2026, 21:57 | 12,465 | +68 |
| 19 Aug 2026, 19:36 | 12,397 | +85 |
| 18 Aug 2026, 17:24 | 12,312 | +13 |
| 17 Aug 2026, 20:05 | 12,299 | +68 |
| 16 Aug 2026, 18:37 | 12,231 | -43 |
| 15 Aug 2026, 03:45 | 12,274 | first reading |
62 posts held, back to 27 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 34 pages of 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 25 of 44 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 62 (27 July 2026 – 2 September 2026) |
| Views total | 63,764 |
| Reactions total | 41 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 20:53 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.
Measured directly from 8 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.
67 reactions across 31 posts, in 3 distinct kinds. The most used accounts for 85.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 57 | 85.1% | |
| 👍 | 9 | 13.4% | |
| 💯 | 1 | 1.49% |
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 38 of the 62 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 67 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 62 most recent posts we hold, published 27 July 2026 to 2 September 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.
🏷️ ️ 御姐推荐️🏷️ 【花名】:#兔兔酱 #上城区 【水费】:#1000p #1800pp 【罩杯】:#C罩杯 【电报】:@tuy00001103 【标签】:#御姐 #舌吻 #六九 #制服 【报告】:1 2 3 *商k下海,女上桩机 ©️ yutangbazhu copyright protection 🫦点击参与 激情群聊🫦 🍑以身入局 参与计划🍑
Signed 🐟 鱼大(鱼塘HR/办公号)
做了一个绍兴 宁波辅榜 有好的老师可以推荐给我 https://t.me/nsytbz101
Signed 🐟 鱼大(鱼塘HR/办公号)
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7638588179
Signed 极搜🔍资源搜索@JISOU
😇😇😇😇😇 ✅夜色如诗,句句倾心,我们不是向导! ✅是与你共赴一场感官漫游的同行者,在冰球融化的间隙! ✅在爵士乐浸润的威士忌杯沿,在月光与路灯的冷暖博弈中! ✅我们陪你把心事折成纸船,放逐于无垠的暗蓝。你只需带着自己来! ✅剩下的,交给夜色,交给我们,妹妹们翘首以盼! ✅夜色包养伴游品质保证承诺:保证素人 背调 绝对拒绝曾下海过 😄【夜色包养选妃频道全网资源: @yese7988 😄【夜色双向机器人: @yese988_bot 入会立即享受六折优惠,私聊会有更多的意外惊喜等着您,颠覆你对包养的看法! 🤗😳😳 😄【夜色包养伴游联系方式:@yese798 见面面试不满意,%100退还介绍费! 包见面,包上床,货不对版包退换!
❤1
Signed 🐟 鱼大(鱼塘HR/办公号)
别把别人的宽容, 当作做下菜的理由 课表有的如图做 其他随便怎么口嗨 课表之前没给人做 给做了还感谢别人的建议
❤5
Signed 🐟 鱼大(鱼塘HR/办公号)
鱼塘本周活动开启 周一 露露半价券竞拍 @lululaoshi0821 嘉儿7折兑换 @vbvb520 苏沫儿6折兑换 @Sumoer918 回归老师 桃花回归 @xiaotaohua1688 JOJO回归 @JoJobaobao 拿铁回归 @latte123330 悦悦回归 @Xx161700
Signed 🐟 鱼大(鱼塘HR/办公号)
小🐟拉大🐎 175的排骨我能见过 175的大马真没见过 产自湘江湖畔175大车 试驾热线: @xm175888 ⚠️试驾有风险 开车需谨慎⚠️
❤2
Signed 🐟 鱼大(鱼塘HR/办公号)
拓海开新群了 新群优惠多 去看看吧 https://t.me/HztxhHqGLbot?start=i-Fv-8edAhlRI2ZmQ0
Signed 🐟 鱼大(鱼塘HR/办公号)
周六赌博日,瓜分3万鱼饵
Signed 🐟 鱼大(鱼塘HR/办公号)
所有狼友约课老师都是个人行为,跟群无关,群提供老师曝光信息,狼友看报告出击。按需选择。 接受投诉,只能尽量处理售后,但是也没那么多精力,该写差评写差评,该曝光曝光。主要不是慈善机构,没那么多钱补贴。 如果接受不了直接开盒,感谢理解
Signed 🐟 鱼大(鱼塘HR/办公号)
触发双倍水群 晚上8点开启
Signed 🐟 鱼大(鱼塘HR/办公号)
狗推一下 蒂蒂 @xyu4320 少御脸 安迪 @uadaia 174大长腿 准备跑路 限时活动开启
Signed 🐟 鱼大(鱼塘HR/办公号)
Showing the 12 most recent of 62 posts we hold for @HZYT99. 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.
@HZYT99 edited 1 post 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 2 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.
@HZYT99 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“黑鱼出击计划” (@HZYT99), 12,961 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/HZYT99.
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.