Telegram RegisterThe public register of Telegram
Telegram profile photo for 奶崽崽

Channel

奶崽崽

@zaizai5223

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

767subscribers

+215 since we began measuring on 4 November 2026

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

Register entry

Telegram ID-1004433297535
TypeChannel
Username@zaizai5223
CreatedBetween 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 November 2026
Last confirmed live5 November 2026
Measurements held2
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/zaizai5223

Growth

552767659.54 Nov 2026, 15:22 — 552 subscribers5 Nov 2026, 14:24 — 767 subscribers4 Nov 2026, 15:225 Nov 2026, 14:24
2 measurements taken within a single day, net +215. 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 520–799 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 14:24767+215
4 Nov 2026, 15:22552first reading

Engagement

20 posts held, back to 12 October 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.

ERR · 30 days
48.8%
avg views ÷ 767 subscribers
Avg views / post
374
19 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 November 2026
Posts held20 (12 October 2026 – 4 November 2026)
Views total7,112
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Nov 2026, 15:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
4s
Average length
1s

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

Recent posts

Telegram’s own ‘edited’ marker: 0 of 20 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

4 Nov 2026, 06:21 UTC142 viewsread 4 November 2026
Photo

🎰 【骑士团☆崽崽 半价活动】 🎫 加入的前置频道: 🎫 加入 —— 广州少女御姐榜 🎫 加入 —— 广州少女御姐骑士团 🎫 加入 —— 广州少女御姐预备榜 🎫 加入 —— 广州少女御姐甄选😘 🎫 加入 —— 骑士团预备群 🎫 加入 —— 奶崽崽 🎟️ 要求活动期间群内发言数 20 🎁 奖品内容: 半价p × 1 💡 活动说明: 👉🏻① 开奖时间起(7天内兑奖,过期作废) 👉🏻② 炸号中奖作废 (老师可以拒绝兑奖) 👉🏻③ 出击完7日内提供详细的报告提交: 「严莉莉」 @yanlili_bot 否则拉黑并通报。 👉🏻④ 禁止转让或买卖,否则拉黑名单挂榜。 📢为保证老师的利益,请老师兑奖严格按照机器人🤖推送的 开奖信息 跳转兑奖! 📅 开奖日期: (UTC + 8) 2026年11月06日 14时19分32秒 ⚡️ 加成说明: ⚡️ 加成消耗:6个少女币🎖 ⚡️ 加成次数:8 ⚡️ 额外消耗:每次加3个…

29 Oct 2026, 05:26 UTC274 viewsread 4 November 2026
Forwarded from @GBTBGBD

【工兵报告】https://t.me/GZGBTBT 【老师艺名】崽崽 【联系方式】@zaizai52o 【所在位置】天河 【验证留名】公交车 【验证时间】10.25 【修车费用】1500pp 【颜值身材】大奶嫩妹 【服务内容】课表一条龙 【服务态度】满意 【优点缺点】喜欢吃大奶,享受情绪价值的上 【推荐程度】10分 【体验细节】根据指引准时到科室,开门看到崽崽是我喜欢的类型,跟照片差不多,果断交水费跟崽崽一块去洗澡,脱衣服看到崽崽的大奶,直接流口水哈哈洗完澡后开始反向服务,亲耳朵脖子,慢慢往下亲,吸奶的时候反馈很真实,声音也很骚,随后开始舔,下面挺粉嫩的,掰开吸崽崽舔的逼一颤一颤的,反应很强烈,舔了没一会就高潮了 然后开始带套做爱,鸳鸯时她的身子软得像水,一双大腿又白又嫩,摸上去光滑细腻,怎么都舍不得放开。全程崽崽配合得特别主动,各种姿势都来者不拒,身体柔软又敏感,叫声和喘息都恰到好处,既不矫情也不冷场。整体体验非常丝滑,满意…

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

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

“奶崽崽” (@zaizai5223), 767 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/zaizai5223.

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.