Parenting & family — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 the other topics.
Growth
11 measurements spanning 82 days, net +11. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 589–606 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
29 Oct 2026, 00:46
604
+2
22 Oct 2026, 16:18
602
+1
15 Oct 2026, 12:06
601
+3
9 Oct 2026, 06:56
598
-1
28 Sept 2026, 10:00
599
-2
15 Sept 2026, 13:58
601
+7
30 Aug 2026, 17:09
594
+2
22 Aug 2026, 22:04
592
+1
15 Aug 2026, 19:26
591
-2
8 Aug 2026, 03:17
593
no change
7 Aug 2026, 17:17
593
first reading
Engagement
3 posts held, back to 4 August 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 3 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
95 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 84.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5406850667266455276
80
84.2%
custom 5267302902031987501
8
8.42%
custom 5406650521790461303
7
7.37%
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 3 of the 3 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 95 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 3 most recent posts we hold, published 4 August 2026 to 7 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.
[Весь вечер не могла отправить пост, тг тупил. Поэтому отправляю сейчас, про наши вчерашние приключения))]
Утром мы отправились в Заречный!
Невероятно красивое место 💔
Сосны, вода, тишина, то что доктор прописал.
Вообще мы ехали кататься на сапе, но был очень сильный ветер и я не рискнула. Погрустила, но зато прогулялась в одиночестве)
Фотографий особо нет, потому что я гуляла без телефона. Но там невероятно. Там …
Всем доброго вечера 🩷
Каждый день я ставлю себе цель написать пост, и каждый день я буквально борюсь с собой за каждое слово.
Вчера у нашего Федюши были именины 🤰 слава Богу мы попали в храм. После храма в мы планировали пойти в кафе с детской комнатой, но, когда мы туда пришли, выяснилось, что кухня не работает. Я конечно ужасно расстроилась, потому что пришлось уходить и думать куда пойти. Утро было спасено двумя…
А ещё сегодня успела в городе и в парикмахерскую сходить, по делам сбегать. Даже на кусочек вебинара по учебе попала. А вечером устроили у себя трудовой дет сад 😉
Вообщем бодренько. С таким количеством детей никакие лишние мысли в голову не лезут 😂 вообще ничего не лезет.
Вдохновляюсь!
#отпускныезаметки26
Showing the 3 most recent of 3 posts we hold for @ne_blog_matuhki. 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.
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 29 October 2026 — this
entry's latest reading, not the date you are reading this.
“Не блог матушки ✨” (@ne_blog_matuhki), 604 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/ne_blog_matuhki.
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.
