2 measurements spanning 6 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โ4 and does not start at zero.
Measurement log โ every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 10:49
3
no change
7 Aug 2026, 19:01
3
first reading
Engagement
5 posts held, back to 6 April 2026 โ 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 5 posts for this entry, the most recent from 6 April 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Links
4
Lifetime counters from Telegramโs own channel header, read 13 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.
Showing the 5 most recent of 5 posts we hold for @en_zue72b9ez. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Handles this channel named that no longer answer
Dead references
2
handles named in this channelโs posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@en_zue72b9ez named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
Never seen alive
References a handle that is not a live channel โ we have no record it ever was one.
@fun_c72c47_bot named in 1 post, 14 August 2026 โ 14 August 2026
@lily_182fbb_bot named in 1 post, 14 August 2026 โ 14 August 2026
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 August 2026 โ this
entry's latest reading, not the date you are reading this.
โโ ๐โะฐโ๐ขโ ๐ฅโัโ โ๐โะตโะฐโฮบโ โ๐โ โ (@en_zue72b9ez), 3 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/en_zue72b9ez.
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.
