5 measurements spanning 8 days. 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 2,232–2,235 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
15 Aug 2026, 14:57
2,233
-2
11 Aug 2026, 19:32
2,235
+3
8 Aug 2026, 12:37
2,232
-1
7 Aug 2026, 16:32
2,233
no change
7 Aug 2026, 16:28
2,233
first reading
Engagement
16 posts held, back to 14 December 2025 — 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 · 30 days
73.1%
avg views ÷ 2,233 subscribers
Avg views / post
1,630
5 posts measured
Reaction rate
3.05%
reactions ÷ views · ER floor
Posts in window
5
of 16 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 5 August 2026
Posts held
16 (14 December 2025 – 5 August 2026)
Views total
8,164
Reactions total
249
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
7 Aug 2026, 16:32 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.
Reaction mix
541 reactions across 13 posts, in 23 distinct kinds. The most used accounts for 18.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
98
18.1%
🤣
84
15.5%
😭
79
14.6%
😱
41
7.58%
🤪
38
7.02%
🤡
35
6.47%
🙏
31
5.73%
🌚
27
4.99%
👍
25
4.62%
😁
13
2.40%
🤬
13
2.40%
💔
9
1.66%
🎉
8
1.48%
💩
7
1.29%
🖕
7
1.29%
👀
5
0.924%
😍
5
0.924%
🤔
5
0.924%
👎
4
0.739%
🫡
3
0.555%
3 further kinds
4
0.739%
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 13 of the 16 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 541reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 14 December 2025 to 5 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.
【公告】一些 Q&A
如何判断自己的 giffgaff 号码是否已被封禁？
由于 giffgaff 官方在回复中明确表示 “we reserve the right to suspend the account without prior notice”，即有权在不事先通知的情况下暂停服务，因此部分用户在号码被封停后，可能不会收到任何短信或邮件提醒。
根据多位已被封号用户的反馈，封号后可能会出现以下情况之一或同时出现：
1. 无法使用手机号登录 giffgaff 官网，使用手机号登录时提示：“Oops, wrong mobile number or password”（见图 1）
2. 使用 member name 登录后，在 My credit 页面显示为 Not available，而非此前正常显示的余额（见图 2）
若出现以上情况，通常可视为该号码已被官方暂停服务。
号码被封后我可以做什么？
若您的号码被封停，可尝试以…
🙏14❤4🎉3
Showing the 12 most recent of 16 posts we hold for @giffgaff_403. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 16 most recent posts we hold, published 14 December 2025 to 5 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
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.
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 15 August 2026 — this
entry's latest reading, not the date you are reading this.
“403 阿姨 gg 物流中心状态公告” (@giffgaff_403), 2,233 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/giffgaff_403.
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.
