我还有好多地方需要改正,就不选花魁了,可以投梓悦
🤪8❤5😎1

Channel
@xue70
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
2,919subscribers
+319 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003944498919 |
|---|---|
| Type | Channel |
| Username | @xue70 |
| Created | 8 July 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/xue70 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 76% 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 |
|---|---|---|
| 12 Oct 2026, 12:44 | 2,919 | -263 |
| 5 Oct 2026, 11:01 | 3,182 | -5,008 |
| 27 Sept 2026, 07:15 | 8,190 | +5,089 |
| 16 Sept 2026, 01:20 | 3,101 | +39 |
| 12 Sept 2026, 00:41 | 3,062 | +34 |
| 7 Sept 2026, 16:38 | 3,028 | +60 |
| 2 Sept 2026, 15:34 | 2,968 | +22 |
| 30 Aug 2026, 10:24 | 2,946 | +19 |
| 27 Aug 2026, 14:11 | 2,927 | +17 |
| 24 Aug 2026, 06:26 | 2,910 | +31 |
| 20 Aug 2026, 18:25 | 2,879 | +51 |
| 17 Aug 2026, 23:23 | 2,828 | +68 |
| 14 Aug 2026, 20:13 | 2,760 | +112 |
| 11 Aug 2026, 10:13 | 2,648 | +38 |
| 8 Aug 2026, 09:16 | 2,610 | +10 |
| 7 Aug 2026, 20:16 | 2,600 | no change |
| 7 Aug 2026, 19:40 | 2,600 | first reading |
14 posts held, back to 8 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 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 14 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
249 reactions across 11 posts, in 11 distinct kinds. The most used accounts for 63.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 159 | 63.9% | |
| 🤪 | 36 | 14.5% | |
| 🫡 | 24 | 9.64% | |
| 🥰 | 9 | 3.61% | |
| 💯 | 7 | 2.81% | |
| 🦄 | 4 | 1.61% | |
| 😭 | 3 | 1.20% | |
| 🤬 | 3 | 1.20% | |
| 🎉 | 2 | 0.803% | |
| 😎 | 1 | 0.402% | |
| 🤗 | 1 | 0.402% |
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 11 of the 14 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 249 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 8 July 2026 to 5 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.
我还有好多地方需要改正,就不选花魁了,可以投梓悦
🤪8❤5😎1
唉在老家也能吃上关于自己的瓜 吵架别带我 我是无辜的😭
🤪7❤4
红休
🥰3
排课问题还会在继续改进并改进 不好意思占用大家时间了 金针菇的事情确实是我的不对 对不起对不起 以前不会排课 现在已经学会了很多 耽误到大家时间了 以后满课也会在频道里面发 大家可以随意监督😢 1号2号休息两天 在老家 还有些人不要觉得我一味着在忍让觉得 好欺负 不会在那么懦弱了 有些东西不想发出来并不是怕 我的错我会认 挨打就立正!
❤15
哦哦哦哦哦哦哦哦发个旧视频
❤11
安全安全
❤8🥰6🤗1
今天休息一天 下次发现大吉吉直接退 我频道已经提前说好了 不要到时候被退了现场埋怨我😟 还有那种进门脸红 还没开始就超级硬的 口的时候我嘴巴麻的 一律不接 发现直接退 让走人
🤪21❤10🫡7💯3🤬3
把之前删除的照片补回来
❤22
小雪后宫 pinned a photo
把烦恼一jio踢开
❤17
妖魔鬼怪快离开 妖魔鬼怪快离开 刚学的老爹的咒语
❤35💯4🦄4
Photo, posted without a caption
❤32🫡17😭3🎉2
Showing the 12 most recent of 14 posts we hold for @xue70. 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“1” (@xue70), 2,919 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/xue70.
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.