Channel
@mks11s_blog
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
122subscribers
+3 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001727776545 |
|---|---|
| Type | Channel |
| Username | @mks11s_blog |
| Created | Between 1 December 2021 and 30 April 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 | 4 |
| Confirmed unchanged | 4 times, most recently 12 October 2026 |
| On Telegram | t.me/mks11s_blog |
Marketing & affiliate — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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 |
|---|---|---|
| 10 Sept 2026, 04:39 | 122 | +1 |
| 24 Aug 2026, 22:43 | 121 | +2 |
| 9 Aug 2026, 04:30 | 119 | no change |
| 8 Aug 2026, 13:00 | 119 | first reading |
8 posts held, back to 27 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 8 posts for this entry, the most recent from 8 August 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.
70 reactions across 7 posts, in 6 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5202182504810820638 | 28 | 40.0% | |
| custom 5273779734189204859 | 19 | 27.1% | |
| custom 5341782406653302974 | 10 | 14.3% | |
| custom 5379642835425325877 | 8 | 11.4% | |
| custom 5249498372804458070 | 4 | 5.71% | |
| custom 5273741337181579492 | 1 | 1.43% |
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 7 of the 8 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 70 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 27 July 2026 to 8 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 52494983728044580704custom 52737797341892048594custom 52021825048108206381
36:25 минут удовольствия Села смотреть видео, где бренд дизайнер объясняет свою концепцию нашего будущего брендинга для ТФ 😎 Так горжусь, до какого уровня мы доросли… мой шок в шоке, у меня очень мощная команда 💗💗💗 Сейчас еще активно исследуем и внедряем ИИ в работу. Спасибо, что компания дает такие возможности Короче, летим 🚀
custom 52021825048108206388custom 53796428354253258772
Даже на верится 🥹💔 Мы теперь спим на огромной кровати и смотрим на огромном телевизоре любимое шоу 📺 Деталька за деталькой создается уют 🏠🐈👕
custom 52021825048108206388custom 53417824066533029745custom 53796428354253258775custom 52737797341892048592
«Береги платье снову, а честь и ЗДОРОВЬЕ смолоду»! 🩻 Мотайте это на ус, потому что чем ты старше, чем все ярче ощущается, когда ты небрежно относишься к себе, своему организму и здоровью Ко мне вот в 26 постучались колени 😂 и сказали «Катюша, ты давай там, береги себя». Поэтому ближайшее время меня ждут тейпы, компрессы, всякие физиотерапии Еще сделала чекап по анализам, потому что энергия дает сбой. Вспомнила все…
custom 52021825048108206384custom 52737413371815794921
А Малышка уже посчитала, что это не наша кровать, а ее когтеточка 🙈 Но мы ее переучаем теперь что-то драть, прыгать на стол, вспоминаем снова команды (да-да, она умная как собака, просто хитрожопая и притворяется тупенькой) Очень жду, когда еще купим стол, кресло, чтобы было комфортно работать 👩🏻💻
custom 52737797341892048595custom 52021825048108206382custom 53417824066533029742
Video message, posted without a caption
custom 52737797341892048598
Распаковка кровати?
Пол отмыли 😮💨 Точнее даже больше Олег отмыл, он чудо и бережет мои больные колени А что мы будем делать дальше?)) Ваши предположения 🤭
custom 52021825048108206385custom 53417824066533029743custom 53796428354253258771
Showing the 8 most recent of 8 posts we hold for @mks11s_blog. 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.
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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“Обо всем с mks11s 🪴 маркетинг, life, соционика” (@mks11s_blog), 122 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/mks11s_blog.
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.