Telegram RegisterThe public register of Telegram

Channel

🥇知鸢°全国包养选妃总导航

@zyby188

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

25,905subscribers

-245 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003781550724
TypeChannel
Username@zyby188
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/zyby188

Growth

25,90526,15026,027.56 August 2026 — 26,150 subscribers7 August 2026 — 26,145 subscribers8 August 2026 — 26,123 subscribers9 August 2026 — 26,074 subscribers9 August 2026 — 26,046 subscribers10 August 2026 — 26,001 subscribers11 August 2026 — 25,941 subscribers13 August 2026 — 25,905 subscribers6 August 202613 August 2026
8 measurements spanning 6 days, net -245. 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 25,868–26,187 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 00:1425,905-36
11 Aug 2026, 23:5625,941-60
10 Aug 2026, 21:3426,001-45
9 Aug 2026, 23:3726,046-28
9 Aug 2026, 01:2026,074-49
8 Aug 2026, 00:5226,123-22
7 Aug 2026, 04:1526,145-5
6 Aug 2026, 19:4626,150first reading

Engagement

85 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.028%
avg views ÷ 25,905 subscribers
Avg views / post
7.4
85 posts measured
Reaction rate
3.57%
reactions ÷ views · ER floor
Posts in window
85
of 85 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 1 of 85 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 12 August 2026
Posts held85 (6 August 202612 August 2026)
Views total625
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 22:19 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

Video runtime
1m 03s
Average length
13s

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

1 reaction across 1 post, in 1 kind.

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

Measured over the 85 most recent posts we hold, published 6 August 2026 to 12 August 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

12 Aug 2026, 22:00 UTC3 viewsread 12 August 2026

🚀️闲人互推-2号车🚀 AD: 问鼎/多多28/爆奖推荐100送100 🪽直播大秀裸舞 🪽直播大秀裸舞 🪽直播大秀裸舞 🪽直播大秀裸舞 🪽直播大秀裸舞 🪽酒店收藏级录像【免费】 🪽直播大秀裸舞 🪽直播大秀裸舞 🪽直播大秀裸舞 🪽台灣網紅外流素人自拍 🪽低价TON链TRX转账能量 🪽直播大秀裸舞 🪽🥇知鸢°全国包养选妃总导航 🪽御女宫 漫画 🪽直播大秀裸舞 📁🔥免费社工库🏅送大头照🏅查全家户籍🏅开盒人肉🔥 互推交流: @xianrenhutuiss

12 Aug 2026, 21:21 UTC5 viewsread 12 August 2026

♡ 嫩妹少女处女穴合集 ✦ 每日绿帽 调教绿奴 ✦ 反差婊极品 ✦ 反差-萝莉 福利社(实时更新) ✦ 中学生㊙️处女呦女破处俱乐部 ✦ 全国真实约炮交友 ✦ 西瓜ai色情动漫剧 ✦ ️针孔摄像头探花设备 | 微型摄·· ✦ 免费加速器|免费VPN|免费节点 ✦ 情感树洞 ✦ 光年-抖音粉丝小红书快手视频号·· ✦ 💞中学生处女呦女 ✦ 东南亚大事件新闻曝光 ✦ 动漫里番二次元 ✦ 西瓜视频ai色情动漫 ✦ 慢语树洞 ✦ 悄悄话树洞 ✦ Telegram增长指南 ✦ 夜店酒吧捡尸全集 ✦ 女同双飞💞干翻姐妹 ✦ 每日更新🔥AI上头短剧 ✦ 孕妇做爱💞内射合集 ✦ 西瓜色漫剧场 ✦ 阿黑颜AI智能脱衣 ✦ 成人AI动漫剧场 ✦ 极品反差Ai动漫视频 ✦ 男模/异性SPA/男技师与富婆私密·· ✦ Telegram数字生活指南 ✦ 菲菲🦋在线视频裸聊1v1🔞❤️‍🔥 ✦ 中文资源导航合集 ✦ 日本🇯🇵动漫公益分享 ✦ 巨乳肥臀微胖

