Telegram RegisterThe public register of Telegram
Telegram profile photo for 椰椰🥥的频道

Channel

椰椰🥥的频道

@zwzazff166

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

851subscribers

+41 since we began measuring on 17 November 2026

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

Register entry

Telegram ID-1003085106045
TypeChannel
Username@zwzazff166
Created22 August 2025 — measured — dated from the channel’s first post
First recorded17 November 2026
Last confirmed live20 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 20 November 2026
On Telegramt.me/zwzazff166

Growth

810851830.517 November 2026 — 810 subscribers17 November 2026 — 810 subscribers20 November 2026 — 851 subscribers17 November 202620 November 2026
3 measurements spanning 3 days, net +41. 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 804–857 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Nov 2026, 02:20851+41
17 Nov 2026, 08:22810no change
17 Nov 2026, 07:47810first reading

Engagement

14 posts held, back to 22 August 2025 — 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
77.8%
avg views ÷ 851 subscribers
Avg views / post
662
3 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
3
of 14 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 1 of 3 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 held14 (22 August 2025 – 17 November 2026)
Views total1,985
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 08: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
18s
Average length
6s

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

47 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 80.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3880.9%
👏714.9%
🔥24.26%

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

Measured over the 14 most recent posts we hold, published 22 August 2025 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 3 posts held from the last 30 days (33.3%) 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).

17 Nov 2026, 03:36 UTC278 viewsread 17 November 2026

限时双飞福利来咯🧧 双飞 中途可换人 ❤️ 单次 1500 50分钟 可优惠200 两次 3000 90分钟 可优惠500

15 Nov 2026, 17:03 UTC507 views0 reactionsread 17 November 2026
Photo

已到长春 明天17号🉑🈷️ 开课时间上午10-晚上10点 位置📍朝阳区蔚山路附近 闺蜜花朵🉑双飞 @huaduoyuehui68 约课先看置顶课表~ 联系 @zwzazff1 双向 @shengao166_bot

24 Oct 2026, 00:49 UTC≈1,200 viewsread 17 November 2026

明天撤退了 ,今天可约12点到4点哦❗❗❗

14 Jan 2026, 03:13 UTC≈5,890 views5 reactionsread 17 November 2026

回家啦 年后有机会再见😶‍🌫️

👏5

17 Sept 2025, 02:41 UTC≈7,440 views3 reactionsread 17 November 2026

椰椰 (猫椰椰 9.16)俗话说,美女的朋友大都是美女,椰椰作为知名兼职花朵的闺蜜,自然也成为了我必刷的名单之一。本次短暂回归长春,椰椰竟然正好次日开课,如此美妙的缘分,当然不容放过,果断预约! 椰椰的教室在朝阳,是最方便上楼的公寓之一,开门之后,清新的香气扑面而来,椰椰藏在门后,让我更加按耐不住自己的好奇心。终于揭开她的面纱,完全没有辜负我的期待,椰椰颜值和视频里的那个美人完全一致,皓齿柳眉,眼送秋波,瓜子脸型,樱桃小嘴。而亲眼所见她穿着性感内衣的高挑身材,更是把我馋得暗咽口水。 边聊边更衣,椰椰很是热情,操着一口可爱的南方口音。她个子很高,身材匀称风骚,背对着调试水温的时候,透过紫色轻纱的轮廓让我大饱眼福。出浴,椰椰帮忙擦身,随着身体的接触,有些按耐不住地抱在一起,吻上她饱满的小嘴,甜味占据整个口腔,椰椰在我身上蹭啊蹭,我亲着她的胸,她舔舐我的耳朵,🐔也不自觉地高耸入云。上床体验一把她的手法,口哈时间很长,几乎覆盖全身。…

❤3

25 Aug 2025, 09:19 UTC≈9,630 views6 reactionsread 17 November 2026

给椰椰🥥的车评: 很多人都知道我最爱的是萝莉,确切的说是萝莉身材,我要澄清一下:我喜欢有灵魂的妹子,也就是能提供情绪价值的,不论少女还是少妇,萝莉还是大长腿我都可以喜欢。 最近欣闻花朵带着闺蜜空降长春,出于对花朵的喜爱,我觉得她闺蜜一定不错,毕竟物以类聚人以群分,遂决定找时间去一探究竟。 因为椰椰花朵可以双飞,因此我必须第一时间cj,在熬过了一个周末后,我终于有时间一睹芳容,时间就在今天中午!(可能是椰椰妹子给我硬挤出的时间)见面的第一感觉是个好高,胸好大,腿好长!不得不说,cj过的妹子,很难有哪个像她身材一样棒,尤其是她穿上连体短裙,修长的大腿纤细笔直,我看呆了。椰椰是标准的御姐类型,年纪大概27岁左右的样子,人照9分没啥差别,她一张嘴就是典型的南方味道,一口哥哥让我又酥又麻,进屋后她年面带微笑照顾我坐下,用身体跟我有意无意的摩擦,同时用嗲嗲的声音跟我聊天,我的二弟不知不觉间就已经准备好了。冲洗以后,我看到椰椰在床上摆好了姿势…

❤6

22 Aug 2025, 03:55 UTC≈9,690 views9 reactionsread 17 November 2026

❤️ 本人椰椰❤️闺蜜花朵 可接双飞~配合默契 单次1500~50分钟 两次3000~90分钟 双飞中途可换人❤️ 闺蜜联系方式: @huaduoyuehui68 https://t.me/huaduohy666

❤9

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

“椰椰🥥的频道” (@zwzazff166), 851 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/zwzazff166.

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.