Telegram RegisterThe public register of Telegram
Telegram profile photo for 安安的哥哥们

Channel

安安的哥哥们

@anan520888

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

872subscribers

+70 since we began measuring on 21 August 2026

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

Register entry

Telegram ID-1003449967147
TypeChannel
Username@anan520888
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded21 August 2026
Last confirmed live23 October 2026
Measurements held11
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/anan520888

Topic

Adult — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 80% 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

8021,5301,16621 August 2026 — 802 subscribers21 August 2026 — 802 subscribers22 August 2026 — 933 subscribers29 August 2026 — 1,530 subscribers1 September 2026 — 1,168 subscribers4 September 2026 — 982 subscribers12 September 2026 — 977 subscribers30 September 2026 — 959 subscribers11 October 2026 — 937 subscribers17 October 2026 — 876 subscribers23 October 2026 — 872 subscribers87221 August 202623 October 2026
11 measurements spanning 63 days, net +70. 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 693–1,639 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Oct 2026, 22:19872-4
17 Oct 2026, 18:08876-61
11 Oct 2026, 06:56937-22
30 Sept 2026, 00:59959-18
12 Sept 2026, 18:56977-5
4 Sept 2026, 19:59982-186
1 Sept 2026, 05:151,168-362
29 Aug 2026, 06:571,530+597
22 Aug 2026, 15:53933+131
21 Aug 2026, 14:30802no change
21 Aug 2026, 14:15802first reading

Engagement

20 posts held, back to 9 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 21 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2s
Average length
2s

Measured directly from 1 video 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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 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 1 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 9 August 2026 to 21 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

21 Aug 2026, 01:29 UTC235 viewsread 21 August 2026
Photo

🎰 成都优选骚御姐安安给大家发福利啦! 📮 参与条件: 🌏️ 归属地 四川 🪪 必须设置用户名 🎫 加入-安安的哥哥们 └ 🔑 发送口令﹝我爱安安﹞ 🎫 加入-成都修车优选(楼凤精选) └ 🔑 发送口令﹝我爱安安﹞ 🎫 加入-安安的哥哥们 🎫 加入-成都一号线修车(可搜索附近的人) ❗ 口令提示: 请先参与抽奖,再发送口令激活 🎁 奖品内容: 💰️ 优选积分 520 × 10 💰️ 口令红包 20 × 10 💰️ 口令红包52 × 2 ⚠️ 抽奖说明: 1.抽奖前设置好用户名 2.中奖后请48h内联系兑奖人兑奖,逾期不兑! 3.炸号,退群者不予兑奖 4.开奖前请在 @cdline1youxuan 任意评论一条以上帖子(最好截图证明),否则中奖不予兑换! 5.口令兑换联系 @saoan777 优选积分请联系 @baemon520 📅 开奖日期:(北京时间) 2026年08月26日 20时00分00秒

19 Aug 2026, 12:58 UTC235 viewsread 21 August 2026

成都嫩妹御姐高校车评 基本信息: 【时间】:2026-08-19 【老师】:安安 【留名】:惊风火扯 【老师年龄】:23 【是否代聊】:否 【修车水费】:600 【所在位置】:双流机场路 【服务内容】:浅舌吻、69、陪洗、深喉…图片上所有服务 评价得分: 【评价】:👍 好评 【人照】:9 【颜值】:9 【身材】:9 【服务】:10 【态度】:10 【环境】:10 【综合】:9.5 【过程】:坐在那柔软的沙发上,半躺着,舒服极了。安安给你递开水,像小猫般依偎身旁,谈笑风生,亲切自然,完全不像初见生疏。她的笑容,就像初冬的阳光,温暖永不冷场。 天光一点点逝去,言语间,人影间,情绪升温。两人对视,心意相通,默契渐生。交付“水费”之后,浴室共浴的那一刻,她用手轻轻替你搓洗,动作细腻得让人心慌,习惯未成,却已陶醉。洗尽尘埃,她又细心帮你擦净身体,蹲下帮你抹干脚上的水珠,每一处细节都浸满深意。 上床无半点花样挑逗,只有全套彻底,没有…

11 Aug 2026, 07:53 UTC618 views0 reactionsread 21 August 2026

https://t.me/saoananbot?start=4f3b6ef2 最新福利视频,宝宝们放心看

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

Named by 1 registered channel — 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.

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

“安安的哥哥们” (@anan520888), 872 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/anan520888.

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.