Photo, posted without a caption

Channel
مُذكرة هانسل.
@Viixn
On this record: Topic · Growth · Engagement · Posts · Cite this entry
3,265subscribers
-127 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001451528446 |
|---|---|
| Type | Channel |
| Username | @Viixn |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/Viixn |
Topic
Religion — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 16 Nov 2026, 11:14 | 3,265 | -7 |
| 10 Nov 2026, 22:46 | 3,272 | -6 |
| 7 Nov 2026, 04:09 | 3,278 | -2 |
| 4 Nov 2026, 03:07 | 3,280 | -6 |
| 1 Nov 2026, 05:37 | 3,286 | -2 |
| 28 Oct 2026, 23:01 | 3,288 | -2 |
| 25 Oct 2026, 19:57 | 3,290 | -1 |
| 23 Oct 2026, 00:49 | 3,291 | -3 |
| 20 Oct 2026, 02:01 | 3,294 | -2 |
| 16 Oct 2026, 22:00 | 3,296 | -5 |
| 13 Oct 2026, 18:26 | 3,301 | -7 |
| 7 Oct 2026, 17:14 | 3,308 | -6 |
| 30 Sept 2026, 21:39 | 3,314 | -16 |
| 16 Sept 2026, 03:01 | 3,330 | -5 |
| 12 Sept 2026, 15:15 | 3,335 | -7 |
| 8 Sept 2026, 06:00 | 3,342 | -9 |
| 3 Sept 2026, 08:47 | 3,351 | -2 |
| 31 Aug 2026, 05:13 | 3,353 | -4 |
| 28 Aug 2026, 01:17 | 3,357 | -5 |
| 25 Aug 2026, 02:13 | 3,362 | first reading |
Engagement
20 posts held, back to 19 December 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 3 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 20 posts for this entry, the most recent from 4 October 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
صلاة الوتر 🌿.
Showing the 12 most recent of 20 posts we hold for @Viixn. 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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“مُذكرة هانسل.” (@Viixn), 3,265 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/Viixn.
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.