Telegram RegisterThe public register of Telegram
Telegram profile photo for 大芬私语

Channel

大芬私语

@zcezlj

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

433subscribers

+16 since we began measuring on 20 August 2026

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

Register entry

Telegram ID-1003426465163
TypeChannel
Username@zcezlj
CreatedBetween 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 August 2026
Last confirmed live11 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/zcezlj

Topic

Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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

41743342520 August 2026 — 417 subscribers21 August 2026 — 422 subscribers27 August 2026 — 426 subscribers3 September 2026 — 432 subscribers11 September 2026 — 433 subscribers20 August 202611 September 2026
5 measurements spanning 22 days, net +16. 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 415–435 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 14:18433+1
3 Sept 2026, 07:46432+6
27 Aug 2026, 23:34426+4
21 Aug 2026, 03:28422+5
20 Aug 2026, 13:45417first reading

Engagement

19 posts held, back to 9 May 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 20 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 04s
Average length
18s

Measured directly from 7 videos 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.

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.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 19 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 9 May 2026 to 20 August 2026, 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

8 Aug 2026, 15:23 UTC135 viewsread 20 August 2026
Photo

Photo, posted without a caption

Signed 龙岗大芬私语开课中

6 Aug 2026, 03:52 UTC162 viewsread 20 August 2026
Video

Video, posted without a caption

Signed 龙岗大芬私语开课中

28 Jun 2026, 05:26 UTC452 viewsread 20 August 2026
Photo

下雨天想在你的怀里躲雨,想听你心跳的声音

Signed 大芬私语开课中

19 Jun 2026, 04:01 UTC535 viewsread 20 August 2026

📢 开奖结果公布 🎁 活动:大芬私语开课中口令红包¥200元:@Zceqqcom 当前参与人数:1150人 🏆 中奖名单: 1. 破冰 奖品:口令红包¥200元 2. 楊 奖品:到店消费优惠¥100元 3. Sandy 奖品:到店消费优惠¥100元 4. D 奖品:到店消费优惠¥100元 5. 别炸 奖品:到店消费优惠¥100元 6. JM 奖品:到店消费优惠¥100元 7. 凉 奖品:到店消费优惠¥100元 8. 肥 奖品:到店消费优惠¥100元 9. TUTU.HU 奖品:到店消费优惠¥100元 10. 凌云 奖品:到店消费优惠¥100元 11. cccc 奖品:到店消费优惠¥100元 ⏰ 开奖时间:2026年06月19日 12时01分

Signed 深圳福利抽奖机器人

15 Jun 2026, 15:29 UTC570 viewsread 20 August 2026
Video

🎁 大芬私语开课中口令红包¥200元:@Zceqqcom 📦 奖品内容: 💰 口令红包¥200元 ×1 💰 到店消费优惠¥100元 ×10 👥 参与条件: 🔗 加入-深圳途虎修车大队 └ 💬 发言数大于 8 条 🔗 加入-深圳途虎修车榜 🔗 加入-深圳途虎修车报告 🔗 加入-大芬私语 ⏰ 开奖方式: 定时开奖: 2026年06月19日 12时00分00秒 ⚠️ 抽奖说明: 中奖者找当前管理员领取口令红包 优惠券找当前老师消费抵扣

Signed 深圳福利抽奖机器人

12 Jun 2026, 17:11 UTC633 views2 reactionsread 20 August 2026
Video

🎁 大芬私语开课中口令红包¥200元:@Zceqqcom 📦 奖品内容: 💰 口令红包¥200元 ×1 💰 到店消费优惠¥100元 ×10 👥 参与条件: 🔗 加入-深圳途虎修车大队 └ 💬 发言数大于 8 条 🔗 加入-深圳途虎修车榜 🔗 加入-深圳途虎修车报告 🔗 加入-大芬私语 ⏰ 开奖方式: 定时开奖: 2026年06月19日 12时00分00秒 ⚠️ 抽奖说明: 中奖者找当前管理员领取口令红包 优惠券找当前老师消费抵扣

2

Signed 深圳福利抽奖机器人

12 Jun 2026, 17:04 UTC572 viewsread 20 August 2026

✅ 已识别当前群组/频道 名称:大芬私语 类型:频道 Chat ID:-1003426465163 公开用户名:@zcezlj 请复制上面的 Chat ID,到后台验证条件里直接填写。 私密群/私密频道优先使用这个 ID,最稳定。 也可以随时发送 /chatid 再查询一次。

Signed 深圳福利抽奖机器人

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

Mentions

Named by 5 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.

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

“大芬私语” (@zcezlj), 433 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/zcezlj.

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.