Telegram RegisterThe public register of Telegram
Telegram profile photo for 涵涵

Channel

涵涵

@zzxbdx

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

459subscribers

+412 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-1003973839387
TypeChannel
Username@zzxbdx
Created20 August 2026 — measured — dated from the channel’s first post
First recorded20 August 2026
Last confirmed live19 November 2026
Measurements held10
Confirmed unchanged1 time, most recently 19 November 2026
On Telegramt.me/zzxbdx

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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.

Previous handles

@zzxbdx was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@zzxbdxj
held 20 August 2026 – 20 August 2026

Growth

4745925320 August 2026 — 47 subscribers20 August 2026 — 58 subscribers27 August 2026 — 147 subscribers3 September 2026 — 160 subscribers11 September 2026 — 163 subscribers30 September 2026 — 219 subscribers9 October 2026 — 222 subscribers17 November 2026 — 431 subscribers17 November 2026 — 431 subscribers19 November 2026 — 459 subscribers20 August 202619 November 2026
10 measurements spanning 91 days, net +412. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Nov 2026, 21:18459+28
17 Nov 2026, 17:22431no change
17 Nov 2026, 16:47431+209
9 Oct 2026, 19:40222+3
30 Sept 2026, 12:56219+56
11 Sept 2026, 21:15163+3
3 Sept 2026, 00:38160+13
27 Aug 2026, 23:12147+89
20 Aug 2026, 23:4458+11
20 Aug 2026, 16:3047first reading

Engagement

28 posts held, back to 20 August 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 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
259.7%
avg views ÷ 459 subscribers
Avg views / post
1,190
16 posts measured
Reaction rate
0.045%
reactions ÷ views · ER floor
Posts in window
19
of 28 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. It is computed over the 7 of 16 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 November 2026
Posts held28 (20 August 2026 – 17 November 2026)
Views total19,070
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 17: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
48s
Average length
12s

Measured directly from 4 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

4 reactions across 4 posts, in 1 kind.

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

Measured over the 28 most recent posts we hold, published 20 August 2026 to 17 November 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

Telegram’s own ‘edited’ marker: 1 of 19 posts held from the last 30 days (5.26%) 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).

31 Oct 2026, 05:03 UTC≈1,140 views1 reactionsread 17 November 2026
Forwarded from @zzsf121

郑州师范学院修车群专属报告 【妹子花名】:涵涵 【验证留名】:狮子座 【人照得分】: 9 【颜值得分】: 9 【身材得分】: 9 【服务得分】: 9 【态度得分】: 10 【环境得分】: 9 【综合得分】: 9.17 【验证时间】:2026-10-30 【过程描述】:涵涵人照没有差别,真人更加的自然活泼可爱,整体随和大方灵动,又有单纯可爱气质,热情有情商。和老师躺在柔软的大床上,双手抚摸光滑温热的肌肤。老师体质敏感 全身颤抖,口活很好,戴套再也忍不住,缓缓进入,终于,在一阵猛烈的冲击后,同时到达快乐的顶点。开6的性价比很高,可以闭眼直接去,老师的人照一致。很嫩,身材很好 很值。

❤1

29 Oct 2026, 11:42 UTC≈1,200 viewsread 17 November 2026

涵涵妹妹很年轻的,也很好看,画的淡妆,和视频基本基本一致,身材凹凸有致,皮肤很白很光滑,有陪浴,培育时重点部位会清洗的很干净,在床上时妹妹很听话,各种姿势都很配合,逼紧,水多,抽插特别爽,没一会就秒了!老师刚来就想出击来着,一直挺忙的没时间,这次时间合适顺利相约,整体体验下来还是很好的妹妹,性格好,乖巧可爱,有机会还会再约涵涵妹妹,十分推荐,颜值高 嫩 确实是嫩!

28 Oct 2026, 08:44 UTC≈1,260 views0 reactionsread 17 November 2026

