6 Aug 2026, 13:44 UTC517 viewsread 8 August 2026
Photo
熟客+1 隱藏版無套正妹~ 有興趣的可以私密我~ 北部：10張小朋友 160.c.45.21歲 活潑的女生 長得滿漂亮的說 #學生妹 #無套妹 #臺北找小姐 #約妹售後 💚賴：2024814 💚備用賴ty8908 💚或者tg：@t48tw 💚Gleezy：tw2025888
Channel
客評分享 紅牌推薦Gleezy：tw2025888
@tghp5
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
511subscribers
+44 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002441000532 |
|---|---|
| Type | Channel |
| Username | @tghp5 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 2 times, most recently 3 October 2026 |
| On Telegram | t.me/tghp5 |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 |
|---|---|---|
| 18 Sept 2026, 16:17 | 511 | +13 |
| 10 Sept 2026, 21:58 | 498 | +3 |
| 1 Sept 2026, 04:26 | 495 | +11 |
| 24 Aug 2026, 04:36 | 484 | +1 |
| 16 Aug 2026, 03:08 | 483 | +15 |
| 8 Aug 2026, 04:47 | 468 | no change |
| 8 Aug 2026, 00:53 | 468 | +1 |
| 7 Aug 2026, 18:17 | 467 | first reading |
Engagement
6 posts held, back to 20 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 6 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
5 Aug 2026, 14:23 UTC584 viewsread 8 August 2026
Photo
解鎖新妹 vip大大 已試車 原價一節6w vip兩節7w 3+1可更優惠~ 第一次下海兼職 隱藏版 美女校花 有興趣的 顔值控的 包滿意 滿分10分已經打滿分 身材資料160.B.45.20歲 漂亮 可愛的女生~ 皮膚很好哦~ 需要提前2天預約~ 💚賴：2024814 💚備用賴ty8908 💚或者tg：@t48tw 💚Gleezy：tw2025888 #臺北找小姐 #高檔正妹 #美女校花 #第一次下海兼職 #學生妹 #清純蘿莉控 #約妹售後 #真實客評 #vip獨家分享~
3 Aug 2026, 08:13 UTC36 viewsread 8 August 2026
Forwarded from @sty968Photo
謝謝vip大大捧場~ 有喜歡的可直接找我預約哦~ 隱藏版正妹~ 露露160.c.48.30【極品秘書兼職】 10k試車價8k
30 Jul 2026, 17:32 UTC849 viewsread 8 August 2026
Photo
謝謝大哥的信任 今天剛加進來就找我約妹捧場~ 問了在哪裏看見我 結果是在tg頻道加到我的賴 可能已經有觀察我一段時間了吧~ 直接讓我幫忙安排隱藏版正妹~ 約的直接給10分 相信我的人 當然不會讓你失望哦~ 還有別的潛水的哥哥 要來捧場一下嗎~ 小尋營業時間13:00到03:00 💚賴：2024814 💚備用賴ty8908 💚或者tg：@t48tw 💚Gleezy：tw2025888
30 Jul 2026, 17:09 UTC713 viewsread 8 August 2026
Photo
感恩熟客大大捧場 有的時候小尋 比較忙哦 有的約的也不錯 也不是每個都會發 有的特別介意隱私的 當然也不會發 售後皆為客人同意在發~ 謝謝每個捧場過小尋的恩客~ 💚賴：2024814 💚備用賴ty8908 💚或者tg：@t48tw 💚Gleezy：tw2025888
20 Jul 2026, 10:17 UTC966 viewsread 8 August 2026
Photo
真的還蠻感動的 雖然久久約一次 雖然工作有的時候真的很忙 很累 但是還是願意花時間 來捧場 謝謝每一次信任~ 感謝熟客大哥~ 專門從臺南包車到高雄約想要的女生~😘 💚賴：2024814 💚備用賴ty8908 💚或者tg：@t48tw 💚Gleezy：tw2025888
Showing the 6 most recent of 6 posts we hold for @tghp5. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“客評分享 紅牌推薦Gleezy：tw2025888” (@tghp5), 511 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/tghp5.
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.