Personal blog — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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
9 measurements spanning 55 days, net +35. 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 950–996 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
1 Oct 2026, 09:01
991
+3
16 Sept 2026, 10:17
988
+6
9 Sept 2026, 08:58
982
-2
1 Sept 2026, 00:15
984
+3
25 Aug 2026, 01:08
981
+4
16 Aug 2026, 16:54
977
+22
8 Aug 2026, 05:03
955
-1
8 Aug 2026, 00:48
956
no change
7 Aug 2026, 16:47
956
first reading
Engagement
3 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 3 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
62 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 56.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
custom 5440652820095182800
35
56.5%
❤🔥
23
37.1%
💯
2
3.23%
🔥
2
3.23%
Custom emoji. One 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 count beside it is 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 62 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 26 July 2026 to 6 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.
Летние посты пока не пишутся everyday
Но #каждыйденьлета оффлайн обязательно случается, не смотря на рабочие будни и если честно, небольшой завал в проектах (из-за плохо работающего интернета в поездках 😵💫)
Но я 2 недели жила в обнимку с ноутом и мне удалось все нагнать,
И начались стандартные рабочие будни матери 3х детей (хаха!)
А лето
Это же привычка уже
Ее не пропьешь потеряешь
А я всегда так умела
Всегда …
Наконец-то работаю в своем «кабинете»
Стабильный интернет, нужная температура воздуха, свет и тд
Сейчас со мной 2ое детей, Павла уехала с кузиной к бабушке еще на недельку другую
Холодильник пустой
Кафе за углом (спаси Хосподи 🙏)
Если что, я уезжала не в отпуск, просто вывозила детей из города и сама должна была по плану работать над онлайн частью проектов
Но обстановка и родственники внесли коррективы, работат…
Ну и акцентирую внимание на книгах июля
Мало сейчас читаю
Еще про меньше книг хочется делиться в блоге
Но тут какое-то чудо
Обе две
И обе хочется тут «засветить»
Думаю, чем вызывается это желание?
Наверно, когда книга не просто про удовольствие времяпрепровождения, но и про явный след в сознании
Испытываю полное книжное удовлетворение в этом месяц, вот!
#читаю_2026
#летокаждыйдень
❤🔥16🔥2custom 54406528200951828002
Showing the 3 most recent of 3 posts we hold for @booksandhomes. 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 1 October 2026 — this
entry's latest reading, not the date you are reading this.
“Читающий Хоумстейджер 🌿” (@booksandhomes), 991 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/booksandhomes.
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.
