храм рядом с моей работой ночью выглядит ещё красивее
❤15🐳2

Channel
@jpbookshelf
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
245subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002190068110 |
|---|---|
| Type | Channel |
| Username | @jpbookshelf |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 19 November 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 19 November 2026 |
| On Telegram | t.me/jpbookshelf |
Literature — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Nov 2026, 23:20 | 245 | +1 |
| 2 Nov 2026, 18:36 | 244 | -2 |
| 26 Oct 2026, 19:49 | 246 | -1 |
| 20 Oct 2026, 14:48 | 247 | +3 |
| 13 Oct 2026, 04:11 | 244 | +2 |
| 3 Oct 2026, 16:58 | 242 | +4 |
| 9 Sept 2026, 17:19 | 238 | -3 |
| 16 Aug 2026, 19:18 | 241 | -2 |
| 8 Aug 2026, 09:47 | 243 | no change |
| 7 Aug 2026, 18:31 | 243 | first reading |
5 posts held, back to 23 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 5 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
86 reactions across 5 posts, in 8 distinct kinds. The most used accounts for 47.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 41 | 47.7% | |
| 🐳 | 14 | 16.3% | |
| 😢 | 14 | 16.3% | |
| 🙏 | 6 | 6.98% | |
| 😍 | 4 | 4.65% | |
| 🔥 | 3 | 3.49% | |
| 😁 | 2 | 2.33% | |
| 🤣 | 2 | 2.33% |
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 5 of the 5 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 86 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 23 July 2026 to 4 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.
храм рядом с моей работой ночью выглядит ещё красивее
❤15🐳2
прочитанное за июль после начала подработки не успеваю с непривычки читать в обычном количестве, но скоро нагоню уже последний месяц лета начался... (наконец-то, ужасная жара)
🐳2🔥2🤣2😁2
недавно умер писатель, у которого я прочитала больше двадцати произведений жаль, что я не успела попросить его подписать мне какую-нибудь книжку в августе выходит его последняя книжка p.s. маленький стенд в нашей местной библиотеке, посвящённый ему по случаю его смерти спасибо, Хигасино Кэйго, за хорошее начало пути в японской литературе
😢14🙏6🐳2
дни пролетают в магазине, очень весело, но писать особо не о чем теперь моя галерея забита общими фотографиями с ребятами с работы, но выкладывать их лица тут особо не хочется недавно впервые сходила с ними в караоке, а вчера зашли в какой-то ресторан китайской кухни было очень вкусно
❤16🐳6😍4
сегодня после работы сходила на очередной фестиваль, было очень, очень, очень много людей (что как правило неотъемлимая часть праздника) за выброс мусора в специально отведённых на это местах давали милые стикеры
❤10🐳2🔥1
Showing the 5 most recent of 5 posts we hold for @jpbookshelf. 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 19 November 2026 — this entry's latest reading, not the date you are reading this.
“bookshelf (офтоп)” (@jpbookshelf), 245 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/jpbookshelf.
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.