Telegram RegisterThe public register of Telegram

Channel

EUtopia Labs

@EUtopiaLabs

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

152subscribers

+0 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-1001379334455
TypeChannel
Username@EUtopiaLabs
DescriptionEUtopia Labs 官方頻道 EUtopia.app // @jokebig2bot // @jokedealbot
CreatedBetween 1 March 2018 and 24 June 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/EUtopiaLabs

Growth

1526 August 2026 — 152 subscribers8 August 2026 — 152 subscribers6 August 20268 August 2026
2 measurements spanning 2 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 151–153 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 19:30152no change
6 Aug 2026, 23:35152first reading

Engagement

20 posts held, back to 24 June 2020the 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.

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 7 September 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
36
Videos
4
Links
36

Lifetime counters from Telegram’s own channel header, read 8 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

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 1 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 1reactions 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 24 June 2020 to 7 September 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

7 Sept 2023, 10:05 UTC≈2,650 views1 reactionsread 8 August 2026

If the bots are not working, try the /feedback command

1

7 Jan 2021, 12:19 UTC≈5,970 viewsread 8 August 2026

According to our testing, the following DNS servers does not appear to block hkchronicles.com : 根據我哋嘅測試 以下嘅DNS伺服器並冇封鎖 hkchronicles.com: 8.8.8.8 (Google DNS) 8.8.4.4 (Google DNS) 1.1.1.1 (Cloudflare DNS) 1.0.0.1 (Cloudflare DNS) 208.67.220.220 (OpenDNS) 208.67.222.222 (OpenDNS) 8.20.247.20 (Comodo Secure DNS) 8.26.56.26 (Comodo Secure DNS) 9.9.9.9 (Quad9) 149.112.112.112 (Quad9)

1 Oct 2020, 09:02 UTC≈4,730 viewsread 8 August 2026

出街之前請用scheduled msg留個人資料俾信任嘅人或者律師 多謝各位

11 Aug 2020, 03:54 UTC≈3,030 viewsread 8 August 2026
Photo

小弟睇到透心涼 #撐蘋果日報 #WeNeedAppleDaily #SupportAppleDaily

31 Jul 2020, 10:34 UTC≈2,430 viewsread 8 August 2026

一次兩個禮拜咁延遲就係濫權 一次延遲一年就唔係濫權

31 Jul 2020, 10:11 UTC≈2,000 viewsread 8 August 2026

屌你老母起撚埋乜撚明日大愚 收埋萬幾億就拎出嚟做抗疫基金啦 全民wfh未呀弱智

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

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

“EUtopia Labs” (@EUtopiaLabs), 152 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/EUtopiaLabs.

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.