16 Jan 2023, 16:38 UTCviews —
The account of the user that owns this channel has been inactive for the last 5 months. If it remains inactive in the next 30 days, that account will self-destruct and this channel may no longer have an owner.
Channel
G.G.BOX 時。格
@ggbox852
On this record: Growth · Engagement · Posts · Citations · Cite this entry
73subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001280625454 |
|---|---|
| Type | Channel |
| Username | @ggbox852 |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/ggbox852 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 13:36 | 73 | -1 |
| 21 Aug 2026, 16:24 | 74 | -1 |
| 9 Aug 2026, 21:15 | 75 | no change |
| 6 Aug 2026, 20:26 | 75 | first reading |
Engagement
7 posts held, back to 29 April 2022 — 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 7 posts for this entry, the most recent from 16 January 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
28 Jun 2022, 12:23 UTC343 viewsread 9 August 2026
荒廢了sor 主力IG 冇IG既PM ME
4 May 2022, 08:20 UTC417 viewsread 9 August 2026
Photo
是日笑話：俄新社聲稱在烏克蘭軍方總部發現了使用黑魔法的跡象（圖二），聲稱烏克蘭軍人試圖「淨化」其武器 ————- 轉載至香港軍事台 https://t.me/HKMilitary P.S. 大力推介 譚雅戰記 堅係正～^ _ ^
4 May 2022, 08:18 UTC291 viewsread 9 August 2026
Photo
https://t.me/HKMilitary/3882
3 May 2022, 17:45 UTC247 viewsread 9 August 2026
Photo
Yeah！ 我係保錡fans 嚟架（未睇error 遊同自肥前本來鍾意Dee哥多啲） 😭嗰陣佢嚟市集，禾開心到好似當年中學行山撞到發哥咁！不過佢走數冇follow番我🥹應該係太忙掛🥲一時客套講吓話科勞啫.係我認真咗啫。未聽既快手去聽！ https://youtu.be/iF2trFCpAmQ
29 Apr 2022, 03:34 UTC198 viewsread 9 August 2026
Photo
Photo, posted without a caption
29 Apr 2022, 03:34 UTC166 viewsread 9 August 2026
Photo
Photo, posted without a caption
Showing the 7 most recent of 7 posts we hold for @ggbox852. 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
Names
Channels on the register whose handles appear in this channel's posts.
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“G.G.BOX 時。格” (@ggbox852), 73 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/ggbox852.
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.