Telegram RegisterThe public register of Telegram
Telegram profile photo for 成都外围❗️成都包养❗️成都上门❗️成都学生会

Channel

成都外围❗️成都包养❗️成都上门❗️成都学生会

@abaaa952

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

30,843subscribers

+12,933 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001621654788
TypeChannel
Username@abaaa952
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/abaaa952

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

17,91030,84324,376.57 August 2026 — 17,910 subscribers8 August 2026 — 17,912 subscribers9 August 2026 — 18,594 subscribers9 August 2026 — 19,188 subscribers10 August 2026 — 19,187 subscribers11 August 2026 — 19,177 subscribers12 August 2026 — 19,171 subscribers14 August 2026 — 19,136 subscribers15 August 2026 — 19,127 subscribers17 August 2026 — 19,114 subscribers18 August 2026 — 19,088 subscribers19 August 2026 — 19,056 subscribers20 August 2026 — 19,048 subscribers21 August 2026 — 19,041 subscribers22 August 2026 — 19,025 subscribers24 August 2026 — 18,997 subscribers25 August 2026 — 18,969 subscribers26 August 2026 — 18,956 subscribers27 August 2026 — 18,952 subscribers28 August 2026 — 19,532 subscribers30 August 2026 — 19,512 subscribers31 August 2026 — 19,504 subscribers1 September 2026 — 19,496 subscribers2 September 2026 — 20,248 subscribers3 September 2026 — 20,236 subscribers4 September 2026 — 21,347 subscribers8 September 2026 — 24,611 subscribers11 September 2026 — 29,073 subscribers13 September 2026 — 30,843 subscribers7 August 202613 September 2026
29 measurements spanning 36 days, net +12,933. 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 15,970–32,783 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
13 Sept 2026, 01:3930,843+1,770
11 Sept 2026, 00:3929,073+4,462
8 Sept 2026, 04:2024,611+3,264
4 Sept 2026, 21:3621,347+1,111
3 Sept 2026, 06:2420,236-12
2 Sept 2026, 02:2320,248+752
1 Sept 2026, 04:4519,496-8
31 Aug 2026, 03:5419,504-8
30 Aug 2026, 02:0819,512-20
28 Aug 2026, 22:3419,532+580
27 Aug 2026, 21:1418,952-4
26 Aug 2026, 21:3618,956-13
25 Aug 2026, 18:0318,969-28
24 Aug 2026, 17:5418,997-28
22 Aug 2026, 23:5419,025-16
21 Aug 2026, 10:1619,041-7
20 Aug 2026, 10:2519,048-8
19 Aug 2026, 11:4619,056-32
18 Aug 2026, 11:1419,088-26
17 Aug 2026, 10:2419,114first reading

Engagement

48 posts held, back to 7 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 54 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.10%
avg views ÷ 30,843 subscribers
Avg views / post
340
28 posts measured
Reaction rate
0.185%
reactions ÷ views · ER floor
Posts in window
28
of 48 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 28 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 2 September 2026
Posts held48 (7 August 20262 September 2026)
Views total9,509
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 01:03 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
3m 59s
Average length
9s

Measured directly from 27 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

4 reactions across 3 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 7 of the 48 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 48 most recent posts we hold, published 7 August 2026 to 2 September 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

2 Sept 2026, 10:14 UTC60 viewsread 3 September 2026
Photo

⚠️ 请勿给妹妹现场展示本频道 🌟🌟 查看成都大圈资源 🌟🌟 查看成都中圈资源 🌟🌟 高端外围导航入口 🌟🌟 包养包月导航入口 🌟🌟 客户评价反馈频道 🌟🌟 客服大蜜蜜:@CY9818 🌟🌟 双向客服:@cy918_bot

2 Sept 2026, 10:12 UTC61 views1 reactionsread 3 September 2026
Photo

成都三毛:冰清玉洁 清纯可爱 一次牵手 回味无穷 你的初戀情人𝗶𝗻𝗴...✨ Age:08年 身高:168胸围:D 身材高挑 五官精致 皮肤雪白 性格温柔 ⚠️拒绝低素质、议价

1

2 Sept 2026, 10:12 UTC57 viewsread 3 September 2026
Photo

