Telegram RegisterThe public register of Telegram

Channel

hanzhen.

@hannzhen

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

3subscribers

+0 since we began measuring on 13 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002275038705
TypeChannel
Username@hannzhen
Created27 January 2025measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/hannzhen

Growth

313 Aug 2026, 15:16 — 3 subscribers14 Aug 2026, 20:14 — 3 subscribers13 Aug 2026, 15:1614 Aug 2026, 20:14
2 measurements spanning 1 day. 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)SubscribersChange
14 Aug 2026, 20:143no change
13 Aug 2026, 15:163first reading

Engagement

20 posts held, back to 27 January 2025the 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 20 January 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
22s
Average length
22s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

20 Jan 2026, 04:23 UTC48 viewsread 13 August 2026
Poll

hi, kalo ufs sekarang masih ada yg mau gak ya?

  1. ngga0%

Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.

13 May 2025, 14:14 UTC204 viewsread 13 August 2026

becanda, tunggu aku bosen ya nanti aku ufsin (gak janji bakal bosen atau nggak)

27 Apr 2025, 06:16 UTC254 viewsread 13 August 2026
Poll

emang kalo ufs ada yang mau kah?

  1. mau96%
  2. nggak4%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

19 Apr 2025, 18:46 UTC245 viewsread 13 August 2026
Poll

gabut, ufsin hannzhen nggak yah?

  1. nay!0%

Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.

Showing the 12 most recent of 20 posts we hold for @hannzhen. 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 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

20 Jan 2026, 04:23 UTCAnonymous Poll23 voters

hi, kalo ufs sekarang masih ada yg mau gak ya?

  1. ngga0%

Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.

27 Apr 2025, 06:16 UTCAnonymous Poll74 voters

emang kalo ufs ada yang mau kah?

  1. mau96%
  2. nggak4%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

19 Apr 2025, 18:46 UTCAnonymous Poll45 voters

gabut, ufsin hannzhen nggak yah?

  1. nay!0%

Shares as published, totalling 0%. 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 20 most recent posts we hold, published 27 January 2025 to 20 January 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.

Citation-graph rank

Citation-graph rank — 757,262 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“hanzhen.” (@hannzhen), 3 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/hannzhen.

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.