Channel
@Banxia789
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,570subscribers
-8 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003982302952 |
|---|---|
| Type | Channel |
| Username | @Banxia789 |
| Description | 私信 @banxia78 双向 @Banxia78Bot 提前预约 |
| Created | Between 1 April 2026 and 14 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 10 |
| On Telegram | t.me/Banxia789 |
Personal blog — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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 |
|---|---|---|
| 17 Sept 2026, 00:22 | 1,570 | no change |
| 15 Sept 2026, 11:56 | 1,570 | -8 |
| 12 Sept 2026, 04:02 | 1,578 | -29 |
| 7 Sept 2026, 22:14 | 1,607 | -16 |
| 2 Sept 2026, 19:27 | 1,623 | -2 |
| 30 Aug 2026, 17:44 | 1,625 | +3 |
| 28 Aug 2026, 00:47 | 1,622 | +1 |
| 24 Aug 2026, 19:43 | 1,621 | +10 |
| 21 Aug 2026, 08:48 | 1,611 | +33 |
| 18 Aug 2026, 00:00 | 1,578 | first reading |
19 posts held, back to 14 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 1 page 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.
| Window | Rolling 30 days · latest post in window 8 September 2026 |
|---|---|
| Posts held | 19 (14 August 2026 – 8 September 2026) |
| Views total | 629 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Sept 2026, 00:22 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.
Lifetime counters from Telegram’s own channel header, read 17 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 7 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.
13 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 61.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 61.5% | |
| 👍 | 4 | 30.8% | |
| 👏 | 1 | 7.69% |
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 9 of the 19 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 14 August 2026 to 8 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.
感谢这段时间同学们的照顾，暑假在这边遇到了很多很好很好的同学，也有一些同学不太喜欢我，在这里就说声抱歉了，毕竟我不是人民币不可能人人都喜欢，我嘴比较笨，不太会说话，熟悉我的都知道我是属于慢热型，不是那种自来熟的类型，毕竟身份证18岁，我真实年龄也只有17岁，不过很高兴也很感动很多同学一直对我的喜欢。这边学校我已经办了休学，暂时就不在东莞了，如果有人需要我的频道可以有偿转让，当然我也可以自己留着，有机会回东莞了我可以自己用。怎么说呢，我也不知道说什么，谢谢来过我教室上课的所有同学，爱你们😘
👍4❤1
晚上好啊
❤1
开课了，过来提前预约
Sticker, posted without a caption
还有少许位
黑你的人有千千万😢，我不是人民币，不能做到人人都喜欢💋💋，只服务好喜欢的人，开课啦💋💋🉑🈷️
晚上还有位
东莞98每一份报告都来自群友，基本都带转发来源，除非群友不愿意直接转发，坚决不做收好处费假报告✊ 98群报告模板: 上课时间:8/19 验证留名: Arpan Patel 所在位置：大朗 老师名称：#半夏 老师电报：@banxia78 上课价格：600p 妹子年龄：嫩妹 总体评分（满分10分）: 容貌评分: 9 身材评分： 10 服务评分： 9 环境评分： 9 自由评论： 孤独的七夕，联系了老师，见到老师跟频道一致嫩妹一枚，服务很好，重点口活，不催种，这个七夕没失望，妹子真好 东莞避坑交流（老师🈲入）: https://telegram.me/+m8dh0w7pgNphNzRl 更多资源👉👉👉: @DG98JTbot 提交报告: @FB128858bot
❤2
今日七夕🌷🌹🌷🌹🌷🌹，让我做你的一次女友，期待你的鲜花😘😘😘😘
还有少许位
不是所有的诋毁都要去计较，只做给喜欢的人看，开课了
东莞98每一份报告都来自群友，基本都带转发来源，除非群友不愿意直接转发，坚决不做收好处费假报告✊ 98群报告模板: 上课时间:8/17 验证留名: 姆博 所在位置：#大朗 老师名称：#半夏 老师电报：@banxia78 上课价格：1200pp 妹子年龄：18 总体评分（满分10分）: 容貌评分: 9 身材评分： 10 服务评分： 9 环境评分： 9 自由评论： 老师的确漂亮，身材比例完美，酥胸嫩滑，腿细长白第一次出击老师，我有些拘谨，但是老师主动温柔，聊了一会我就放下包袱，迎接老师的服务。都有些迫不及待的想把老师压在身下，脱衣洗澡老弟很快就按耐不住表达了它的满意，到了床上，服务很仔细，很享受，弄的我控制不住的低吟。口活一绝，整根插入美人口中的，生理上的刺激和心理上的满足感简直了。后续经过男上热身后，进入正题，让老师女上在我鞭上荡秋千，触觉和视觉上的双重高潮。不断舞动，忍不住喷涌而出。老师也俏皮的落下了些甘霖。休息的的时…
❤1
Showing the 12 most recent of 19 posts we hold for @Banxia789. 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.
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 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“东莞半夏日记📔” (@Banxia789), 1,570 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Banxia789.
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.