12 Aug 2026, 19:52 UTC6 viewsread 12 August 2026
Photo

编号:7782093(点击复制) 📹点击查看验证视频🤖 昵称:qb131 省份:天津 城市:天津 年龄:19 身高:163 体重:88 罩杯:B 职业:学生 是否是chu女:否 可不可以口:可以 能不能内s:否 能不能无套:否 SM能不能:否 有没有纹身:无 是否可外省:可以 是否可过夜:可以 可不可以同居:可以 月可陪伴天数:3-20天 大概姨妈日期:月末 找金主的原因:希望找个疼我对我好满足我物质需求的爹系男友 月生活费多少:3天8k 7天1.6w 4w 分几次给生活费:2-3 自我介绍加分项:活泼开朗 温柔可爱 会照顾人 不事多 提供情绪价值 歌声甜美 游戏高手 会弹吉他 皮肤白 情商高 对老板雷点(不接受): 最快什么时候出发:提前说 ➡️介绍费7888 —————————————————— ▶️288入会抵扣888💵会员介绍费7折 ▶️会员首单仅需4900⚠️ ▶知鸢°官方客服下单 ▶双向限制点击 ▶新手

12 Aug 2026, 14:39 UTC16 viewsread 12 August 2026
Photo

编号:Y7781919(点击复制) 📹点击查看验证视频🤖 省份: 上海 地区: 松江 年龄: 19 身高: 165 体重: 95 罩杯:b 职业: 学生 是否是chu女: 否 月生活费多少: 2w 可不可以口: 可 SM能不能: 不能 能不能无🍑(体检后):能 分几次给生活费: 两次 大概姨妈日期: 月初 能不能内🐍(体检后):能 有没有纹身: 没有 是否可外省: 可 对老板雷点(不接受): 暴力 可不可以同居: 不能 是否可过夜: 可 月可陪伴天数: 4天 找金主的原因: 缺钱 自我介绍加分项:情绪价值高 能喝会玩 唱歌好听 ➡️介绍费7888 —————————————————— ▶️288入会抵扣888💵会员首单介绍费7折 ▶️会员首单仅需4900⚠️ ▶知鸢°官方客服下单 ▶双向限制点击 ▶新手下单必看指南 ▶客户成交案例 ——————————————————

12 Aug 2026, 13:49 UTC14 viewsread 12 August 2026
Photo

编号:7782091(点击复制) 📹点击查看验证视频🤖 昵称:qb134 省份:浙江 城市:杭州 年龄:19 身高:169 体重:110 罩杯:c 职业:学生 是否是chu女:否 可不可以口:可 能不能内s:否 能不能无套:否 SM能不能:否 有没有纹身:没有 是否可外省:可 是否可过夜:可 可不可以同居:可 月可陪伴天数:4 大概姨妈日期:16-22 找金主的原因:缺钱 月生活费多少:4天1w 分几次给生活费:2 自我介绍加分项:脾气好 情绪价值高 对老板雷点(不接受):油腻 不尊重人 最快什么时候出发:随时 ➡️介绍费7888 —————————————————— ▶️288入会抵扣888💵会员介绍费7折 ▶️会员首单仅需4900⚠️ ▶知鸢°官方客服下单 ▶双向限制点击 ▶新手下单必看指南 ▶️客户成交案例 ——————————————————

12 Aug 2026, 12:11 UTC13 viewsread 12 August 2026
Photo

编号:7781951(点击复制) 📹点击查看验证视频🤖 省份:广东 城市:广州 年龄:19 身高:165 体重:88 罩杯:b 学历: 职业: 是否是处女:否 可不可以口:可 能不能内射:否 能不能无套:能 SM能不能:轻微 有没有纹身:没有 是否可外省:否 是否可过夜:可 可不可以同居:不可以 月可陪伴天数:3天 大概姨妈日期:8号 找金主的原因: 月生活费多少:1.6w 分几次给生活费:固定分2次 自我介绍加分项:乖巧听话温柔 对老板雷点(不接受): ➡️介绍费7888 —————————————————— ▶️288入会抵扣888💵会员首单介绍费7折 ▶️会员首单仅需4900⚠️ ▶知鸢°官方客服下单 ▶双向限制点击 ▶新手下单必看指南 ▶客户成交案例 ——————————————————

