Зеленоград
custom 521796812023637707430custom 52201665464914596394custom 53525736966680816243

Channel
@muzauthor
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2subscribers
-1,398 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001917357879 |
|---|---|
| Type | Channel |
| Username | @muzauthor |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/muzauthor |
Local community — 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 3 October 2026 and assigned it the closest of 31 fixed categories, at 80% 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 |
|---|---|---|
| 12 Oct 2026, 13:26 | 2 | +1 |
| 2 Oct 2026, 01:56 | 1 | -1,413 |
| 21 Aug 2026, 16:59 | 1,414 | +6 |
| 18 Aug 2026, 09:12 | 1,408 | +2 |
| 15 Aug 2026, 15:42 | 1,406 | +2 |
| 12 Aug 2026, 09:07 | 1,404 | +4 |
| 9 Aug 2026, 08:00 | 1,400 | no change |
| 9 Aug 2026, 07:48 | 1,400 | first reading |
13 posts held, back to 26 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 13 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
597 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 65.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5217968120236377074 | 388 | 65.0% | |
| custom 5352573696668081624 | 116 | 19.4% | |
| custom 5220166546491459639 | 78 | 13.1% | |
| custom 5247213725080890199 | 15 | 2.51% |
Custom emoji. Every row above is a 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 13 of the 13 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 597 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 26 July 2026 to 1 August 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 521796812023637707430custom 52201665464914596394custom 53525736966680816243
Зеленоград
custom 521796812023637707437custom 52201665464914596393custom 53525736966680816243
Зеленоград
custom 521796812023637707441custom 53525736966680816244custom 52201665464914596393
Зеленоград
custom 521796812023637707444custom 52201665464914596398custom 53525736966680816248custom 52472137250808901992
Зеленоград
custom 521796812023637707440custom 52201665464914596398custom 53525736966680816246
Зеленоград
custom 521796812023637707438custom 52201665464914596396custom 53525736966680816246custom 52472137250808901992
Зеленоград
custom 521796812023637707432custom 53525736966680816248custom 52201665464914596394custom 52472137250808901992
Екатеринбург
custom 521796812023637707430custom 52201665464914596397
Екатеринбург
custom 535257369666808162423custom 52179681202363770748custom 52201665464914596397
Екатеринбург
custom 521796812023637707424custom 53525736966680816248custom 52201665464914596395
Екатеринбург
custom 521796812023637707416custom 522016654649145963916custom 53525736966680816247custom 52472137250808901994
Muza & Fox Екатеринбург
custom 535257369666808162437custom 521796812023637707419
Showing the 12 most recent of 13 posts we hold for @muzauthor. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Mussa” (@muzauthor), 2 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/muzauthor.
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.