Telegram RegisterThe public register of Telegram
Telegram profile photo for H-TST清吟小班

Channel

H-TST清吟小班

@HH33852

On this record: Growth · Engagement · Posts · Citations · Cite this entry

458subscribers

+18 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003900414017
TypeChannel
Username@HH33852
CreatedBetween 1 April 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/HH33852

Growth

4404584496 August 2026 — 440 subscribers6 August 2026 — 440 subscribers6 August 2026 — 441 subscribers15 August 2026 — 458 subscribers6 August 202615 August 2026
4 measurements spanning 9 days, net +18. 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 437–461 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 08:15458+17
6 Aug 2026, 23:34441+1
6 Aug 2026, 19:18440no change
6 Aug 2026, 15:02440first reading

Engagement

5 posts held, back to 4 August 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
23.3%
avg views ÷ 458 subscribers
Avg views / post
107
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
5
of 5 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 5 August 2026
Posts held5 (4 August 20265 August 2026)
Views total533
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 19:18 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.

Recent posts

5 Aug 2026, 04:55 UTC97 viewsread 6 August 2026
Photo

編號:T 1639 166cm D cup 💰1600 (1q-45🕑)(包酒店房) 服務 :大車 69 環保吹 波推臀推 水蕭 前後陪沖涼 第一次來香港,新鮮面孔 长腿有學生制服高跟鞋 絲襪 有学生服 ,嫩口,短期兼职 ,超紧如处女 班長客服:@HH55432

5 Aug 2026, 04:54 UTC98 viewsread 6 August 2026
Photo

編號:T 792 174cm E cup 💰1600 (1q-45🕑)(包酒店房) 服務 :大車 69 環保吹 波推臀推 水蕭 前後陪沖涼 🈶空姐制服,🈶秘书z制服,🈶瑜伽裤,🈶白色丝袜,黑色丝袜,高质 白嫩 靓女 高跟鞋 絲襪 性感制服 学生服 超幼 三点粉嫩 瘦低無腩 一线鲍鱼 初黎港 岩岩开鲍 班長客服:@HH55432

5 Aug 2026, 04:54 UTC86 viewsread 6 August 2026
Photo

編號:T925 168cm E cup 💰1600 (1q-45🕑)(包酒店房) 🈚️🐰➕5 🉑後花園+500 🉑吞精+500 🉑颜射+300 服務:大車坦克车 69 口暴 深喉 環保吹 波推臀推 水蕭 前後細心陪沖涼 AV类型极品服务王/帝王般享受 有高跟鞋 絲襪 性感制服 班長客服:@HH55432

4 Aug 2026, 05:05 UTC128 viewsread 6 August 2026

8🈷️4號尖沙咀TST營業鮮果🏨 學生妹➡️幼幼➡️巨乳➡️大波➡️車模➡️空姐模特➡️ 韓妹⬇️ 新果報導⬇️專線🈚️🐰佳麗🍑 極品幼幼 ⬇️⬇️⬇️⬇️⬇️⬇️ T1549 T1302 T1458 T1450 T1266 T1563 T1369 T1375 T1542 T1200 T1516 T1574 T1577 T1564 T1323 T1583 T1522 T1391 T1259 T1535 T733 T1516 T1593 T1529 T1597 T1372 T1600 T 777 T 1602 T1606 T1607 T1423 T956 T1257 T1533 T1626 T1073 T1274 T1588 T1587 T1614 T1629 T1627 T1632 T1635 T1616 T1302 T1634 T1517 T1431 客服班長預約 @HH55432

4 Aug 2026, 04:35 UTC124 viewsread 6 August 2026
Photo

編號:T1431 165cm C cup 💰1700 (1q-45🕑)(包酒店房) 🈚️🐰➕5 服務 : 大車 69 環保吹 波推 臀推 跪地水蕭 前后细心陪沖涼 主动热情型 没纹身 有jk 有学生服 高跟鞋 性感制服 一級靚鮑魚 少毛 緊如處女/上下粉嫩 甜美可愛 好得意 声音超嗲 /第一次来香港,超可爱呦妹 粉鲍鱼超紧 班長客服:@HH55432

Showing the 5 most recent of 5 posts we hold for @HH33852. 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 — 84,656 of 1,481,243entries 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.

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

“H-TST清吟小班” (@HH33852), 458 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/HH33852.

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.