Telegram RegisterThe public register of Telegram
Telegram profile photo for Book Guardian

Channel

Book Guardian

@book_guardian

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

7,289subscribers

+15 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001540017817
TypeChannel
Username@book_guardian
DescriptionКнижные чехлы и аксессуары для книг Для заказа https://bookguardian.ru/ Max https://max.ru/join/_8Nk7extGQzMOG3Yy2HhHc_OmhVEKR2k-vRTjBYXq4Y VK https://vk.ru/bguardian Мы: Наталья @bookguardian Давид @ChefChalios Пишите нам по любым вопросам.
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/book_guardian

Topic

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

6,9997,2897,1446 August 2026 — 7,274 subscribers6 August 2026 — 7,274 subscribers9 August 2026 — 7,269 subscribers12 August 2026 — 7,255 subscribers15 August 2026 — 7,246 subscribers18 August 2026 — 7,236 subscribers22 August 2026 — 7,216 subscribers25 August 2026 — 7,202 subscribers28 August 2026 — 7,184 subscribers31 August 2026 — 7,178 subscribers3 September 2026 — 7,167 subscribers8 September 2026 — 7,156 subscribers13 September 2026 — 7,150 subscribers16 September 2026 — 7,123 subscribers2 October 2026 — 7,086 subscribers9 October 2026 — 7,073 subscribers14 October 2026 — 7,070 subscribers16 October 2026 — 7,065 subscribers19 October 2026 — 7,047 subscribers22 October 2026 — 7,066 subscribers26 October 2026 — 7,055 subscribers29 October 2026 — 7,043 subscribers1 November 2026 — 7,032 subscribers4 November 2026 — 7,017 subscribers7 November 2026 — 7,011 subscribers11 November 2026 — 6,999 subscribers16 November 2026 — 7,289 subscribers6 August 202616 November 2026
27 measurements spanning 102 days, net +15. 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 6,956–7,333 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
16 Nov 2026, 12:407,289+290
11 Nov 2026, 10:066,999-12
7 Nov 2026, 13:067,011-6
4 Nov 2026, 09:197,017-15
1 Nov 2026, 06:277,032-11
29 Oct 2026, 03:297,043-12
26 Oct 2026, 01:407,055-11
22 Oct 2026, 22:167,066+19
19 Oct 2026, 21:287,047-18
16 Oct 2026, 20:097,065-5
14 Oct 2026, 01:597,070-3
9 Oct 2026, 04:377,073-13
2 Oct 2026, 11:197,086-37
16 Sept 2026, 20:417,123-27
13 Sept 2026, 04:167,150-6
8 Sept 2026, 21:587,156-11
3 Sept 2026, 20:417,167-11
31 Aug 2026, 07:237,178-6
28 Aug 2026, 13:247,184-18
25 Aug 2026, 04:597,202first reading

Engagement

69 posts held, back to 30 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 35 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
17.9%
avg views ÷ 7,289 subscribers
Avg views / post
1,300
37 posts measured
Reaction rate
3.21%
reactions ÷ views · ER floor
Posts in window
37
of 69 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 15 November 2026
Posts held69 (30 July 2026 – 15 November 2026)
Views total48,161
Reactions total1,547
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 18:26 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈2,580
Videos
≈315
Links
≈1,070

Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
3m 52s
Average length
21s

Measured directly from 11 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.

Reaction mix

2,661 reactions across 67 posts, in 35 distinct kinds. The most used accounts for 67.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1,80567.8%
🔥34212.9%
👍722.71%
👎682.56%
❤‍🔥411.54%
👀411.54%
🥰301.13%
😨281.05%
🤯260.977%
😍250.939%
💔210.789%
🤩180.676%
🐳160.601%
🎃150.564%
💋140.526%
🥱130.489%
💯110.413%
🤝110.413%
🎉90.338%
🤡80.301%
15 further kinds471.77%

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 69 of the 69 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 2,709 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 69 most recent posts we hold, published 30 July 2026 to 15 November 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.

Recent posts

Telegram’s own ‘edited’ marker: 4 of 37 posts held from the last 30 days (10.8%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Nov 2026, 17:04 UTC788 views51 reactionsread 16 November 2026
Photo

Зимний книжный! У нас есть всего 3 чехла размера мини:)

❤41💋10

15 Nov 2026, 10:18 UTC876 views28 reactionsread 16 November 2026
Photo

Октябрьские предзаказы разосланы⚡️ Проверяйте треки. Если что то не отправилось - сообщите пожалуйста @bookguardian ❗️Не путайте с предзаказами КШИР - они еще шьются

❤20❤‍🔥8

13 Nov 2026, 17:42 UTC≈1,090 views23 reactionsread 16 November 2026

Кидаем классные референсы по Анастасии в комментариях:) Мы начинаем готовиться к созданию арта!

❤23

13 Nov 2026, 12:00 UTC≈1,270 views141 reactionsread 16 November 2026
Photo

😱 Представьте: внезапно ваши любимые книжные герои-детективы становятся…животными Это не сон и не фантазия, а уютный цикл романов, где главные герои — звери, которые живут и разговаривают как люди. Книги из этой серии и атмосферный чехол мы разыгрываем вместе с магазином Book Guardian! 🥰 Каждый победитель получит чехол для книг и 4 книги цикла «Тайны тенистой лощины»: • Зверские убийства в Тенистой Лощине • Забыты…

❤83🔥29👍18🥰5🎉4❤‍🔥2

13 Nov 2026, 11:41 UTC≈1,210 views34 reactionsread 16 November 2026
Photo

Не расходимся! У нас предзаказ до понедельника! 🔘Отправляем в Беларусь 🔘Можно оплатить частями 🔘Чехлы скоро появятся в наличии!

❤34

12 Nov 2026, 17:46 UTC≈1,060 views49 reactionsread 16 November 2026
Photo

😲 ШОК! Теперь можно заказывать в Беларусь! Оформляется как обычный заказ/предзаказ на сайте

❤41😍8

12 Nov 2026, 06:56 UTC≈1,070 views53 reactionsread 16 November 2026
Photo

Октябрьские предзаказы отправлены на 70% В выходные отправлю остальное) Там обложки соответственно 😘

❤53

11 Nov 2026, 09:12 UTC≈1,050 views40 reactionsread 16 November 2026
Video message

Video message, posted without a caption

❤30😍9❤‍🔥1

11 Nov 2026, 07:54 UTC≈1,080 views30 reactionsread 16 November 2026
Photo

Обещала показать результаты ☝️ А пока ждем предзаказ на Анастасию, можно полюбоваться Красавицей и Чудовищем

❤25💔3🥰2

10 Nov 2026, 14:32 UTC≈1,190 views36 reactionsread 16 November 2026

Posted without readable text

❤‍🔥29❤7

10 Nov 2026, 06:37 UTC≈1,320 views20 reactionsread 16 November 2026
Photo

🧑‍🔬Тестируем новые методы оплаты! Оплата прямо тут по ссылке. 🔥Важная особенность - доставка включена в стоимость! Ради теста стоимость выходит супер-выгодной. 🔜ВАЖНО После оплаты нужно написать мне @bookguardian и отправить адрес доставки СДЕК Вот доступный для этого метода ассортимент: "Грустная Сирин" Размер One size 800 рублей включая доставку Размер внутреннего кармана One size: 240 ×170 Грустная Сирин Cali…

❤17🥰3

Showing the 12 most recent of 69 posts we hold for @book_guardian. 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.

Forward network

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.

Mentions

Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“Book Guardian” (@book_guardian), 7,289 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/book_guardian.

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.