Sticker, posted without a caption
custom 51930346711469551463

Channel
@montanovsskie
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
91subscribers
-21 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002308405488 |
|---|---|
| Type | Channel |
| Username | @montanovsskie |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/montanovsskie |
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 89% 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 |
|---|---|---|
| 9 Oct 2026, 08:56 | 91 | -1 |
| 29 Sept 2026, 01:20 | 92 | -4 |
| 7 Sept 2026, 18:40 | 96 | -2 |
| 30 Aug 2026, 20:16 | 98 | -5 |
| 23 Aug 2026, 22:15 | 103 | -5 |
| 15 Aug 2026, 05:18 | 108 | -4 |
| 9 Aug 2026, 06:32 | 112 | no change |
| 7 Aug 2026, 18:30 | 112 | first reading |
19 posts held, back to 16 March 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 19 posts for this entry, the most recent from 26 April 2026. An engagement rate over an empty window would be a number about nothing.
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.
132 reactions across 14 posts, in 10 distinct kinds. The most used accounts for 27.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5193034671146955146 | 36 | 27.3% | |
| custom 5192784201539155759 | 28 | 21.2% | |
| custom 5348565160741068776 | 16 | 12.1% | |
| custom 5368672715857219496 | 15 | 11.4% | |
| custom 5235691066560107927 | 10 | 7.58% | |
| custom 5373341525696617178 | 9 | 6.82% | |
| custom 5373191373639950968 | 8 | 6.06% | |
| custom 5373220553647757467 | 7 | 5.30% | |
| custom 5345802375783282370 | 2 | 1.52% | |
| custom 5238168652804541077 | 1 | 0.758% |
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 14 of the 19 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 132 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 16 March 2026 to 26 April 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.
Sticker, posted without a caption
custom 51930346711469551463
я ничего не буду удалять, пусть всё это останется воспоминанием❤️
custom 51930346711469551462
всем добрый день, я владелец монтановских решил на данное время закрыть кф. я об этом решений думал уже как месяц но не решался так как я привык и привязался к этому кф и к его участникам. за эти три меясца мы поведали немногое и я если честно сказать и судить по моим старым кф долго держимся. осталось очень много воспоминание и я очень рад что открыл в январе этот кф, мне это решение удается очень сложно если честно…
custom 51930346711469551464custom 52356910665601079271
Sticker, posted without a caption
custom 51930346711469551462
Нам уже 3 месяца💕. Я даже не заметил как быстро прошло время с января. За эти 3 месяца у нас было много чего, мы были на грани закрытий, администрация множество раз менялось. Но, в конце концов мы всё еще здесь и держимся вместе с вами. Владелец хочет отблогодарить каждого из вас, участники которые ценят нашу конференцию и поддерживают нас, вам отдельно я блогодарен от чистого сердца, и в том числе хочу выразить тож…
custom 51930346711469551465custom 51927842015391557593custom 52356910665601079273custom 53732205536477574671custom 53733415256966171781
Photo, posted without a caption
custom 51927842015391557595custom 52356910665601079272custom 53731913736399509682custom 53733415256966171781
Уважаемые участники сообщества «Montanovskie», как проходит ваш текущий день? Напоминаем, что вы имеете возможность проголосовать за канал. Это действие будет крайне полезно для нашей конференции. Ссылка: https://t.me/boost/montanovsskie
custom 52356910665601079272custom 53732205536477574672custom 53733415256966171782custom 53485651607410687761custom 53731913736399509681
Sticker, posted without a caption
cr: akosya
custom 51927842015391557592custom 51930346711469551462custom 53485651607410687762custom 52356910665601079271custom 53731913736399509681custom 53733415256966171781
Sticker, posted without a caption
cr: akosya
custom 53733415256966171783custom 53731913736399509682custom 53732205536477574672custom 52356910665601079271custom 53686727158572194961
Sticker, posted without a caption
Showing the 12 most recent of 19 posts we hold for @montanovsskie. 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 9 October 2026 — this entry's latest reading, not the date you are reading this.
“закрыто.” (@montanovsskie), 91 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/montanovsskie.
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.