Telegram RegisterThe public register of Telegram
Telegram profile photo for Vradüx | Closed

Channel

Vradüx | Closed

@A97N1

On this record: Topic · Growth · Engagement · What this channel posts · Stars · Posts · Cite this entry

91subscribers

-5 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-1002211829675
TypeChannel
Username@A97N1
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live12 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/A97N1

Topic

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 27 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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

919693.57 August 2026 — 96 subscribers9 August 2026 — 96 subscribers23 August 2026 — 94 subscribers9 September 2026 — 93 subscribers1 October 2026 — 92 subscribers12 October 2026 — 91 subscribers7 August 202612 October 2026
6 measurements spanning 66 days, net -5. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 90–97 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 13:0991-1
1 Oct 2026, 11:0092-1
9 Sept 2026, 21:5793-1
23 Aug 2026, 20:3794-2
9 Aug 2026, 12:1696no change
7 Aug 2026, 14:5896first reading

Engagement

12 posts held, back to 26 January 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 12 posts for this entry, the most recent from 20 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
19s
Average length
5s

Measured directly from 4 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
2
of 12 we hold a reading for · 17%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @A97N1. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 12 most recent posts we hold for this entry, published 26 January 2026 to 20 February 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

20 Feb 2026, 07:35 UTC134 views0 reactions2 Starsread 9 August 2026
Photo

🤩🤩But if I take myself back, you'll lose me and I'll do it.🌟🌟

20 Feb 2026, 07:20 UTC135 views0 reactions2 Starsread 9 August 2026
Photo

🤩Nickname: Gerzet Premium: 🥷🌟📞

28 Jan 2026, 06:15 UTC163 viewsread 9 August 2026
Photo

🤩🤩Детка, мне лучше без тебя, я уезжаю надолго.✅

Showing the 12 most recent of 12 posts we hold for @A97N1. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“Vradüx | Closed” (@A97N1), 91 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/A97N1.

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.