Telegram RegisterThe public register of Telegram
Telegram profile photo for 阿雅报告群

Channel

阿雅报告群

@yaya20268888

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

39subscribers

+7 since we began measuring on 5 October 2026

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

Register entry

Telegram ID-1003798978650
TypeChannel
Username@yaya20268888
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded5 October 2026
Last confirmed live13 November 2026
Measurements held5
Confirmed unchanged4 times, most recently 13 November 2026
On Telegramt.me/yaya20268888

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 22 October 2026 and assigned it the closest of 31 fixed categories, at 64% 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.

Growth

323935.55 October 2026 — 32 subscribers5 October 2026 — 32 subscribers9 October 2026 — 34 subscribers16 October 2026 — 36 subscribers22 October 2026 — 39 subscribers5 October 202622 October 2026
5 measurements spanning 17 days, net +7. 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 31–40 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Oct 2026, 20:3939+3
16 Oct 2026, 05:1636+2
9 Oct 2026, 15:5434+2
5 Oct 2026, 23:2232no change
5 Oct 2026, 22:4732first reading

Engagement

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

Reaction mix

4 reactions across 4 posts, in 1 kind.

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

Measured over the 20 most recent posts we hold, published 14 August 2026 to 3 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.

Recent posts

3 Oct 2026, 12:30 UTC27 viewsread 5 October 2026
Forwarded from @blossomsreview

#阿雅 @yaya2026999 800 南山 人照课表差异: 人照一致 优点: 时隔一个月来返食,老师依旧非常热情,进门就是一个大大的拥抱加蟒蛇吻,搞得我直接就想在沙发上办了。后来还是忍住先泡泡浴。服务质量一如既往地高。泡泡浴到一半还是忍不住了戴套开搞。一发之后休息一会洗澡。之后老师又做了很详细的服务,弟弟硬邦邦再来了一发。结束之后休息了一会顶不住老师的诱惑还想再来一次,但是实在是没力气了哈哈。歇了一会,意犹未尽。下次再来挑战三次 不足: 还是太瘦了,多吃点 补充: 课室干净,老师也很健谈 评分: 5 投稿信息: 时间: 2026-10-03 投稿人: 库奇 #历史投稿1737221239 投稿数: 1 提示:本频道已建立10万份报告库,检出抄袭即拉黑。 » 繁花资源 » 交流群组 » 我也要写报告

18 Sept 2026, 02:46 UTC114 viewsread 5 October 2026
Forwarded from @blossomsreview

#阿雅 @yaya2026999 800 南山 人照课表差异: 一致 优点: 颜值9分,第一次体验日式泡泡,体验感非常好,酥酥麻麻的感觉是其他地方完全体验不到的,服务直接给到夯,从来没有遇到过服务那么好,态度也是特别好,全程沟通交流不冷场,心理生理双重享受。 不足: 无 补充: 必返 评分: 5 投稿信息: 时间: 2026-09-17 投稿人: Bess... #历史投稿8391201435 投稿数: 1 提示:本频道已建立10万份报告库,检出抄袭即拉黑。 » 繁花资源 » 交流群组 » 我也要写报告

15 Sept 2026, 06:53 UTC126 viewsread 5 October 2026
Forwarded from @szfanhuabg

#阿雅 @yaya2026999 800 南山 人照课表差异: 一致 优点: 是我去过的服务天花板基本项目有的全有 尤其是泡泡浴 摸得受不了 无敌 不足: 无 补充: 想要服务型的来就对了 评分: 4 投稿信息: 时间: 2026-09-15 投稿人: ribi... #历史投稿7450982237 投稿数: 2 提示:本频道已建立10万份报告库,检出抄袭即拉黑。 » 繁花资源 » 交流群组 » 我也要写报告

9 Sept 2026, 15:46 UTC156 views1 reactionsread 5 October 2026
Forwarded from @blossomsreview

#阿雅 @yaya2026999 800 南山 人照课表差异: 基本一致,服务完全按照流程来 优点: 服务超级好,这么好多年没有体会过这个泡泡浴水床的服务了,一直很喜欢这个水床服务,自从东莞关闭以后,重新体验到了,但是他的这个水床服务呢,又跟东莞的不太一样,这个是日式的,但是有一样是一样的,那就是舒服是一样的. 不足: 没有 补充: 下次还来 评分: 5 投稿信息: 时间: 2026-09-09 投稿人: Diwu... #历史投稿8291698759 投稿数: 1 提示:本频道已建立10万份报告库,检出抄袭即拉黑。 » 繁花资源 » 交流群组 » 我也要写报告

❤1

9 Sept 2026, 09:17 UTC137 views1 reactionsread 5 October 2026
Forwarded from @szfanhuabg

#阿雅 @yaya2026999 800 南山 人照课表差异: 人照合一 优点: 地方好找,小区安全,服务流程很细,十分放松,泡泡浴完开始上课,技术牛逼。 不足: 无,满分 补充: 无 评分: 5 投稿信息: 时间: 2026-09-09 投稿人: 梅川 内库 #历史投稿1806232569 投稿数: 1 提示:本频道已建立10万份报告库,检出抄袭即拉黑。 » 繁花资源 » 交流群组 » 我也要写报告

❤1

8 Sept 2026, 16:01 UTC128 viewsread 5 October 2026
Forwarded from @SZFYJT

