Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_8022174706
🔥246❤245👍233🎉218😁207👏11🥰10🤩8

Channel
@JMNU010
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6,771subscribers
-3,310 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003116921300 |
|---|---|
| Type | Channel |
| Username | @JMNU010 |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/JMNU010 |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 21:55 | 6,771 | -555 |
| 11 Nov 2026, 10:16 | 7,326 | -31 |
| 7 Nov 2026, 15:15 | 7,357 | -17 |
| 4 Nov 2026, 18:11 | 7,374 | -226 |
| 1 Nov 2026, 15:46 | 7,600 | -257 |
| 29 Oct 2026, 16:10 | 7,857 | -27 |
| 27 Oct 2026, 00:44 | 7,884 | -29 |
| 24 Oct 2026, 00:11 | 7,913 | -24 |
| 21 Oct 2026, 03:11 | 7,937 | -26 |
| 18 Oct 2026, 03:48 | 7,963 | -30 |
| 14 Oct 2026, 19:07 | 7,993 | -32 |
| 11 Oct 2026, 04:18 | 8,025 | -158 |
| 4 Oct 2026, 18:02 | 8,183 | -200 |
| 25 Sept 2026, 08:39 | 8,383 | -258 |
| 17 Sept 2026, 04:18 | 8,641 | -60 |
| 13 Sept 2026, 08:55 | 8,701 | -97 |
| 9 Sept 2026, 05:01 | 8,798 | -226 |
| 3 Sept 2026, 17:17 | 9,024 | -153 |
| 31 Aug 2026, 07:33 | 9,177 | -171 |
| 28 Aug 2026, 00:07 | 9,348 | first reading |
7 posts held, back to 15 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 56 pages 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 26 October 2026 |
|---|---|
| Posts held | 7 (15 July 2026 – 26 October 2026) |
| Views total | 8,710 |
| Reactions total | 2,404 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 14:40 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.
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.
8,776 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 20.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 1,787 | 20.4% | |
| ❤ | 1,766 | 20.1% | |
| 🎉 | 1,739 | 19.8% | |
| 👍 | 1,713 | 19.5% | |
| 😁 | 1,591 | 18.1% | |
| 🥰 | 62 | 0.706% | |
| 👏 | 61 | 0.695% | |
| 🤩 | 57 | 0.649% |
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 7 of the 7 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 8,776 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 15 July 2026 to 26 October 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.
Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_8022174706
🔥246❤245👍233🎉218😁207👏11🥰10🤩8
黄豆短剧最新地址 新片每日更新,禁忌、刺激、连载不停 想看的都在里面,点了就懂 https://hddj31.com/?_c=CPSTS3L4NC6 建议保存,防止迷路 群福利置顶 黄豆日更短剧 · 越更越带劲 那些不能明说的剧情,这里持续更新 直达链接:https://hddj31.com/?_c=CPSTS3L4NC6 深夜专属入口已更新 黄豆成人短剧,新片不断 想看多“过分”都可以慢慢找 https://hddj31.com/?_c=CPSTS3L4NC6 置顶备用,随时来 【长期有效】黄豆短剧官方地址 每天都有新的禁忌故事上线 尺度自己把控,越看越上瘾 点击进入:https://hddj31.com/?_c=CPSTS3L4NC6
🔥259❤253🎉253👍236😁204🥰9👏6🤩6
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_8022174706
😁283🎉275👍273🔥264❤251🥰11👏10🤩7
艺名: 乔乔 段位: #辅导员(青铜) 地点: #朝阳 编号: #JMBJ1337 纯天然无整容,顶美颜值,不娇情,不催,配合度高,女友感强,乖乖女。 硬件: 168/44/ C/20 车费: 3000/P 5500PP 联系老师: @qixini 机器人: @qiaoqiaozizi_bot 标签: #颜值系 #服务 #嫩妹 北京交流群: @jmnu010a_a 北京大⭕奢侈品 @cgqlbj
❤385🔥374🎉353😁339👍336🤩12👏11🥰7
艺名: 依然 段位: #辅导员(青铜) 地点: #朝阳 编号: #JMBJ1336 陪浴,水中萧,kiss👄,🐻推,指划漫游,丝足,AB面,🈚套口,69👄,窃窃私语,按摩,激情啪啪,情趣内衣,高跟丝袜可选 硬件: 166/53/ D/01 车费: 1200/P 1800PP 联系老师: @YRaini888 机器人: @YRaini8899_bot 标签: #颜值系 #服务 #嫩妹 北京交流群: @jmnu010a_a 北京大⭕奢侈品 @cgqlbj
👍208🔥204❤200🎉186😁168🤩10🥰9👏5
艺名: 小关 段位: #辅导员(青铜) 地点: #朝阳 编号: #JMBJ1335 皮肤光滑细腻,人照无差,活好👌🏻不机车,🉑69,🉑kiss,🉑陪🛁,高跟制服,情趣诱惑,不过分都可满足,不议价 硬件: 165/48/C/ 车费: 1500/P 2800PP 联系老师: @th520954 机器人: @xiaoguan_bot 标签: #颜值系 #服务 #嫩妹 北京交流群: @jmnu010a_a 北京大⭕奢侈品 @cgqlbj
🎉227🔥217👍212❤211😁177🥰9🤩8👏7
艺名: 夏季 段位: #辅导员(青铜) 地点: #丰台 马家堡 编号: #JMBJ1334 陪浴,口爆,指划,🐻推,漫游,煽情,🉑🐍吻,🉑69,高跟丝袜,制服诱惑,激情啪啪,给你带来不一样的神仙体验 。 硬件: 165/45/B/24 车费: 1200/P 2200PP 联系老师: @tbtbtb0606 机器人: @yuji0009995555bot 标签: #颜值系 #服务 #嫩妹 北京交流群: @jmnu010a_a 北京大⭕奢侈品 @cgqlbj
🎉227🔥223❤221👍215😁213👏11🥰7🤩6
Showing the 7 most recent of 7 posts we hold for @JMNU010. 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“【集美师范大学】北京校区/天津校区” (@JMNU010), 6,771 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/JMNU010.
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.