Channel
@VIP_890
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
18subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001815915933 |
|---|---|
| Type | Channel |
| Username | @VIP_890 |
| Created | 12 February 2023 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 7 October 2026 |
| On Telegram | t.me/VIP_890 |
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 78% 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 |
|---|---|---|
| 27 Sept 2026, 04:40 | 18 | -1 |
| 14 Sept 2026, 03:36 | 19 | -1 |
| 30 Aug 2026, 09:06 | 20 | -1 |
| 11 Aug 2026, 14:02 | 21 | no change |
| 7 Aug 2026, 09:19 | 21 | first reading |
8 posts held, back to 12 February 2023 — 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 8 posts for this entry, the most recent from 3 July 2026. An engagement rate over an empty window would be a number about nothing.
https://fragment.com/username/vip_890 https://fragment.com/username/vip_950 https://fragment.com/username/vip_822 https://fragment.com/username/vip_922 https://fragment.com/username/o777777o https://fragment.com/username/v111111v https://fragment.com/username/u111111u https://fragment.com/username/c999999c
@D8888Y https://fragment.com/username/D8888Y
❌ 1 hours left until the end of the auction https://fragment.com/username/x00000x
1️⃣0️⃣💎 https://fragment.com/username/c77777c
1️⃣0️⃣💎 https://fragment.com/username/r11111r
1️⃣0️⃣💎 https://fragment.com/username/a66666a
1️⃣0️⃣💎 https://fragment.com/username/o777777o
Channel created
Showing the 8 most recent of 8 posts we hold for @VIP_890. 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 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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“User name” (@VIP_890), 18 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/VIP_890.
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.