12 Aug 2026, 08:21 UTC1 viewsread 12 August 2026

♡ 嫩妹少女处女穴合集 ✦ 动漫里番二次元 ✦ 反差婊极品 ✦ 日本🇯🇵动漫公益分享 ✦ 每日绿帽 调教绿奴 ✦ 免费加速器|免费VPN|免费节点 ✦ 菲菲🦋在线视频裸聊1v1🔞❤️‍🔥 ✦ 阿黑颜AI智能脱衣 ✦ 孕妇做爱💞内射合集 ✦ 酒店监控 ✦ Telegram数字生活指南 ✦ 巨乳肥臀微胖 ✦ Ai动漫视频反差群 ✦ 成人AI动漫剧场 ✦ 男模/异性SPA/男技师与富婆私密·· ✦ 光年-抖音粉丝小红书快手视频号·· ✦ Telegram增长指南 ✦ 小马拉大车操妈恋母绿妈 ✦ 极品反差Ai动漫视频 ✦ 女同双飞💞干翻姐妹 ✦ 中文资源导航合集 ✦ 眼镜婊反差视频 ✦ 💞中学生处女呦女 ✦ 全国真实约炮交友 ✦ ️针孔摄像头探花设备 | 微型摄·· ✦ 东南亚大事件新闻曝光 ✦ 反差-萝莉 福利社(实时更新) ✦ 慢语树洞 ✦ 西瓜色漫剧场 ✦ 西瓜ai色情动漫剧 ✦ 西瓜视频ai色情动漫 ✦ 悄悄话树洞 ✦ 夜店酒吧

12 Aug 2026, 08:07 UTC4 viewsread 12 August 2026
Photo

编号:Y7781876(点击复制) 📹点击查看验证视频🤖 省份:浙江 城市:温州 年龄:18 身高:163 体重:90 罩杯:B 工作还是雪生:雪生 雷点(不能接受男友的):太老 是否是chu女:否 能否接受SM:否 能否接受无套:否 能否接受口:可 可否同居:否 可否过夜:可 可陪伴天数:2.3 可否其他城市:可 可否飞往外省:可 最快多久出发:随时 姨妈期:月中 生活费接受多少:2天8k,3天1w (生活费短期2次长期3-4次付能否接受):3天分2次 自我加分项:刚下海 清纯甜美 可甜可御 乖巧听话 温柔懂事 体贴 懂得照顾老板 服务意识好 会提供情绪价值 配合度高 声音好听 接受程度高 带出去有面子 ➡️介绍费7888 —————————————————— ▶️288入会抵扣888💵会员首单介绍费7折 ▶️会员首单仅需4900⚠️ ▶知鸢°官方客服下单 ▶双向限制点击 ▶新手下单必看指南 ▶客户成交案例 —

12 Aug 2026, 08:06 UTC4 viewsread 12 August 2026
Photo

编号:Y7781875(点击复制) 📹点击查看验证视频🤖 省份: 广东 地区: 东莞 年龄: 18 身高: 162 体重: 84 罩杯:b 职业: 休学 是否是chu女: 不是 月生活费多少: 1.2w 可不可以口: 可 SM能不能: 不 能不能无🍑(体检后):一天➕1k 分几次给生活费: 2 大概姨妈日期: 十几号 能不能内🐍(体检后):一天+3k 有没有纹身: 是否可外省: 可以 对老板雷点(不接受): 抠搜 可不可以同居: 否 是否可过夜: 可 月可陪伴天数: 3 找金主的原因: 缺钱 自我介绍加分项:乖巧听话 清纯甜美 性格温柔 唱歌画画 无整反差 幽默有趣 情商高情绪价值满满 会撒娇有恋爱感 水多 三点粉 配合度高 ➡️介绍费7888 —————————————————— ▶️288入会抵扣888💵会员首单介绍费7折 ▶️会员首单仅需4900⚠️ ▶知鸢°官方客服下单 ▶双向限制点击 ▶新手下单必看指南

