Telegram RegisterThe public register of Telegram
Telegram profile photo for 宝安首开🥤奈雪💦短期兼职🈷️

Channel

宝安首开🥤奈雪💦短期兼职🈷️

@naixuekeai820

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

748subscribers

-33 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002216009524
TypeChannel
Username@naixuekeai820
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/naixuekeai820

Topic

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 45% 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.

Growth

748781764.57 August 2026 — 781 subscribers8 August 2026 — 781 subscribers14 August 2026 — 775 subscribers21 August 2026 — 766 subscribers29 August 2026 — 759 subscribers5 September 2026 — 751 subscribers13 September 2026 — 748 subscribers7 August 202613 September 2026
7 measurements spanning 37 days, net -33. 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 743–786 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 14:38748-3
5 Sept 2026, 18:01751-8
29 Aug 2026, 02:46759-7
21 Aug 2026, 06:45766-9
14 Aug 2026, 23:05775-6
8 Aug 2026, 01:47781no change
7 Aug 2026, 18:33781first reading

Engagement

19 posts held, back to 3 February 2026the 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 19 posts for this entry, the most recent from 1 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
35s
Average length
18s

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.

Reaction mix

63 reactions across 16 posts, in 10 distinct kinds. The most used accounts for 36.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2336.5%
👍1219.0%
😍914.3%
😘69.52%
👏57.94%
💋23.17%
😁23.17%
🥰23.17%
🎄11.59%
🤗11.59%

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 16 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 63 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 3 February 2026 to 1 May 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

1 May 2026, 06:10 UTC466 views1 reactionsread 8 August 2026
Photo

🫐 ᯓ 𝗰𝗵𝗲𝗲𝗿𝘀⁾⁾🧃 阳光超给力☀️,今日宜快乐🥳 👉🏻 @naixue716 👉🏻 @naixue716bot

1

30 Apr 2026, 14:29 UTC492 views2 reactionsread 8 August 2026
Sticker

Sticker, posted without a caption

🤗1😁1

19 Apr 2026, 04:39 UTC675 views5 reactionsread 8 August 2026

深圳榨汁大队报告区:https://t.me/szzzbgq #宝安 #奈雪 【验证留名】:znhgb 【验证时间】:4.18 【修车水费】:800p 【服务内容】:课表都有 【颜值身材】:高挑美女 【凶器罩杯】:C 【体验细节】:迟到了十几分钟,老师没有催促 这点让人很舒服,老师身材非常好的,苗条,老师很热情的,简单交流一下,就洗漱上课。老师赤裸裸的样子太有诱惑了。很快就步入上课中。服务好,听话。老师下面很紧,包裹性很强,两个人很搭配,进出迎合很默契,也很投入。出水很多,老师高潮后,瘫软了,看着老师楚楚动人的样子,满足的一次出击,下次继续 【事逼行为】:无 【优点缺点】:皮肤雪白 【推荐程度】: 10满分,0颜值,0身材,0服务,0态度,0性价比(五个模块均给出评分) 【联系方式】:@naixue716 【温馨提醒】:报告仅供参考,请理性选择,切勿对号入座

👍21🎄1👏1

16 Apr 2026, 06:44 UTC635 views4 reactionsread 8 August 2026
Photo

📢 上课通知来啦~ 宝贝们记得准时上课哦🐾 👙 @naixue716 🤖 @naixue716bot

👍21👏1

16 Apr 2026, 06:01 UTC620 views1 reactionsread 8 August 2026
Photo

老师艺名:宝安 奈雪 验证方式:手势验证 身材比例:168cm 🐻胸C 消费价位:800P 1500PP 联系方式:@naixue716 频道简介:@naixuekeai820 双向联系:@naixue716bot

1

26 Mar 2026, 09:38 UTC≈1,230 views1 reactionsread 8 August 2026
Photo

开课啦宝子们 🍀 @naixue716 🍀 @naixue716bot

1

5 Mar 2026, 04:51 UTC≈1,900 views6 reactionsread 8 August 2026
Photo

开课啦宝宝们快来约课哦 🍀 @naixue716 🍀 @naixue716bot

3👍1👏1😘1

1 Mar 2026, 03:36 UTC≈2,100 views6 reactionsread 8 August 2026
Photo

三月 你好🌸 所有美好如期而至 心情日日皆欢喜。 约课: @naixue716 @naixue716bot

2👍1💋1😍1😘1

28 Feb 2026, 03:26 UTC≈2,050 views6 reactionsread 8 August 2026
Photo

快乐的方式有很多 约课找我☺️ 👉 @naixue716 👉 @naixue716bot

3👍2😘1

27 Feb 2026, 11:20 UTC≈1,840 views5 reactionsread 8 August 2026
Photo

约课了老公们晚上还有位哦 🍀 @naixue716 🍀 @naixue716bot

😍21👍1😘1

Showing the 12 most recent of 19 posts we hold for @naixuekeai820. 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.

Mentions

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 13 September 2026 — this entry's latest reading, not the date you are reading this.

“宝安首开🥤奈雪💦短期兼职🈷️” (@naixuekeai820), 748 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/naixuekeai820.

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.