Channel
Мука О’ника
@mukaonika
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,933subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001624604441 |
|---|---|
| Type | Channel |
| Username | @mukaonika |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/mukaonika |
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 15 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 07:41 | 2,933 | +3 |
| 14 Sept 2026, 22:41 | 2,930 | +1 |
| 12 Sept 2026, 00:29 | 2,929 | no change |
| 11 Sept 2026, 05:58 | 2,929 | -2 |
| 6 Sept 2026, 03:01 | 2,931 | +2 |
| 30 Aug 2026, 04:13 | 2,929 | -2 |
| 24 Aug 2026, 02:16 | 2,931 | -5 |
| 17 Aug 2026, 09:54 | 2,936 | -1 |
| 13 Aug 2026, 18:17 | 2,937 | +4 |
| 10 Aug 2026, 23:47 | 2,933 | -1 |
| 7 Aug 2026, 12:59 | 2,934 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@hleb_na_zakvaske · 22,844
Telegram ranks this channel #14 of 74 here — alongside 73 others — read 19 September 2026
@drbakers · 29,980
Telegram ranks this channel #19 of 83 here — alongside 82 others — read 7 September 2026
@kucheryavaya_sveta · 22,097
Telegram ranks this channel #21 of 78 here — alongside 77 others — read 21 September 2026
@shkolahleba · 27,537
Telegram ranks this channel #27 of 81 here — alongside 80 others — read 10 September 2026
@bankpovarov · 51,028
Telegram ranks this channel #30 of 81 here — alongside 80 others — read 25 August 2026
@Dasha_Chernenko · 92,093
Telegram ranks this channel #35 of 90 here — alongside 89 others — read 17 August 2026
@academy_resource · 26,455
Telegram ranks this channel #78 of 86 here — alongside 85 others — read 12 September 2026
@zhabcka_food · 25,964
Telegram ranks this channel #86 of 89 here — alongside 88 others — read 13 September 2026
This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Мука О’ника” (@mukaonika), 2,933 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/mukaonika.
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.