宝宝们:如有联系不上,加我QQ:1824486997
❤1

Channel
@junjunaini
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
327subscribers
+71 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004336289453 |
|---|---|
| Type | Channel |
| Username | @junjunaini |
| Created | 26 June 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/junjunaini |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 23:16 | 327 | +67 |
| 8 Aug 2026, 09:15 | 260 | no change |
| 7 Aug 2026, 14:36 | 260 | +4 |
| 7 Aug 2026, 13:47 | 256 | first reading |
17 posts held, back to 26 June 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 pageof 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 7 August 2026 |
|---|---|
| Posts held | 17 (26 June 2026 – 7 August 2026) |
| Views total | 6,540 |
| Reactions total | 13 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 09:15 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.
27 reactions across 13 posts, in 3 distinct kinds. The most used accounts for 55.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 15 | 55.6% | |
| 👍 | 8 | 29.6% | |
| 👎 | 4 | 14.8% |
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 15 of the 17 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 27reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 26 June 2026 to 7 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.
宝宝们:如有联系不上,加我QQ:1824486997
❤1
杭州开课资讯分享: 颜值:8 身材:8 服务:9 时间:8.6 联系方式:@hufhjjkg 细节:看到新来的君君老师,正好离得不远,就抱着试试看的心态约了时间,长篇流水帐就不写了,直接说几个让我觉得值回票价的点: 1、服务到位,从进门到结束,流程该有的都有,节奏把控的很好,细节上也挺用心,不是那种机械走流程的感觉,说实话,在杭州现在这个环境下,能体验到这种服务水准,有点意外惊喜 2、情绪价值给足,全程不催不赶,这点必须重点夸,不管是开始前的聊天铺垫,还是结束后的收拾寒暄,老师都很有耐心,不急不躁,完全没有那种完事走人的压迫感。聊天气氛也自然,整个过程像朋友相处,心态很放松 3、照片跟本人八分相似,没有照骗的落差感,结合这个颜值,服务态度和价位,真的可以说是性价比天花板,反正我这次没踩雷,后续应该会考虑返场。 该报告使用 @hzkaikebot 生成,如有任何疑问请联系 @fugezhiyou
❤2
定期检查是对身体的负责
👍1
毛多多的,宝宝喜欢吗😘
❤2👍1
【快乐星球报告榜】 https://telegram.me/Hshdhbdgsu 【验证留名】:y 【验证时间】:7.30 【出击老师】:君君 @hufhjjkg 【所在地区】:拱墅区 【修车水费】:一课 【人照相似】:9.2 【大致年龄】:26 【身高体重】:160/95 【服务态度】:热情主动无法抗拒 【体验过程】: 老师约好时间,提前10分钟到达地点,停车方便,室内一早已经开好了空调,也是觉得舒服。老师很开朗热情,交上了水费开始清洁共浴。清洗的都很仔细,擦干后上床开始正事。直接先一个大蟒蛇,还要用上了力气恨不得喘不过气。接着是很认真的攻击我的两点,一路向下面推进,仔仔细细舔了整个奔周区域,又接上舒服的口活,真的很懂啊。一阵阵舒爽袭来,赶紧戴上了护具开始攻击,老师的女上,热情感染了我,就算是被夹住了,我也用力顶回去。不管是换什么姿势,都是双向奔赴的热情互动,最终都还是全部喷发了。躺着休息一会再洗一趟,穿戴好了告别出门。 【…
❤1
宝宝们,有空可约,有课室,可上门😘😘
❤1
周末了宝宝们都休息了吗?正常开课约起来哟!
❤2
艺名:君君 颜值:8.9 身材:9 服务:9.2 时间:7月22 联系方式:@hufhjjkg 细节:老师笑容甜美,说话温柔,长相清秀,身材也很棒,还是护士出身,情绪价值拉满,聊天有情商。一进入正题,她就主动提出跟我一起洗澡。洗澡时她帮我仔细擦拭身体,擦完后回到床上,换上了我喜欢的那套情趣制服。老师的身材把制服撑得特别有味道,性感极了,我的小弟弟瞬间就有了反应,她的两个雪乳手感绝佳,给我口的时候,她一直抬眼看着我,那眼神太勾人了,老师的口活真的很棒,我很快就顶不住了。她熟练地带上小雨伞,翻身坐上来就开始疯狂摇动,屁股激烈地撞击着我,嘴里还不断说着淫荡的话,最要命的是她下面又会夹又会吸,换了几个姿势后,不到10分钟我就忍不住交枪了。完事后她也没急着催我洗澡,我们又抱在一起聊了一会儿,才一起去洗澡。整体非常满意 该报告使用 @hzkaikebot 生成,如有任何疑问请联系 @fugezhiyou
❤1👍1
宝宝们,如有联系不上的,请加QQ:1824486997
❤3👎1
【快乐星球报告榜】 https://t.me/Hshdhbdgsu 【验证留名】:be 【验证时间】:7.12 【出击老师】:君君 @hufhjjkg 【所在地区】:拱墅 【修车水费】:500 【人照相似】:9 【大致年龄】:26 【身高体重】:160/95 【体验过程】: 老师人比较好,身材瘦瘦的,腰细腿长,摸起来手感很不错。进门后她挺主动的,先帮我洗澡,洗完还拿毛巾仔细擦干。开始服务的时候,先是简单的口,口活湿润不生硬。后面转正戏打桩,她配合度挺高,一直在轻轻叫床,声音软软的,听着还挺舒服的。她服务的时候比较细心,整个过程她没催时间,房间也干净,户型看着舒服也很紧,完事之后她又主动帮我洗了一次澡。 【推荐程度】:96(满分💯) 【温馨提醒】:报告仅供参考,请理性选择,切勿对号入座。
❤1
宝宝们,正常开课哦😘
❤1👍1👎1
杭州开课资讯分享: 颜值:9分 身材:9分 服务:课表 时间:7.3 联系方式:@hufhjjkg 【服务态度】:服务态度很好,很配合 【体验过程】: 老师是新人且本人自聊,真人比照片更有味道,有种惊艳高级感,但熟悉后又落落大方,感觉像老朋友一样,服务是没的说就是职业的会所也不能这样顶,一是口活儿特别好,边口边有眼神交流,而且时间很久,你不说停老师就一直口,二是做的时候很投入,风骚主动,就是鸡鸡被夹的又舒服又麻的感觉,再加上言语挑逗,情绪价值拉满,真的是那句骑肥马操瘦逼太贴切了,后面第二次做的时候做着做着感觉一股暖流,真的舒服的要死,三是做完之后,没想到老师还有聊天,情绪价值给到位,而且不是敷衍那种,而是很用心那种,感觉真的是宝葴老师,总结和提醒一下:两课才能真正体会到老师的高性价比服务,提醒的是老师是短期兼职,想上课的同学抓紧时间 【推荐程度】:90(满分💯) 【温馨提醒】:报告仅供参考,请理性选择,切勿对号入座。 该报…
👍2
Showing the 12 most recent of 17 posts we hold for @junjunaini. 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 — 1,102,074 of 1,481,217entries 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.
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 2 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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“君” (@junjunaini), 327 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/junjunaini.
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.