Telegram RegisterThe public register of Telegram
Telegram profile photo for 中華電信

Channel

中華電信

@aaaaaszxa

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry

15,249subscribers

-115 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-1001911867684
TypeChannel
Username@aaaaaszxa
Description檔案庫
Created16 March 2023measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live21 August 2026
Measurements held14
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/aaaaaszxa

Growth

15,24915,36415,306.57 August 2026 — 15,364 subscribers8 August 2026 — 15,354 subscribers9 August 2026 — 15,342 subscribers10 August 2026 — 15,336 subscribers11 August 2026 — 15,321 subscribers12 August 2026 — 15,317 subscribers13 August 2026 — 15,313 subscribers14 August 2026 — 15,300 subscribers16 August 2026 — 15,294 subscribers17 August 2026 — 15,286 subscribers18 August 2026 — 15,277 subscribers19 August 2026 — 15,258 subscribers20 August 2026 — 15,254 subscribers21 August 2026 — 15,249 subscribers7 August 202621 August 2026
14 measurements spanning 14 days, net -115. 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,232–15,381 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 12:3715,249-5
20 Aug 2026, 15:0815,254-4
19 Aug 2026, 18:3215,258-19
18 Aug 2026, 15:1215,277-9
17 Aug 2026, 14:3215,286-8
16 Aug 2026, 06:0515,294-6
14 Aug 2026, 14:2815,300-13
13 Aug 2026, 06:4715,313-4
12 Aug 2026, 03:4215,317-4
11 Aug 2026, 04:3415,321-15
10 Aug 2026, 05:1615,336-6
9 Aug 2026, 05:0215,342-12
8 Aug 2026, 04:1215,354-10
7 Aug 2026, 09:1515,364first reading

Engagement

5 posts held, back to 16 March 2023the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 31 pagesof 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 5 posts for this entry, the most recent from 13 April 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
3

Lifetime counters from Telegram’s own channel header, read 22 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

12,088 reactions across 4 posts, in 15 distinct kinds. The most used accounts for 90.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍10,96190.7%
6595.45%
🤡540.447%
💩480.397%
🔥480.397%
🖕470.389%
👎430.356%
🌚420.347%
🤮420.347%
🥰390.323%
👏370.306%
🦄260.215%
😁230.19%
🍌140.116%
🏆50.041%

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 5 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 12,088reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 16 March 2023 to 13 April 2023, 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

13 Apr 2023, 06:35 UTC≈207,000 views872 reactionsread 22 August 2026

開心看片,推薦底下好群😈 羊媽發車 羊傳媒(TG大群}

👍651174👎14👏13😁13🖕4💩3

11 Apr 2023, 19:36 UTC≈131,000 views1,574 reactionsread 22 August 2026

群組規定 點我立即跳外群

👍1,430104😁10🥰8🍌7🏆5👏5🦄5

5 Apr 2023, 02:23 UTC≈192,000 views4,775 reactionsread 22 August 2026

👉工商合作總客服專線🤟 天天簽到保平安

👍4,560140🤡22👏19🔥17🌚10🍌7

16 Mar 2023, 18:32 UTC≈198,000 views4,867 reactionsread 22 August 2026

這裡是不用錢的檔案庫 只發檔不收檔❤️ 點我立刻進檔案庫

👍4,320241💩45🖕43🤮42🌚32🤡32🔥31

Showing the 5 most recent of 5 posts we hold for @aaaaaszxa. 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.

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

“中華電信” (@aaaaaszxa), 15,249 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/aaaaaszxa.

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.