Channel
@ZYFLZ8888
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
165subscribers
-9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001241564340 |
|---|---|
| Type | Channel |
| Username | @ZYFLZ8888 |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 2 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 2 October 2026 |
| On Telegram | t.me/ZYFLZ8888 |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Oct 2026, 12:17 | 165 | -4 |
| 8 Sept 2026, 21:21 | 169 | -2 |
| 23 Aug 2026, 23:55 | 171 | -1 |
| 16 Aug 2026, 13:55 | 172 | -1 |
| 8 Aug 2026, 14:30 | 173 | no change |
| 7 Aug 2026, 23:51 | 173 | -1 |
| 7 Aug 2026, 09:25 | 174 | first reading |
6 posts held, back to 1 March 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 27 March 2024. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 2 of the 6 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 6 most recent posts we hold, published 1 March 2024 to 27 March 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️⬇️ 免费素材大全，素材国家分组明细，分类明细 😆1#加拿大➡️https://t.me/jianad_sucai 😆2#英国 ➡️https://t.me/yingguo_sucai1 😆3#德国➡️https://t.me/deguo_sucai1 😆4#法国 ➡️https://t.me/faguo_sucai1 😆5#新西兰 ➡️https://t.me/xinxilan_sucai 😆6#美国 ➡️https://t.me/meiguo_sucai1 😆7#日本 ➡️https://t.me/riben_sucaik 😆8#韩国 ➡️https://t.me/huashu_sucai1v 😆9#越南 ➡️https://t.me/yuenan_sucai1 😆10#印度 ➡️https://t.me/yindu_sucail 😆11#菲律宾 ➡️https://t.me/feilv…
https://t.me/WL222222ji
https://t.me/ZhongwendaohangBOT6
半夜偷溜进姐表姐房间发现她竟然喜欢裸睡 自从表姐搬进我家，每次半夜上厕所经过表姐房间都感觉心里痒痒的，今晚鼓起勇气哪怕得不到，趁睡觉的时候偷拍两张 想来一发的时候看看感觉也不一样。 表姐门是锁着的，幸好这种卧室门钥匙通用。 我蹑手蹑脚的进去，竟然发现表姐没穿衣服，我草，这捡大漏了。·手忙脚乱的赶紧拍两张，只可惜表姐这个姿势看不到大白奶。 👉|2345看图王 |素材话术 | 👉|☎️轰炸 |飞鱼接码 |
❤1
骚逼嫂子乱伦系列#善良的嫂子 👉|2345看图王 |素材话术 | 👉|☎️轰炸 |飞鱼接码 |
老妈刚洗完澡躺在床上敷面膜，我枕在了她的大腿上，手时时不时的摸摸大腿，可能是因为我经常帮老妈按摩大腿的，老妈并没有说我 仔细观察了下老妈大腿中间发现老妈没穿内裤e，太激动了不知道哪里来的勇气，手轻轻的去拉开了她的裤子，不敢有太大的动作怕被发现，可惜只能看到点阴毛没看到别的，感觉老妈的毛好多 过程中老妈大腿动了一下，真的太害怕了，我赶紧把手拿开了，又把手放在老妈的肚子上，我也经常摸老妈的肚子的这个不怕 最后终于又把老妈搞到手🤕 👉|2345看图王 |素材话术 | 👉|☎️轰炸 |飞鱼接码 |
Showing the 6 most recent of 6 posts we hold for @ZYFLZ8888. 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.
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.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“老王家族 ⭕️ 微密圈” (@ZYFLZ8888), 165 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/ZYFLZ8888.
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.