一键关注惠州 𝘽𝙖𝙣𝙖𝙣𝙖𝙏𝙑® 🍌 https://t.me/addlist/q3-mW1riatgyY2Q5

Channel
深圳香蕉集团名师榜单
@zs1112
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
12,189subscribers
+104 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1004365042174 |
|---|---|
| Type | Channel |
| Username | @zs1112 |
| Created | Between 1 June 2026 and 28 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/zs1112 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 23:37 | 12,189 | +16 |
| 5 Sept 2026, 00:40 | 12,173 | +19 |
| 3 Sept 2026, 09:34 | 12,154 | +8 |
| 2 Sept 2026, 06:43 | 12,146 | +4 |
| 1 Sept 2026, 08:45 | 12,142 | +11 |
| 31 Aug 2026, 07:35 | 12,131 | +10 |
| 30 Aug 2026, 10:57 | 12,121 | +9 |
| 29 Aug 2026, 14:07 | 12,112 | +27 |
| 28 Aug 2026, 22:15 | 12,085 | first reading |
Engagement
6 posts held, back to 28 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 9 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.893%
- avg views ÷ 12,189 subscribers
- Avg views / post
- 109
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 6
- of 6 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.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 6 (28 August 2026 – 30 August 2026) |
| Views total | 653 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 22:54 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
- 30s
- Average length
- 8s
Measured directly from 4 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.
Recent posts
🎉 惠州香蕉集团合并 🎁 奖品清单 • 老师1P半价 × 1 • 188口令 × 1 • 88 × 1 🛡️ 参与条件 • 加入 惠州香蕉集团 【广告群】 • 加入 惠州蕉友群 🍌 【🚫禁广告】 • 加入 惠州 𝘽𝙖𝙣𝙖𝙣𝙖𝙏𝙑® 🍌 • 加入 惠州𝘽𝙖𝙣𝙖𝙣𝙖𝙏𝙑老师典藏榜 • 加入 惠州焦友抽奖频道 • 参加抽奖后需在 惠州香蕉集团 【广告群】 内发言666次 └ 群内发送“抽奖进度”查看完成度(每日限5次) • 必须设置用户名 ⌛ 开奖时间 • 2026-09-10 00:00:00 📜 抽奖说明 刷屏、灌水、纯表情、复制粘贴、无意义对话、撤回内容等,一律视为无效发言,不计入统计! 再次重申:灌水无意义发言都不兑奖!请用心交流。 活动最终解释权归本群管理团队所有。 中奖的12小时内联系管理员领取 @ssoood123 24小时内预约时间,72小时过时自动作废 炸号作废放回奖池重新抽奖 用了优惠劵要写报告! ✨…
📊 0条车评 写报告 好评 0% | 人照 | 服务 中评 0% | 颜值 | 态度 差评 0% | 身材 | 环境 🙋🏻♀️ 花名:#高颜萝莉贝儿 🌍 位置: #会所 💸 费用: #349F #419FF 💌 联系:@zs3336 📢 频道:https://t.me/zs3334 📝 服务内容:92-94服务萝莉音 声音夹夹得 超级好听 本人也很漂亮 顶级嫩妹 奶子贼大 听话 服务贼好 超级推荐 照片本人一模一样 不照骗 假一赔十
📊 2条车评,综合分 8.8 好评 100% | 人照 8.0 | 服务 9.0 中评 0% | 颜值 8.5 | 态度 9.5 差评 0% | 身材 9.0 | 环境 8.5 👆 【点击查看评价】 🙋🏻♀️ 花名:#贝贝酱 🌍 位置: #金山湖 💸 费用: #700P #1400PP 💌 联系:@djshssh28 📢 频道:https://t.me/sjdhx2837 📝 服务内容:馒头户型無套口口臭鸳鸯浴 69互动调情咪咪 美臀 后入观音坐莲乖巧可爱听话不催不事真人真照有小裙子
📊 1条车评,综合分 10.0 好评 100% | 人照 10.0 | 服务 10.0 中评 0% | 颜值 10.0 | 态度 10.0 差评 0% | 身材 10.0 | 环境 10.0 👆 【点击查看评价】 🙋🏻♀️ 花名:#羊羊 🌍 位置: #龙丰 💸 费用: #700P #1300PP 💌 联系:@ccczzxxc 📢 频道:https://t.me/zcyuuu 📝 服务内容:舌吻鸳鸯浴六九情趣制服诱惑 高跟丝袜水中萧 kiss
📊 1条车评,综合分 8.7 好评 100% | 人照 9.0 | 服务 8.0 中评 0% | 颜值 10.0 | 态度 8.0 差评 0% | 身材 10.0 | 环境 7.0 👆 【点击查看评价】 🙋🏻♀️ 花名:#由美 🌍 位置: #麦地 💸 费用: #700P #1400PP 💌 联系:@maidiyoumei520 📢 频道:@maodiyoumei1314 📝 服务内容:鸳鸯浴🛁水中萧、无套吹箫、波推、激情爱爱、十指调情、丝袜、👙情趣制服、各种姿势配合、
Showing the 6 most recent of 6 posts we hold for @zs1112. 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.
Forward network
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.
Mentions
Named by 1 registered channel — 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.
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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳香蕉集团名师榜单” (@zs1112), 12,189 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/zs1112.
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.