Telegram RegisterThe public register of Telegram

Channel

【集美师大】深圳校区

@JMNUSZ

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

5,581subscribers

-156 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003914871852
TypeChannel
Username@JMNUSZ
CreatedBetween 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/JMNUSZ

Growth

5,5815,7475,6646 August 2026 — 5,737 subscribers7 August 2026 — 5,747 subscribers10 August 2026 — 5,694 subscribers12 August 2026 — 5,581 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -156. 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 5,556–5,772 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 22:435,581-113
10 Aug 2026, 06:385,694-53
7 Aug 2026, 15:165,747+10
6 Aug 2026, 20:055,737first reading

Engagement

12 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 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
4.99%
avg views ÷ 5,581 subscribers
Avg views / post
278
12 posts measured
Reaction rate
0.326%
reactions ÷ views · ER floor
Posts in window
12
of 12 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 3 of 12 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 11 August 2026
Posts held12 (6 August 202611 August 2026)
Views total3,341
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:57 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 01s
Average length
9s

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.

Reaction mix

3 reactions across 3 posts, in 1 kind.

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

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

11 Aug 2026, 06:25 UTC273 views1 reactionsread 12 August 2026
Photo

🌿艺名:#淼淼 💪段位:#辅导员(钻石) 🌏位置:#福田 💄编号:#SZJM384 课时费💰:2500p 5000pp 个人资料: 深圳cos圈甜美天花板 【香港🇭🇰在读学生】 (白虎) 真实:港大学生🉑证件 多套Cos JK 女仆 🉑私人订制 包天 空降✈🈲冒 👔标签:#极品推荐 #cos #舌吻 #69 #童颜萝莉 💋私聊:@JMNUsz001 →双向:@jmnusz001bot 深圳话题群:https://t.me/jmsdxsh

1

11 Aug 2026, 06:15 UTC242 viewsread 12 August 2026
Photo

🌿艺名:#朵朵 💪段位:#辅导员(钻石) 🌏位置:#南山 💄编号:#SZJM382 课时费💰:4000p 8000pp 个人资料:朵朵172冷白皮真实留学生兼职🉑验证 身高:172 年龄: 真实05 喜胖勿扰 地表颜值天花板 高素养 高情商 高学历 真实冷白皮 短期兼职提前预约 🈚️风尘气息 只见素质哥哥 本人主打反差感 素颜已经足够权威 穿衣大牌 时尚高级 首次⬇️💦 同城🉑见 幸运幸运 请降临我手心 ₊⁺🍀 ☘︎ ˖ ⁺ 👔标签:#极品推荐 #顶美 #舌吻 #69 #真人真照! #顶级体验! 💋私聊:@JMNUsz001 →双向:@jmnusz001bot 深圳话题群:https://t.me/jmsdxsh

11 Aug 2026, 06:12 UTC231 viewsread 12 August 2026
Photo

🌿艺名:#小甜 💪段位:#辅导员(黄金) 🌏位置:#南山 💄编号:#SZJM382 课时费💰:1388p 2388pp 👔标签:#可萝可御 #舌吻 #69 #户外 #cos #角色扮演 #女友感爆棚 #顶级服务 #配合度极高! 💋私聊:@T2002TRH →双向:@xitianjqbot 🫡报告反馈: 深圳话题群:https://t.me/jmsdxsh

8 Aug 2026, 05:11 UTC248 viewsread 8 August 2026
Photo

🌿艺名:#庆庆 💪段位:#辅导员(钻石) 🌏位置:#南山 💄编号:#SZJM377 课时费💰:2500p 5000pp 个人资料: 𝐇𝐞𝐢𝐠𝐡𝐭/ 170 • 𝐁𝐮𝐬𝐭/ C+ • 𝐀𝐠𝐞/ 02 偶尔兼职刚下💦 期待有缘人 𝙏𝙝𝙖𝙣𝙠𝙨 𝙮𝙤𝙪 •𝘽𝙤𝙨𝙨 💫💫💫 🌺高情商會來事 自带高级感 氣場十足 🌺活好不粘人 温柔 听话 懂事 耐心💯💯, 🌺人间妲己 温柔耐心 爱笑 🌺超敏感体质 一触即发可 请相信一定会给您带来终身难忘的邂逅 👔标签:#极品推荐 #空姐 #舌吻 #69 #高颜值 #好评推荐 💋私聊:@JMNUsz001 →双向:@jmnusz001bot 深圳话题群:https://t.me/jmsdxsh

8 Aug 2026, 04:42 UTC302 viewsread 8 August 2026
Photo

🌿艺名:#艾希 段位:#辅导员(白银) 🌏位置:#南山 编号:#SZJM0376 💰课费:1288p 2288pp 标签:#御姐 #kiss #69 #全套服务 #角色扮演 #sm 💓私聊:@Aixiok888 💓双向:@Aixiok866_bot 报告反馈:https://t.me/jmsdxsh/4/1600 深圳话题群:https://t.me/jmsdxsh