打桩报告:https://t.me/+oxZLXLYHtnowNjA0 验证留名:Luke 验证时间:9.8 修车水费:8 服务内容:日式泡泡浴,AB面服务 颜值身材 :身材苗条,长相甜美 体验细节 :第一次体验日式标准服务,感觉非常棒,还会日语叫床。口活一级棒 是否事逼 :否 优点缺点 :无 推荐程度 :10 老师艺名 :阿雅 老师联系 :@yaya2026999 温馨提醒 :报告仅供参考,不要太沉迷报告.自己体验一下

6 Sept 2026, 12:56 UTC136 viewsread 5 October 2026
Forwarded from @c800bg

800群出击报告 (https://t.me/GDPSZ ) 工兵留名:巴巴博一 出击时间:9月6日 老师花名:#阿雅 地理位置:#南山 上课支出:800/p 颜值身材:颜值高达9分人照一致,C罩杯圆润细腻 服务内容:日式泡泡水床+服务 出击体验:老师人比照片好看,第一次体验日式泡泡浴,很舒服的一次出击,水床结束之后还会帮洗,吹功一流,水床之后还有ab面服务,老师服务的很舒服,整体感觉非常好,一定会返 缺点:无。 联系方式: @yaya2026999 老师频道: https://t.me/yaya20269999 推荐程度:10/满分10.0分(强烈推荐) 群收录评级: (提交报告需要提供相关资料,如聊天记录,付款记录等,记录不会公开) 1、尽量写的客观一些,过于夸张吹捧或者字数太长会拒收; 2、免责声明:以上报告内容为当事人主观感受,并不构成出击建议;出击有风险,来都来了需谨慎。

3 Sept 2026, 10:16 UTC172 viewsread 5 October 2026
Forwarded from @blossomsreview

#阿雅 @yaya2026999 800 南山 人照课表差异: 基本一致,真人比图片好看 优点: 服务天花板这个毋容置疑了,热情主动,还时不时给来几句日语就很有感觉 不足: 没有,直接是完美 补充: 二刷, 评分: 5 投稿信息: 时间: 2026-09-03 投稿人: 结城结弦 #历史投稿7635154061 投稿数: 2 (该老师累计2次) 提示:本频道已建立10万份报告库,检出抄袭即拉黑。 » 繁花资源 » 交流群组 » 我也要写报告

2 Sept 2026, 16:15 UTC166 views1 reactionsread 5 October 2026
Forwarded from @blossomsreview

#阿雅 @yaya2026999 800 南山 人照课表差异: 人照一致,真人比照片还好看 优点: 服务很细致,之前没有体验过日式泡泡浴,这次来阿雅老师这里特地体验一次。可以说是深圳泡泡浴天花板了!泡泡抹在身上特别舒服,阿雅老师的胸推还有手法都很舒服,摸了一下就硬梆梆。玩了二十分钟之后就带我去把洗泡泡洗掉,洗的时候还带了水箫。洗完回床上又做了一遍服务,翻过来我硬的不行了,戴套冲刺,没几下就把我秒了。结束之后阿雅老师也陪着聊天,送水喝,态度特别热情。 不足: 太瘦了,能摸到肋骨,多吃点 补充: 上楼还是挺方便的,可以让老师帮远程开门 评分: 5 投稿信息: 时间: 2026-09-02 投稿人: Jacky #历史投稿1737221239 投稿数: 1 提示:本频道已建立10万份报告库,检出抄袭即拉黑。 » 繁花资源 » 交流群组 » 我也要写报告

❤1

30 Aug 2026, 14:54 UTC167 viewsread 5 October 2026
Forwarded from @blossomsreview

#阿雅 @yaya2026999 800 南山 人照课表差异: 一致 优点: 姐姐很善谈,很主动,身材好,态度好,环境好,课表写的都有,情绪价值拉满。 不足: 无 补充: 下次还反 评分: 5 投稿信息: 时间: 2026-08-30 投稿人: h #历史投稿7335364111 投稿数: 1 提示:本频道已建立10万份报告库,检出抄袭即拉黑。 » 繁花资源 » 交流群组 » 我也要写报告

30 Aug 2026, 12:30 UTC158 viewsread 5 October 2026
Forwarded from @blossomsreview

#阿雅 @yaya2026999 800 南山 人照课表差异: 一致 优点: 第一次体验日式泡泡,非常舒服,阿雅服务态度非常好,活也非常好,身材好,做的时候声音好听,跟说话两个版本,下次会再来 不足: 无 补充: 无 评分: 5 投稿信息: 时间: 2026-08-30 投稿人: jack... #历史投稿5441596816 投稿数: 2 提示:本频道已建立10万份报告库,检出抄袭即拉黑。 » 繁花资源 » 交流群组 » 我也要写报告

22 Aug 2026, 10:19 UTC184 viewsread 5 October 2026
Forwarded from @szfanhuabg

#阿雅 @yaya2026999 800 南山 人照课表差异: 无差异 优点: 泡泡浴头一次体验 感觉很舒服 服务很好 不足: 没有 补充: 无 评分: 5 投稿信息: 时间: 2026-08-22 投稿人: lili... #历史投稿7570220014 投稿数: 1 提示:本频道已建立10万份报告库,检出抄袭即拉黑。 » 繁花资源 » 交流群组 » 我也要写报告

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

Forward network

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.

Mentions

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

“阿雅报告群” (@yaya20268888), 39 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/yaya20268888.

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.