Telegram RegisterThe public register of Telegram
Telegram profile photo for 许清禾

Channel

许清禾

@orzpo

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

884subscribers

+251 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-1002551725509
TypeChannel
Username@orzpo
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/orzpo

Topic

Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 19 September 2026 and assigned it the closest of 31 fixed categories, at 80% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

63389376313 August 2026 — 633 subscribers14 August 2026 — 676 subscribers22 August 2026 — 832 subscribers28 August 2026 — 875 subscribers6 September 2026 — 893 subscribers13 September 2026 — 884 subscribers88413 August 202613 September 2026
6 measurements spanning 31 days, net +251. 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 594–932 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 14:41884-9
6 Sept 2026, 01:38893+18
28 Aug 2026, 17:03875+43
22 Aug 2026, 13:44832+156
14 Aug 2026, 06:17676+43
13 Aug 2026, 11:31633first reading

Engagement

19 posts held, back to 24 July 2026the 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 19 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
9s
Average length
9s

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

10 Aug 2026, 10:08 UTC213 viewsread 13 August 2026
Forwarded from @foshanchuji

【时间】:2026-08-10 【老师】:许清禾 【留名】:雷王 【人照】:10 【颜值】:10 【身材】:10 【服务】:9 【态度】:10 【环境】:10 【综合】:9.83 【过程】: 老师是服务系,服务有AB面,课表里面的内容都有,而且老师每一项做的都很细致,特别是口,做的非常舒服,老师舌头灵活,一会舔一会转圈的,简直上天了。老师也非常配合。最后戴套啪啪,老师各种姿势都很配合,叫声也好听。

10 Aug 2026, 06:19 UTC211 viewsread 13 August 2026
Photo

做什么都一个人的话 会不会有点太厉害啦

8 Aug 2026, 10:17 UTC267 viewsread 13 August 2026
Video

你的日常生活里加上我 你会不会觉得挤

7 Aug 2026, 10:47 UTC285 viewsread 13 August 2026
Photo

小人得志听起来很坏 小狗得志听起来就很萌

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

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.

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

“许清禾” (@orzpo), 884 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/orzpo.

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.