星 探 事 務 所 ✨ pinned a photo

Channel
星 探 事 務 所 ✨
@PTGFSTARUP
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,693subscribers
-37 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 | -1001940101811 |
|---|---|
| Type | Channel |
| Username | @PTGFSTARUP |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/PTGFSTARUP |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Nov 2026, 13:17 | 1,693 | -3 |
| 8 Nov 2026, 14:46 | 1,696 | +2 |
| 5 Nov 2026, 17:45 | 1,694 | -3 |
| 3 Nov 2026, 04:19 | 1,697 | -4 |
| 27 Oct 2026, 21:01 | 1,701 | +4 |
| 25 Oct 2026, 03:17 | 1,697 | -2 |
| 18 Oct 2026, 23:58 | 1,699 | -2 |
| 15 Oct 2026, 15:29 | 1,701 | -3 |
| 12 Oct 2026, 18:27 | 1,704 | -4 |
| 6 Oct 2026, 09:22 | 1,708 | -2 |
| 29 Sept 2026, 04:35 | 1,710 | -4 |
| 19 Sept 2026, 03:00 | 1,714 | -3 |
| 14 Sept 2026, 19:01 | 1,717 | -2 |
| 11 Sept 2026, 12:39 | 1,719 | -5 |
| 7 Sept 2026, 02:57 | 1,724 | +2 |
| 2 Sept 2026, 14:08 | 1,722 | -1 |
| 30 Aug 2026, 18:25 | 1,723 | -1 |
| 20 Aug 2026, 15:03 | 1,724 | -2 |
| 17 Aug 2026, 09:44 | 1,726 | -2 |
| 13 Aug 2026, 12:16 | 1,728 | first reading |
Engagement
6 posts held, back to 7 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 2 pages 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
星探事務所02: GFABLE莊小姐 Age:23歲 Height:166cm Weight:106lbs 👙34B 22 32👙 Miss Lam囡囡分析: 莊小姐最喜歡床上做莊,當然你要令佢進入"想要"既狀態👧🏻佢好鍾意甜言蜜語/Dirty Words On Bed. 整個形象既溫柔又活潑既女友。 Cs Miss Lam💯 @Starupmisslam http://wa.me/+85262734297 聯絡✌🏻
星 探 事 務 所 ✨ pinned a photo
星探事務所03: 高妹子-泳欣 Age:25歲 Height:171cm Weight:114lbs 👙32C 25 32👙 Miss Lam囡囡分析: 賣車Sales高妹泳欣👧🏻賣點正正就係一對雪白既42吋長腿😍我係女仔睇到都覺得正,建議追加Miss Lam提供既緊身摟屌裙同埋高跟鞋💋包你興致勃勃咁後入泳欣妹妹❤️🔥 http://wa.me/+85262734297 聯絡✌🏻 Cs Miss Lam💯 @Misslamhk 高妹子泳欣好評: https://t.me/ptgfstar/543?single
星 探 事 務 所 ✨ pinned a photo
星探事務所04: 短髮妹妹Maxine Age:23歲 Height:164cm Weight:112lbs 👙32B 23 32👙 Miss Lam囡囡分析: 全場暫時唯一真正既短髮妹妹Maxine👧🏻上網睇過啲調查 如果短髮女士進行床上活動有一大好處,BJ/ML既時候可以更清楚見到佢既樣貌神情。呢個特徵正正係Maxine為各位男士效勞或展示既地方❤️💋 Cs Miss Lam💯 @Misslamhk http://wa.me/+85262734297 聯絡✌🏻 Maxine好評: https://t.me/ptgfstar/498?single
Showing the 6 most recent of 6 posts we hold for @PTGFSTARUP. 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
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@PTGFSTARUP named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“星 探 事 務 所 ✨” (@PTGFSTARUP), 1,693 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/PTGFSTARUP.
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.