#bia叽兔(#软甜糯米糍 #awdydbb1 #小晚酱) 83V+44sV+34P 已补↓ 露脸 https://t.me/c/3897645902/8691 cos JK lo https://t.me/c/3897645902/8702 粉嫩嫩 https://t.me/c/3897645902/8740 OL 情趣 裸 https://t.me/c/3897645902/8781 短片 https://t.me/c/3897645902/8817
❤9👍4

Channel
@aikan_z7z8
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
19,391subscribers
+14,190 since we began measuring on 27 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003478671293 |
|---|---|
| Type | Channel |
| Username | @aikan_z7z8 |
| Description | 放一些非cos向非flj的片子,还有我本人的碎碎念啥的 |
| Created | Between 1 November 2025 and 30 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 September 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 31 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/aikan_z7z8 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 12 October 2026 and assigned it the closest of 31 fixed categories, at 93% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 13:47 | 19,391 | +363 |
| 14 Nov 2026, 10:49 | 19,028 | +409 |
| 11 Nov 2026, 15:46 | 18,619 | +278 |
| 9 Nov 2026, 18:56 | 18,341 | +278 |
| 8 Nov 2026, 10:50 | 18,063 | +268 |
| 7 Nov 2026, 03:30 | 17,795 | +219 |
| 6 Nov 2026, 00:46 | 17,576 | +152 |
| 5 Nov 2026, 03:06 | 17,424 | +145 |
| 4 Nov 2026, 04:18 | 17,279 | +140 |
| 3 Nov 2026, 02:08 | 17,139 | +179 |
| 1 Nov 2026, 23:06 | 16,960 | +334 |
| 1 Nov 2026, 00:00 | 16,626 | +404 |
| 30 Oct 2026, 22:06 | 16,222 | +396 |
| 29 Oct 2026, 20:29 | 15,826 | +203 |
| 28 Oct 2026, 18:09 | 15,623 | +185 |
| 27 Oct 2026, 18:48 | 15,438 | +307 |
| 26 Oct 2026, 16:18 | 15,131 | +303 |
| 25 Oct 2026, 16:15 | 14,828 | +348 |
| 24 Oct 2026, 17:56 | 14,480 | +571 |
| 23 Oct 2026, 14:31 | 13,909 | first reading |
28 posts held, back to 17 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 33 pages of Telegram’s post history, 20 posts per page.
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 18 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 28 (17 August 2026 – 14 November 2026) |
| Views total | 151,970 |
| Reactions total | 128 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 18 Nov 2026, 06: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.
Lifetime counters from Telegram’s own channel header, read 18 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video 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.
158 reactions across 24 posts, in 3 distinct kinds. The most used accounts for 82.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 130 | 82.3% | |
| 👍 | 24 | 15.2% | |
| 😁 | 4 | 2.53% |
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 24 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 158 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 17 August 2026 to 14 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.
Telegram’s own ‘edited’ marker: 4 of 20 posts held from the last 30 days (20.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).
#bia叽兔(#软甜糯米糍 #awdydbb1 #小晚酱) 83V+44sV+34P 已补↓ 露脸 https://t.me/c/3897645902/8691 cos JK lo https://t.me/c/3897645902/8702 粉嫩嫩 https://t.me/c/3897645902/8740 OL 情趣 裸 https://t.me/c/3897645902/8781 短片 https://t.me/c/3897645902/8817
❤9👍4
#芝士猫 7V 已补↓ https://t.me/c/3897645902/8669
❤2👍1
#Dirtyecho8 #饱饱 #睡觉的美少女 正片 xp 扩肛 肛喷 烂皮炎 屁穴开发 重口 评论区查看详细
❤11
#Dirtyecho8 #饱饱 #睡觉的美少女 X作品 xp 扩肛 肛喷 烂皮炎 屁穴开发 重口 评论区查看详细
❤5
#小希神 7V 已补↓ https://t.me/c/3897645902/7497
❤8👍3
#菜菜萝莉 #🐰Zoey💌 (#caiwenjiji) #小黄帝Zoey #小佐 #Zoey #Zoey_LuckyBabe 压缩包里会多点短片和大部分图集
❤4
#菜菜萝莉 #🐰Zoey💌 (#caiwenjiji) #小黄帝Zoey #小佐 #Zoey #Zoey_LuckyBabe #真嗣 #zhensi0106 #碇真嗣 #zhansi0106 #真嗣 群友投稿 12V 其余的挺好搜 不搬了 已补↓ https://t.me/c/3897645902/7321
❤6
#菜菜萝莉 #🐰Zoey💌 (#caiwenjiji) #小黄帝Zoey #小佐 #Zoey #Zoey_LuckyBabe #真嗣 #zhensi0106 #碇真嗣 #zhansi0106 #菜菜萝莉 常服 19V+20sV 已补↓ https://t.me/c/3897645902/7251
❤8
#菜菜萝莉 #🐰Zoey💌 (#caiwenjiji) #小黄帝Zoey #小佐 #Zoey #Zoey_LuckyBabe #真嗣 #zhensi0106 #碇真嗣 #zhansi0106 #菜菜萝莉 COS 5V+17sV 已补↓ https://t.me/c/3897645902/7214
❤3
#星十三 #三月 (#miao1676) #五月 (#wuyuetu1618) #珊迪和派大星 (#theebrat3) #咩咩Tu_uu (#verymei55) #珊迪(#muhamma64296349) #泡泡珊迪星(#WuYueTu1618) #一颗芝士星(#robanso1982) #一颗黄油星 已补↓ #珊迪 #一颗芝士星 16期27V https://t.me/c/3897645902/7120 后续更新2期 放评论区
❤5👍1
#星十三 #三月 (#miao1676) #五月 (#wuyuetu1618) #珊迪和派大星 (#theebrat3) #咩咩Tu_uu (#verymei55) #珊迪(#muhamma64296349) #泡泡珊迪星(#WuYueTu1618) #一颗芝士星(#robanso1982) #一颗黄油星 已补↓ #珊迪 16期33V https://t.me/c/3897645902/7080
#星十三 #三月 (#miao1676) #五月 (#wuyuetu1618) #珊迪和派大星 (#theebrat3) #咩咩Tu_uu (#verymei55) #珊迪(#muhamma64296349) #泡泡珊迪星(#WuYueTu1618) #一颗黄油星 #一颗芝士星(#robanso1982) 已补↓ #珊迪和派大星 7期14V https://t.me/c/3897645902/7050 #咩咩Tu_uu 3期4V https://t.me/c/3897645902/7068
Showing the 12 most recent of 28 posts we hold for @aikan_z7z8. 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.
@aikan_z7z8 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 1 post on @aikan_z7z8 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“顺意の古玩城|少萝收藏” (@aikan_z7z8), 19,391 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/aikan_z7z8.
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.