Posted without readable text

Channel
精選清純學妹🍵 專區
@heh4570
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,964subscribers
+1,802 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002465223302 |
|---|---|
| Type | Channel |
| Username | @heh4570 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/heh4570 |
Topic
Adult — 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 06:36 | 2,964 | +290 |
| 5 Oct 2026, 15:57 | 2,674 | +147 |
| 28 Sept 2026, 02:36 | 2,527 | +238 |
| 18 Sept 2026, 21:38 | 2,289 | +111 |
| 14 Sept 2026, 17:39 | 2,178 | +3 |
| 10 Sept 2026, 17:37 | 2,175 | +90 |
| 5 Sept 2026, 07:42 | 2,085 | +55 |
| 1 Sept 2026, 11:46 | 2,030 | +61 |
| 29 Aug 2026, 02:09 | 1,969 | +69 |
| 26 Aug 2026, 08:43 | 1,900 | +105 |
| 23 Aug 2026, 06:58 | 1,795 | +201 |
| 19 Aug 2026, 15:57 | 1,594 | +90 |
| 16 Aug 2026, 19:43 | 1,504 | +87 |
| 13 Aug 2026, 04:03 | 1,417 | +124 |
| 10 Aug 2026, 12:11 | 1,293 | +122 |
| 7 Aug 2026, 23:33 | 1,171 | no change |
| 7 Aug 2026, 20:21 | 1,171 | +9 |
| 7 Aug 2026, 16:19 | 1,162 | first reading |
Engagement
11 posts held, back to 30 July 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
10 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 90.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 9 | 90.0% | |
| ❤ | 1 | 10.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 8 of the 11 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 30 July 2026 to 5 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
🇹🇼在校女大生 #嬌小可愛型 棉棉➡️157m・45kg・C奶・19歲 青春肉體就是讚,膚白嫩滑好摸 想玩服裝玩具記得帶,妹妹很願意配合 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 ⭐gleezy預約:Xiaon52 🌐預約點擊: @xxn529 👍官網:www.kz258.com
🥰1
Signed 小暖~🍵 營業中🐰
🇹🇼短兼高中生 #嬌小可愛型 小糕➡️154m・43kg・C奶・19歲 超敏感妹妹,被一碰就全身發熱 小穴出水,深喉、浴室愛愛快來解鎖 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 ⭐gleezy預約:Xiaon52 🌐預約點擊: @xxn529 👍官網:www.kz258.com
🥰2
Signed 小暖~🍵 營業中🐰
🇹🇼短兼高中生 #嬌小可愛型 朵朵➡️160m・45kg・C奶・19歲 清純可愛學生妹妹又很有反差 穴穴超粉 可以配合哥哥變裝和玩具呦 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 ⭐gleezy預約:Xiaon52 🌐預約點擊: @xxn529 👍官網:www.kz258.com
🥰1
Signed 小暖~🍵 營業中🐰
小暖口碑品質茶坊🍵全頻道導航總覽 🇹🇼正妹篩選專區:@xiaon5 新手專區:@yyua520 精選學生專區:@heh4570 成熟女人專區:@yunwei66 北部班表:@beik529 中部班表:@jkmgh63 南部班表:@nankj52 高檔🎀 紅牌vip茶:@vv89ip 🐰小暖の碎碎唸【需審核】 https://t.me/+jUZmR2zqyxU2YjA1 為了讓大家更方便查看不同內容 已整理好各專區頻道 依需求點擊直接加入即可!
Signed 小暖~🍵 營業中🐰
🇹🇼大學顏值校花 #清純係 初雪➡️162m・45kg・C奶・20歲 剛兼職小穴粉嫩緊實 水多又敏感 很會撒嬌 想要被哥哥慢慢帶著玩 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 ⭐gleezy預約:Xiaon52 🌐預約點擊: @xxn529 👍官網:www.kz258.com
Signed 小暖~🍵 營業中🐰
Posted without readable text
❤1
Signed 小暖~🍵 營業中🐰
🇹🇼JK制服學妹 #清純小隻馬 巧巧➡️156m・44kg・C奶・19歲 第一次兼職 很羞澀的可愛學妹 配合度極高哦 乳頭身體都很敏感 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 ⭐gleezy預約:Xiaon52 🌐預約點擊: @xxn529 👍官網:www.kz258.com
🥰2
Signed 小暖~🍵 營業中🐰
🇹🇼小隻馬清純係 #鄰家小妹 甜心➡️158m・45kg・C奶・19歲 皮膚白皙 服務貼心 甜美外型 可以喇舌69 小穴非常緊實多汁 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 ⭐gleezy預約:Xiaon52 🌐預約點擊: @xxn529 👍官網:www.kz258.com
🥰1
Signed 小暖~🍵 營業中🐰
🇹🇼剛成年的幼齒學生妹 心心➡️155m・42kg・B奶・18歲 皮膚白皙水嫩 乳頭很敏感 喜歡跟哥哥玩69 冰火 白虎一線鮑魚 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 ⭐gleezy預約:Xiaon52 🌐預約點擊: @xxn529 👍官網:www.kz258.com
🥰1
Signed 小暖~🍵 營業中🐰
🇹🇼清純學生 #馬尾蘿莉 許糖➡️158m・43kg・C奶・18歲 清純小隻馬學生 床上超黏人 嫩白皮膚 白虎小穴 多汁敏感 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 ⭐gleezy預約:Xiaon52 🌐預約點擊: @xxn529 👍官網:www.kz258.com
🥰1
Signed 小暖~🍵 營業中🐰
Showing the 11 most recent of 11 posts we hold for @heh4570. 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 7 registered channels — 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“精選清純學妹🍵 專區” (@heh4570), 2,964 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/heh4570.
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.