12 Aug 2026, 08:00 UTC4 viewsread 12 August 2026

🚀️闲人互推-1号车🚀 AD: 问鼎/多多28/爆奖推荐100送100 🪽💋火辣女优AV番号❤️‍🔥 🪽🔥🔥🔥抖音深度视频🔥🔥🔥 🪽直播大秀裸舞 🪽推特抖音网红吃瓜洩密 🪽开封外出喝茶小学妹又软又嫩 🪽🥇知鸢°全国包养选妃总导航 🪽御女宫 漫画 🪽母狗茶馆 🪽🇯🇵日本男人の福利駅 🪽🎀莉奈東京デリヘル・ホテル出張 🪽直播大秀裸舞 🪽蜜桃🍑微密圈网红写真 🪽台灣網紅外流素人自拍 🪽❥粉馒头🩷大神频道推荐|电子女友|维度视频 🪽少女学生反差写真 📁🔥免费社工库🏅送大头照🏅查全家户籍🏅开盒人肉🔥 互推交流: @xianrenhutuiss

12 Aug 2026, 07:47 UTC2 viewsread 12 August 2026
Photo

编号:7782089(点击复制) 📹点击查看验证视频🤖 昵称:qb137 省份:黑龙江 城市:绥化 年龄:20 身高:160 体重:50 罩杯:b 职业:大学生 是否是chu女:否 可不可以口:🉑 能不能内s:不能 能不能无套:不能 SM能不能:能 有没有纹身:无 是否可外省:否 是否可过夜:是 可不可以同居:可 月可陪伴天数:6-8 大概姨妈日期:17 找金主的原因:缺钱 月生活费多少:2k1天 分几次给生活费:见一次给一次 自我介绍加分项:乖听话 小母狗属性 会配合 对老板雷点(不接受):太胖 ➡️介绍费7888 —————————————————— ▶️288入会抵扣888💵会员介绍费7折 ▶️会员首单仅需4900⚠️ ▶知鸢°官方客服下单 ▶双向限制点击 ▶新手下单必看指南 ▶️客户成交案例 ——————————————————

12 Aug 2026, 06:06 UTC6 viewsread 12 August 2026
Photo

来自速搜推荐 @SSOU 📢西港新闻快讯 📢素材包装p图绘画套图 📢深圳出击大队资源榜 📢深圳凤雅楼老师榜 📢东南亚大事件 | 吃瓜新... 📢王竹子的SM教学频道 📢盘口一手/京东E卡/中小... 📢cos少萝研究所 📢🥇知鸢°全国包养选妃总... 📢西港日报快讯 📢东南亚日报 📢【东南亚】吃瓜暗网研究社... 📢亚星私网|欧博私网|环球... 📢深圳茶友老师榜 📢WD数据/贷款数据/企业... 👉流量互推规则介绍💥 以下是广告推荐 📢球速体育相信品牌的力量、老品牌值得信赖、不限ip、免实名。 📢 Ton 中文索引 📢 飞驰号铺 [主营:飞机号 开会员 代充星星] 📢 TGFind🚀Telegram最高效的搜索平台! 📢东南亚今日头条|新闻|爆料|悬赏|通缉|吃瓜缅甸妙瓦底大揭 🇨🇳 简体中文包 —————————-- 🔥将 @TonGroupHelpBot 设置为频道管理员,即可在2000+频道进行互推曝光,实现订阅

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

Citation-graph rank

Citation-graph rank — 409,270 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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

“🥇知鸢°全国包养选妃总导航” (@zyby188), 25,905 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/zyby188.

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.