Telegram RegisterThe public register of Telegram
Telegram profile photo for 乐怡

Channel

乐怡

@zhengleyi66

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

897subscribers

+63 since we began measuring on 9 October 2026

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

Register entry

Telegram ID-1002676357117
TypeChannel
Username@zhengleyi66
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 October 2026
Last confirmed live2 November 2026
Measurements held5
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/zhengleyi66

Topic

Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 26 October 2026 and assigned it the closest of 31 fixed categories, at 58% 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 the other topics.

Growth

834897865.59 October 2026 — 834 subscribers13 October 2026 — 857 subscribers19 October 2026 — 864 subscribers26 October 2026 — 866 subscribers2 November 2026 — 897 subscribers9 October 20262 November 2026
5 measurements spanning 24 days, net +63. 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 825–906 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Nov 2026, 23:40897+31
26 Oct 2026, 16:40866+2
19 Oct 2026, 13:06864+7
13 Oct 2026, 09:49857+23
9 Oct 2026, 13:22834first reading

Engagement

20 posts held, back to 18 September 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 20 posts for this entry, the most recent from 9 October 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
7s
Average length
7s

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

8 Oct 2026, 07:50 UTC219 viewsread 9 October 2026
Photo

开始考虑值不值得的时候已经不值得了

4 Oct 2026, 06:57 UTC600 viewsread 9 October 2026
Video

既然老天让我情路坎坷 那我财路一定四通八达

2 Oct 2026, 12:28 UTC786 viewsread 9 October 2026
Forwarded from @NNnmmtlu

【嫩妹报告】https://t.me/NNnmmtfzz 【老师艺名】郑乐怡 【联系方式】@zhengleyi 【所在位置】南海 【验证留名】跳歪 【验证时间】10.2 【修车费用】600 【颜值身材】娇小 【服务内容】课表有 【服务态度】热情 【优点缺点】没 嫩妹皮肤白 颜值在线 【推荐程度】10 【体验细节 胸大声甜,紧致水多,服务周到,配合度高,皮肤好,老师陪我洗澡,水中潇爽的飞起, 女上位特别会扭, ab面十分专业, 深喉到底,本人牛子太长,老师都干呕了,体验细致完美。会多刷 ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 👎🏿府上专员严查假报告!写手代谢出门右转! 报告提交:@Fndxbgbot

Showing the 12 most recent of 20 posts we hold for @zhengleyi66. 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 1 registered channel — 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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“乐怡” (@zhengleyi66), 897 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/zhengleyi66.

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.