Telegram RegisterThe public register of Telegram
Telegram profile photo for 崽崽的小秘密

Channel

崽崽的小秘密

@ffzaizai1

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

5,636subscribers

-23 since we began measuring on 22 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002792090904
TypeChannel
Username@ffzaizai1
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/ffzaizai1

Growth

5,6365,6595,647.522 August 2026 — 5,659 subscribers22 August 2026 — 5,659 subscribers24 August 2026 — 5,653 subscribers27 August 2026 — 5,644 subscribers30 August 2026 — 5,636 subscribers22 August 202630 August 2026
5 measurements spanning 8 days, net -23. 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 5,633–5,662 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 12:185,636-8
27 Aug 2026, 04:075,644-9
24 Aug 2026, 00:135,653-6
22 Aug 2026, 20:155,659no change
22 Aug 2026, 20:005,659first reading

Engagement

17 posts held, back to 17 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.

ERR · 30 days
7.92%
avg views ÷ 5,636 subscribers
Avg views / post
447
2 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
2
of 17 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 22 August 2026
Posts held17 (17 July 202622 August 2026)
Views total893
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 20:15 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
22s
Average length
7s

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.

Reaction mix

11 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 90.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1090.9%
😁19.09%

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 8 of the 17 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 11 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 17 July 2026 to 22 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

31 Jul 2026, 07:00 UTC≈3,350 views1 reactionsread 22 August 2026
Photo

长安风起,南粤风吟 😒深圳长安群😒 持续整合深圳靠谱开课老师资源,更有严格验证审核,有资源主榜单方便选择,有精选推荐为各位出击之路点亮一盏明灯💡每个月群内还有大量现金红包和优质老师优惠卷以及群主赞助的白嫖卷 点击下方按钮或者链接 加入深圳长安群⬇️ https://t.me/Changan8976 深圳长安群各个频道群总入口

1

31 Jul 2026, 05:39 UTC≈2,980 views1 reactionsread 22 August 2026
Forwarded from @CABG00789Photo

学生留名:celen(建议留用户名增加真实度) 老师艺名:#坂田#崽崽#坂田崽崽 联系方式: @ffzaizai 出击时间:7.26 位置坐标:#深圳 #福田区 上课费用:P 人照程度:人照8分,黄白皮,真胸水滴奶,萝莉音台湾腔淫娃(满分10分) 服务内容:大蟒蛇,口得深且无齿感,连续喷水,性瘾强,服务意识非常强,情绪价值拉满。 出击详细体验: 本来老师台风天不上班的,没想到下午四五点突然说开课了,果断出击。老师非常热情,一般i人可能遭不住哈哈哈。 洗完刚上床直接饿狼一样扑上来,大蟒蛇一路舔到下面吸蛋口棒。骚话巨多,水巨多,轻轻一碰就一直有水流出来,太牛了。先用小玩具帮老师潮吹一次,直接带套开干,床上干累了换到客厅镜子前,先跪地抓奶吹然后换镜前后入,老师骚话太多了,配合她的台湾腔娃娃音真的好淫。回到床上又喷了一次,最后后入出水。 今天健身完过来的,状态不佳,但老师依旧态度非常好,而且真的是说来水就来水,一直在状态。难怪要一客一

😁1

22 Jul 2026, 09:44 UTC≈3,900 views2 reactionsread 22 August 2026
Forwarded from @wulingshenchePhoto

验证留名:楚留香 老师昵称:崽崽 电报号: @ffzaizai 出击时间:7.21 地市坐标:#深圳 #坂田 上课花费:700p 出击体验:一盏清茶,一帘月色,一场相逢落入人间烟火。初见崽崽如春水微澜,未曾想,竟遇一位温婉佳人。崽崽老师眉间藏笑,眸中含光,恰似三月桃花开于陌上,温柔了几分夜色,也惊艳了一段时光。 曾行过许多路,见过许多人,只愿寻一份自然相知的欢喜。无需繁华点缀,无需刻意雕琢,只在一言一笑之间,便能感受到那份难得的默契与从容。 她如兰花静放,不争春色,却自有清雅芬芳;如月照溪流,柔和明净,让人不觉沉醉其中。相处之时,仿佛置身烟雨江南,听风吟,赏花落,任岁月缓缓流淌 愿将这一程记忆,藏于心间。待多年以后回望,仍觉那日风轻云淡,那场相遇,恰好温柔了整个夜晚。 优点缺点:丰满热情好客 打分:五菱神车强力推荐

