Telegram RegisterThe public register of Telegram
Telegram profile photo for Книжная рысь📚🐾

Channel

Книжная рысь📚🐾

@book_channel0

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

36subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002670354377
TypeChannel
Username@book_channel0
CreatedBetween 1 March 2025 and 18 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live13 September 2026
Measurements held4
Confirmed unchanged3 times, most recently 13 September 2026
On Telegramt.me/book_channel0

Growth

3638377 August 2026 — 38 subscribers10 August 2026 — 38 subscribers15 August 2026 — 37 subscribers29 August 2026 — 36 subscribers7 August 202629 August 2026
4 measurements spanning 22 days, net -2. 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 36–38 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 17:0336-1
15 Aug 2026, 02:2837-1
10 Aug 2026, 20:4538no change
7 Aug 2026, 16:2438first reading

Engagement

4 posts held, back to 18 July 2025the 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 4 posts for this entry, the most recent from 4 August 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
20s
Average length
20s

Measured directly from 1 video 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

197 reactions across 4 posts, in 20 distinct kinds. The most used accounts for 12.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53304661943255152062412.2%
custom 5224442667470964960199.64%
custom 5454317937152247563189.14%
custom 5233267742932482852178.63%
custom 5332672016514297320178.63%
custom 5357192933994933405168.12%
custom 5204454405071454176147.11%
custom 5355068836443859374136.60%
custom 5454114703594767939136.60%
custom 520871891245939128684.06%
custom 534390305964059074873.55%
custom 532368029202672883663.05%
custom 538645014384110761463.05%
custom 533266209513984190052.54%
custom 533717220164266465742.03%
custom 525832220272546218031.52%
custom 534179822931281310321.02%
custom 535507550223310294821.02%
custom 535523870669539960321.02%
custom 533249293785289001510.508%

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

Measured over the 4 most recent posts we hold, published 18 July 2025 to 4 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
2
across the posts below
Posts paid on
1
of 4 we hold a reading for · 25%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @book_channel0. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 4 most recent posts we hold for this entry, published 18 July 2025 to 4 August 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

4 Aug 2025, 12:56 UTC156 views34 reactions2 Starsread 10 August 2026
Photo

🍂🍂🍂🍂🍂🍂🍂🍂 Хулиган - Эмилия Грин Ворон - Эмилия Грин Сосед - Рози Данан

custom 535719293399493340512custom 53326720165142973208custom 53236802920267288366custom 52087189124593912862custom 53417982293128131032custom 53552387066953996032custom 52332677429324828521custom 53324929378528900151

28 Jul 2025, 12:51 UTC138 views42 reactionsread 10 August 2026
Forwarded from @tsbrfilmVideo

Пульс — 180, дыхание сбито… Спокойно, это не паническая атака — просто тот самый момент. Вы гадали, спорили, делали фанкасты. И вот — наши главные герои: Полина Туманова — Вероника Журавлёва 🥰 Барс — Даниэль Вегас 🔥 Они оживят эту историю. Разобьют наши (и ваши) сердца. И это только начало: совсем скоро вы узнаете, как стать частью фильма.

custom 533046619432551520613custom 545411470359476793910custom 53326720165142973209custom 53571929339949334054custom 52087189124593912863custom 53550755022331029482custom 52332677429324828521

20 Jul 2025, 10:25 UTC134 views57 reactionsread 10 August 2026
Photo

Подборка артов книги "Запрети любить"

custom 545431793715224756318custom 523326774293248285215custom 535506883644385937411custom 53371722016426646574custom 52087189124593912863custom 52583222027254621803custom 54541147035947679393

18 Jul 2025, 18:45 UTC116 views64 reactionsread 10 August 2026
Photo

——ˋˏЭстетика книгиˎˊ—— Поклонник - Анна Джейн

custom 522444266747096496019custom 520445440507145417614custom 533046619432551520611custom 53439030596405907487custom 53864501438411076146custom 53326620951398419005custom 53550688364438593742

Showing the 4 most recent of 4 posts we hold for @book_channel0. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

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

“Книжная рысь📚🐾” (@book_channel0), 36 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/book_channel0.

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.