【出击日期】: 10.28 【验证留名】:YX 【老师昵称】: 涵涵 【联系方式】: @zzxiaobudin 【人照评分】:9 【服务评分】:9 【总体评分】:9 【服务过程】: 真人是非常可爱的嫩妹,白白嫩嫩的,人照一致。进门先来了一个拥抱,很有女友感,然后帮洗漱,脱了衣服身材一览无余、紧致细腻,让人忍不住上手去摸。 到了床上超级反差,先是趴在胸口,然后亲上面,迷人的秀发撩的人心荡漾,然后滑下去口,看着可可爱爱,实际色色的,然后女上,小小年纪女上还挺不错,我不服输,翻身压在身下冲刺,她双腿紧紧夹住我,咬住被子,更加诱人,然后从后面,摸着翘臀 冲刺,回味无穷,嫩妹 不要错过。

28 Oct 2026, 08:06 UTC≈1,190 views1 reactionsread 17 November 2026
Forwarded from @GLL_A6Photo

【时间】:2026-10-28 【老师】:涵涵 【留名】:清风 【人照】:9 【颜值】:9 【身材】:9.3 【服务】:9.3 【态度】:10 【环境】:9 【综合】:9.27 【过程】:见面涵涵很温柔,开朗大方,会主动聊天,也很热情,,长的也好看,身材很好,穿的特别有感觉,本人比照片好看 床上配合也很好,服务也做的细致,不催,小舌头柔柔软软的在你身上亲热,好舒服,特别有感觉,口的时候更刺激,时而还用舌头勾引弟弟,时而还用眼神勾引我,勾引的我内心火热热的,简直受不了,直接开炮,声音也好听,完全就是嫩妹的叫床声,后入式很爽,逼又滑又嫩又紧,大长腿,腿很光滑,身材管理到位,屁股肉肉的,身材的视觉很棒,最后疯狂抽插十几分钟顺利出水,下次有空老二刷。 车评仅供参考自行辨别!

❤1

26 Oct 2026, 09:12 UTC≈1,290 views1 reactionsread 17 November 2026
Forwarded from @zzsf121

郑州师范学院修车群专属报告 【妹子花名】:涵涵 【验证留名】:Hilary 【人照得分】: 9 【颜值得分】: 9 【身材得分】: 9.5 【服务得分】: 9 【态度得分】: 9.5 【环境得分】: 9 【综合得分】: 9.17 【验证时间】:2026-10-26 【过程描述】:妹妹整体给人的第一印象就是年轻漂亮,长相清秀甜美,属于白幼瘦类型的可爱风格,个人感觉比频道照片好看。五官看起来很精致,眼睛有神,脸型小巧精致,笑起来特别好看,整体形象干净清爽,给人一种自然舒服的感觉。 妹妹的声音好听,气质方面偏乖巧文静,初次接触时稍微有些羞涩 温柔内敛。整体颜值和气质都比较在线,既有清新可爱的外形,又带着一点小女生的拘谨感,让人觉得亲切又耐看。 妹妹服务还不错,配合度高,服务方面刚入行会的不多,整体体验非常不错,喜欢嫩妹的可以闭眼冲…

❤1

26 Oct 2026, 09:12 UTC≈1,270 viewsread 17 November 2026
Forwarded from @zzlfxck

郑州楼凤阁修车群专属报告 【妹子花名】:涵涵 【老师车牌】:{1} 【验证留名】:Tessa Mora 【人照得分】: 9 【颜值得分】: 9 【身材得分】: 9 【服务得分】: 9 【态度得分】: 10 【环境得分】: 9 【综合得分】: 9.17 【验证时间】:2026-10-25 【过程描述】:今日出击涵涵妹子,特别嫩的一个妹子,皮肤真的很好很嫩,人照基本一致,五官底子很好,淡妆特别好看。165的身高,体重100左右,胸很饱满C+差不多,细腰翘臀,笑起来很可爱。小穴紧致多汁。态度非常好,有陪洗、口活还不错、挺有感觉的,刚来不久服务不多,但提出的姿势都能配合去做,很乖巧,很好调教,满足感和成就感油然而生。推荐老司机试驾,多开发几个姿势,喜欢嫩妹的还是值得推荐的!

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

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

“涵涵” (@zzxbdx), 459 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/zzxbdx.

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.