pm @nicovt if keen!
Signed v 🧿

Channel
@phanpysclearance
On this record: Topic · Growth · Engagement · Posts · Cite this entry
187subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002326264883 |
|---|---|
| Type | Channel |
| Username | @phanpysclearance |
| 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 | 8 October 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 3 times, most recently 8 October 2026 |
| On Telegram | t.me/phanpysclearance |
Ecommerce storefront — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 16:17 | 187 | -2 |
| 30 Aug 2026, 04:37 | 189 | -1 |
| 23 Aug 2026, 03:57 | 190 | -1 |
| 16 Aug 2026, 09:08 | 191 | -1 |
| 8 Aug 2026, 12:00 | 192 | no change |
| 7 Aug 2026, 17:30 | 192 | first reading |
12 posts held, back to 17 August 2025 — 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 12 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
pm @nicovt if keen!
Signed v 🧿
FIRST PAY FIRST SERVE BASIS PM @tyluuhh 1st Row --------- Altaria EX 123/124 - $OLD Houndoom EX 153/162 - $OLD M Camerupt EX XY198a -$26 M Lucario EX 55a - $OLD Kyurem SAR 168/086 - $46 Victini AR 097/086 - $17 Starly IR 221/198 - $15 2nd Row -------- Latios AR 070/064 - $15 M Latias EX SR 079/063 - $5 M Latias EX SAR 088/063 - $50 M Camerupt EX SR 077/063 - $2 M Lucario EX SR 078/063 - $12 M Heracross EX SR 093/8…
Signed 🧿
$750 Pm @tyluuhh
Anyone interested ? Pm @tyluuhh
sold
Signed v
glaceon $2 garde claimed machoke $5
Signed v
released $3
Signed v
mailing will be done tmr! if anyb wna add anyt lmk before tmr 8am~
Signed v
$5 comment claim / pm @nicovt
Signed v
$45 comment claim / pm @nicovt
Signed v
$130 comment claim / pm @nicovt
Signed v
mb $10 comment claim / pm @nicovt
Signed v
Showing the 12 most recent of 12 posts we hold for @phanpysclearance. 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“🎈🐘Phanpy’s Clearance🐘🎈” (@phanpysclearance), 187 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/phanpysclearance.
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.