Channel
@VIP_636547
On this record: Topic Β· Growth Β· Engagement Β· Posts Β· Citations Β· Cite this entry
1,250subscribers
-22 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of 1,000β3,162.
| Telegram ID | -1002941701535 |
|---|---|
| Type | Channel |
| Username | @VIP_636547 |
| Created | 24 August 2025 β measured β dated from the channelβs first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/VIP_636547 |
Other / unclassifiable β 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 00:31 | 1,250 | +4 |
| 2 Nov 2026, 00:29 | 1,246 | +55 |
| 29 Oct 2026, 17:06 | 1,191 | -6 |
| 26 Oct 2026, 09:51 | 1,197 | -5 |
| 23 Oct 2026, 01:56 | 1,202 | -5 |
| 20 Oct 2026, 05:47 | 1,207 | -6 |
| 17 Oct 2026, 02:46 | 1,213 | -2 |
| 14 Oct 2026, 09:37 | 1,215 | -3 |
| 10 Oct 2026, 11:14 | 1,218 | -6 |
| 4 Oct 2026, 17:59 | 1,224 | -4 |
| 24 Sept 2026, 22:39 | 1,228 | -5 |
| 15 Sept 2026, 13:40 | 1,233 | -8 |
| 11 Sept 2026, 18:58 | 1,241 | -6 |
| 7 Sept 2026, 12:55 | 1,247 | -3 |
| 3 Sept 2026, 01:14 | 1,250 | -2 |
| 30 Aug 2026, 16:01 | 1,252 | -2 |
| 27 Aug 2026, 23:55 | 1,254 | -1 |
| 24 Aug 2026, 20:03 | 1,255 | -4 |
| 21 Aug 2026, 09:23 | 1,259 | -1 |
| 18 Aug 2026, 06:03 | 1,260 | first reading |
2 posts held, back to 24 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 2 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Ω Ψ³Ψ§Ψ¨ΩΩ ΨΉΩΩ Ψ±ΩΩ Ψ£Ω Ψ±ΩΩΩ ΨͺΩΩΩΨ¬Ψ±Ψ§Ω Ψ§ΩΩ Ψ³Ψ§Ψ¨ΩΩ ΩΩ Ψ―Ω 5 Ψ³Ψ§ΨΉΨ§Ψͺ Ψ£ΨΉΩΩ ΨͺΨ΅ΩΩΨͺΨ§Ψͺ ΩΩ Ψ§ΩΩΨ§Ψ¦Ψ²
Signed π«π. Ωπ΄πΩππΩΩΩΩΩΩΩΩΩΩΩΩΩΩπππ
Channel created
Showing the 2 most recent of 2 posts we hold for @VIP_636547. 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.
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.
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 5 November 2026 β this entry's latest reading, not the date you are reading this.
βCππππ ππππππππβ (@VIP_636547), 1,250 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/VIP_636547.
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.