7 Aug 2026, 08:05 UTC436 viewsread 8 August 2026
Photo

🌿艺名:#鱼幼薇 💪段位:#辅导员(青铜) 🌏位置:#南山 💄编号:#SZJM375 课时费💰:1500p 2500pp 👔标签:#极品御姐 #舌吻 #69 #足交 #情趣 💋私聊:@yyw111 →频道:https://t.me/+zHD0EcQPqyg0YWI1 🫡报告反馈:暂无 深圳话题群:https://t.me/jmsdxsh

7 Aug 2026, 07:15 UTC442 views1 reactionsread 8 August 2026
Photo

🌿艺名:#白虎cos 💪段位:#辅导员(钻石) 🌏位置:#福田 💄编号:#SZJM374 课时费💰:4000p 8000pp 个人资料:本人真实生活自拍照请勿外传|假赔 身高/175 年龄/08 胸围/c 体重98斤 /天然白虎 dy本人小网红🉑验后台|接受任何情趣 ⚠️⚠️⚠️Cos服都很贵,出来接单没有带,如需Cos需要客户自费并提前预约 怕去的不是本人🉑提前沟通直接视频验证 #福田 #cos #🦜 #新人推荐 🌟安排预约: @zsrj51999 📲双向限制: @zsrj8888bot 👔标签:#白虎 #cos #舌吻 #69 #🦜 #极品 💋私聊:@JMNUsz001 →双向:@jmnusz001bot 深圳话题群:https://t.me/jmsdxsh

1

7 Aug 2026, 07:12 UTC260 viewsread 8 August 2026
Photo

🌿艺名:#梦珊 💪段位:#辅导员(青铜) 🌏位置:#南山 💄编号:#SZJM372 课时费💰:600p, 1200pp 👔标签:#御姐 #陪浴 #调情 #全套服务 💋私聊:@Shan8335 →双向:@Shan19_bot 🫡报告反馈:暂无 深圳话题群:https://t.me/jmsdxsh

7 Aug 2026, 05:59 UTC286 viewsread 8 August 2026
Photo

🌿艺名:#阿妤 💪段位:#辅导员(青铜) 🌏位置:#罗湖 💄编号:#SZJM367 课时费💰:800p 1500pp 👔标签:#纯欲 #舌吻 #69 #陪浴 #调情 #制服诱惑 💋私聊:@mljnzybw →双向:@anan520_mmbot 🫡报告反馈:https://t.me/jmsdxsh/4/15244 深圳话题群:https://t.me/jmsdxsh

6 Aug 2026, 08:50 UTC235 viewsread 6 August 2026
Photo

🌿艺名:#安琪娜 💪段位:#辅导员(青铜) 🌏位置:#南山 💄编号:#SZJM371 课时费💰:700p 1200pp 👔标签:#御姐 #舌吻 #69 #制服诱惑 #全套服务 💋私聊:@anqina_99109 →双向:@anqina_bot 🫡报告反馈:暂无 深圳话题群:https://t.me/jmsdxsh

6 Aug 2026, 08:27 UTC206 views1 reactionsread 6 August 2026
Photo

🌿艺名:#小曦 💪段位:#辅导员(钻石) 🌏位置:#福田 💄编号:#SZJM373 课时费💰:2500p 5000pp 个人资料:小曦 05年 166 99斤可爱小甜心 白🐯馒头笔 真🐻E保真(假赔总) 超敏感一碰就湿 完美体验 兼职短开 可解锁多体位 待宝宝如初恋❤️‍🔥希望缘分能让我们相遇 👔标签:#极品推荐 # 童颜巨乳#舌吻 #69 #好评推荐 💋私聊:@JMNUsz001 →双向:@jmnusz001bot 深圳话题群:https://t.me/jmsdxsh

1

6 Aug 2026, 08:22 UTC180 viewsread 6 August 2026
Photo

🌿艺名:#极品学妹 💪段位:#辅导员(钻石) 🌏位置:#福田 💄编号:#SZJM372 课时费💰:2500p 5000pp 个人资料:𝐁𝐮𝐬𝐭| C 𝐇𝐞𝐢𝐠𝐡𝐭|180cm Weight|48Kg 𝐀𝐠𝐞| 真实06 Degree|211 每个客人都说是他💦过的女人中最紧的 第一紧! 🉑舌吻🉑6⃣️9⃣️ 🎀纯天然妈生脸,通体雪白牛奶肌,细腻光滑、吹弹可破,无风尘味。 🎀完美身材比例,水蛇腰(只有53cm!)蜜桃臀 马甲线 👔标签:#极品学妹 #大长腿 #舌吻 #69 #水多 #敏感易高潮 #真人真照 #好评推荐 💋私聊:@JMNUsz001 →双向:@jmnusz001bot 深圳话题群:https://t.me/jmsdxsh

Showing the 12 most recent of 12 posts we hold for @JMNUSZ. 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 — 202,709 of 1,350,102entries 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 6 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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“【集美师大】深圳校区” (@JMNUSZ), 5,581 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/JMNUSZ.

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.