⭐️⭐️⭐️⭐️⭐️⭐️ ⭐️⭐️⭐️⭐️⭐️⭐️ ⭐️⭐️. 💚. ⭐️⭐️
custom 546530779639004663612custom 53076697362790193078❤7custom 52581166928353242834custom 53390824656569823172

Channel
@hexengasse
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
84subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002068109370 |
|---|---|
| Type | Channel |
| Username | @hexengasse |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 7 October 2026 |
| On Telegram | t.me/hexengasse |
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 97% 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 |
|---|---|---|
| 26 Sept 2026, 21:37 | 84 | +1 |
| 7 Sept 2026, 16:22 | 83 | +2 |
| 9 Aug 2026, 18:32 | 81 | no change |
| 7 Aug 2026, 18:22 | 81 | first reading |
4 posts held, back to 14 July 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 4 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
127 reactions across 4 posts, in 10 distinct kinds. The most used accounts for 33.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5258116692835324283 | 42 | 33.1% | |
| custom 5465307796390046636 | 19 | 15.0% | |
| ❤ | 16 | 12.6% | |
| custom 5244882184904413858 | 14 | 11.0% | |
| custom 5307669736279019307 | 9 | 7.09% | |
| custom 5339082465656982317 | 9 | 7.09% | |
| custom 5361924003680241099 | 8 | 6.30% | |
| custom 5427303000882304349 | 5 | 3.94% | |
| custom 5307534719687094184 | 4 | 3.15% | |
| custom 5447128733129391495 | 1 | 0.787% |
Custom emoji. 9 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 4 of the 4 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 127 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 14 July 2026 to 28 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
⭐️⭐️⭐️⭐️⭐️⭐️ ⭐️⭐️⭐️⭐️⭐️⭐️ ⭐️⭐️. 💚. ⭐️⭐️
custom 546530779639004663612custom 53076697362790193078❤7custom 52581166928353242834custom 53390824656569823172
⭐️⭐️⭐️ ⭐️⭐️⭐️
custom 525811669283532428314custom 52448821849044138588❤6custom 53390824656569823176
🤝🤝 три депутата
custom 525811669283532428312custom 54653077963900466367custom 52448821849044138586custom 53075347196870941842custom 54471287331293914951
⭐️⭐️⭐️ ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ ⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️
custom 525811669283532428312custom 53619240036802410998custom 54273030008823043495❤3custom 53075347196870941842custom 53076697362790193071custom 53390824656569823171
Showing the 4 most recent of 4 posts we hold for @hexengasse. 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“ведьмин переулок🕯” (@hexengasse), 84 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/hexengasse.
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.