成都三毛⁵ ꪝ新人173学生兼职 ✯06年✯身高173✯ ✯体重98✯🐻C+✯冷白皮✯ ✯极品高白纯天花板✯校花代言人✯ ✯模特身材✯天使面容✯千娇百媚 ✯敏感体质✯易高潮✯体验感超棒 ✯自带仙女buff ✯ 擅聊天✯高情商 ✯亭亭玉立✯楚楚动人✯落落大方 ✯皮肤光滑无纹身✯大长腿A4腰 ✯主动配合✯女友般甜蜜感觉童颜 ✯主动向哥哥索吻的小妖精✯ ✯女友感十足 好评率超高✯

31 Aug 2026, 10:57 UTC556 viewsread 3 September 2026
Photo

⚠️ 请勿给妹妹现场展示本频道 🌟🌟 查看成都大圈资源 🌟🌟 查看成都中圈资源 🌟🌟 高端外围导航入口 🌟🌟 包养包月导航入口 🌟🌟 客户评价反馈频道 🌟🌟 客服大蜜蜜:@CY9818 🌟🌟 双向客服:@cy918_bot

31 Aug 2026, 10:57 UTC183 viewsread 3 September 2026
Photo

成都三毛极品萝莉 162C 06年 身高:162 🐻:C 体重45kG ·穿着打扮洋气 💓只接待素质客户 温柔体贴 懂事 智慧有内涵 我希望我不是被選擇 而是被熱愛 遇见的都是天意 拥有的都是幸运🌸

31 Aug 2026, 10:57 UTC106 viewsread 2 September 2026
Photo

成都三毛🏠170C 兼职小网红,20岁,170极品小纯,上粉下嫩,可爱乖巧,纯女友系,🉑️蛇纹

30 Aug 2026, 07:53 UTC901 viewsread 2 September 2026
Photo

⚠️ 请勿给妹妹现场展示本频道 🌟🌟 查看成都大圈资源 🌟🌟 查看成都中圈资源 🌟🌟 高端外围导航入口 🌟🌟 包养包月导航入口 🌟🌟 客户评价反馈频道 🌟🌟 客服大蜜蜜:@CY9818 🌟🌟 双向客服:@cy918_bot

30 Aug 2026, 07:53 UTC154 viewsread 2 September 2026
Photo

成都三毛🏠08甜妹刚下水 冰清玉洁 清纯可爱 一次牵手 回味无穷 你的初戀情人𝗶𝗻𝗴...✨ Age:08年 身高:168胸围:D 身材高挑 五官精致 皮肤雪白 性格温柔 ⚠️拒绝低素质、议价

30 Aug 2026, 07:53 UTC41 viewsread 30 August 2026
Photo

成都三毛🏠 ʜɪɢʜᴛ/172ᴄᴍ ·ᴡᴇɪɢʜᴛ/𝟒𝟓 ᴋɢ ·Bust/𝟑𝟒D ▪️𝐀𝐠𝐞年龄/ 𝟎𝟐年 ▪️Occupation/兼职衣服拍摄🎬模特 健身达人 ▪️Hobby / 游戏 旅游 拍照 健身 美食 ⚈ 奶白肤色 小野猫 ⚈ 绝美🍑臀 马甲线 会抖臀 ⚈ 前凸后翘 欧美身材 卡戴珊类型

29 Aug 2026, 10:11 UTC103 viewsread 30 August 2026
Photo

身高:170 胸围:D🐻, 年纪:20 极品高白纯,优雅温柔,冷白皮,自然脸无整,性格好嘴巴甜,会提供情绪价值,给你初恋女友般体验

29 Aug 2026, 10:11 UTC837 viewsread 30 August 2026
Photo

⚠️ 请勿给妹妹现场展示本频道 🌟🌟 查看成都大圈资源 🌟🌟 查看成都中圈资源 🌟🌟 高端外围导航入口 🌟🌟 包养包月导航入口 🌟🌟 客户评价反馈频道 🌟🌟 客服大蜜蜜:@CY9818 🌟🌟 双向客服:@cy918_bot

29 Aug 2026, 10:11 UTC54 viewsread 29 August 2026
Photo

成都三毛🏠00后可清纯可御姐 净高172D🐻 标准前凸后翘🌟 兼职 随时退圈✨ 高素质 性感 开朗性格✨ 超级敏感体质

Showing the 12 most recent of 48 posts we hold for @abaaa952. 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 3 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 13 September 2026 — this entry's latest reading, not the date you are reading this.

“成都外围❗️成都包养❗️成都上门❗️成都学生会” (@abaaa952), 30,843 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/abaaa952.

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.