2

20 Jul 2026, 06:45 UTC≈3,600 views2 reactionsread 22 August 2026

深圳榨汁大队报告区:https://t.me/szzzbgq #龙岗 #崽崽 【验证留名】:je 【验证时间】:7-19 【修车水费】:700p 【服务内容】:课表 【颜值身材】:8 【凶器罩杯】:E 【体验细节】:跟老师约了好几次了,还是来老位置,性格和身材是我喜欢的类型,奶子很大,皮肤白嫩,还是一起洗澡完回到床上,舌头很灵活,深喉很猛, 太有感觉了,几分钟后开始戴套爱爱,各种姿势冲刺,小逼逼插进去很润很紧,还是这么多水,完事后在怀里躺了一会,情绪价值拉满。 【事逼行为】:无 【优点缺点】:E人,活好情绪价值很足 【推荐程度】: 9/10满分,0颜值,0身材,0服务,0态度,0性价比(五个模块均给出评分) 【联系方式】:@ffzaizai 【温馨提醒】:报告仅供参考,请理性选择,切勿对号入座

2

20 Jul 2026, 05:19 UTC≈2,580 views4 reactionsread 22 August 2026
Photo

老师艺名:龙岗 崽崽 验证方式:手势验证 身材比例:162cm 🐻胸E 消费价位:700P 1300PP 联系方式:@ffzaizai 频道简介:@ffzaizai1 双向联系:@ffzaizai3bot 全国榨汁:@quanguozz 报告区:@szzzbgq 深圳推广员:@zztgy(永久唯一账号)

4

19 Jul 2026, 02:58 UTC≈3,020 viewsread 22 August 2026
Forwarded from @H800CJBG

800群出击报告( https://t.me/CAT800fx ) 工兵留名:马一博 出击时间:7.18 老师花名:#崽崽 地理位置:#坂田 上课支出:700p 颜值身材:丰满御姐 服务内容:陪洗 吹做 出击体验:一进门很热情接待,动漫口音很独特,胸是真挺大的。老师是e人,基本上不会有空场没话的时候,陪洗完之后选衣服,大蟒蛇开场,狂野摸一顿,发现下面水很多,进入正戏,换了三个姿势最后出水。 优点缺点:服务意识很强,肉嘟嘟的,喜欢bbw的推荐。 联系方式:@ffzaizai 推荐程度:/满分10.0分 群收录评级: (提交报告需要提供相关资料,如聊天记录,付款记录等,记录不会公开) 1、尽量写的客观一些,过于夸张吹捧或者字数太长会拒收; 2、免责声明:以上报告内容为当事人主观感受,并不构成出击建议;出击有风险,来都来了需谨慎。

18 Jul 2026, 10:49 UTC≈2,760 views0 reactionsread 22 August 2026
Video

我可以陪你吃苦,你能帮我去上班吗🫠🫠🫠

18 Jul 2026, 06:32 UTC≈2,330 views0 reactionsread 22 August 2026
Forwarded from @spikeniubiPhoto

上课地址:#坂田 老师名字:#崽崽 老师账号:@ffzaizai 上课时间:7月17 上课花费:700 颜值身材:162的身高,对于我来说不管后入还是站着的姿势都很nice,颜值属于:丰满可爱,温婉丰腴,热情活泼,没有浓妆艳抹,真实自然! 服务内容:XCZ 上课体验:春风不解风情,崽崽老师风情万种,长夜漫漫无心睡眠,出击崽崽老师,翻云覆雨直到精疲力尽。 一直想找一个丰满热情不冷场,还要胸大的老师,就想体验那种女友般温柔乡醉生梦死的感觉,各大群里天天寻找,到最后却不期而遇,崽崽老师有着丰腴多姿的身材,那对E胸可以让你爱不释手,留连忘返,主动热情,可以把弄得浴火风身,上位的风骚摇动,没有定力的三秒撑不过,鱼水之欢时,声音淫语不断,刺激你的神经,让你飘飘欲仙如痴如醉,国牌运动力度,深度,速度,湿度,四维一体,让你躺着享受着语无伦次的快感,这也使我瞬间被秒,丢人呀!细节就不多说,可以自去亲身体验…… 优点缺点:无 优点:热情开朗,配合度

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

Citation-graph rank

Citation-graph rank — 976,723 of 1,629,518 entries 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.

Forward network

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

“崽崽的小秘密” (@ffzaizai1), 5,636 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/ffzaizai1.

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.