Channel
@BookTaleRP_Info
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
44subscribers
+8 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003845559337 |
|---|---|
| Type | Channel |
| Username | @BookTaleRP_Info |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/BookTaleRP_Info |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 01:37 | 44 | +2 |
| 14 Sept 2026, 02:22 | 42 | no change |
| 10 Sept 2026, 02:21 | 42 | +4 |
| 24 Aug 2026, 08:42 | 38 | +3 |
| 15 Aug 2026, 17:08 | 35 | -1 |
| 15 Aug 2026, 01:47 | 36 | first reading |
20 posts held, back to 18 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 20 posts for this entry, the most recent from 24 August 2026. An engagement rate over an empty window would be a number about nothing.
39 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 25.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5314504888967788361 | 10 | 25.6% | |
| custom 5314679780036078413 | 8 | 20.5% | |
| custom 5314282482676297310 | 7 | 17.9% | |
| custom 5314398240634859186 | 7 | 17.9% | |
| custom 5336957045256001015 | 7 | 17.9% |
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 20 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 39 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 18 August 2026 to 24 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.
«🎁» Проблема устранена. Проект выходит из технических работ и с радостью принимает к себе новых ролевиков ! 🎁 🧴🧴🤩ПОСТАВИТЬ БРОНЬ 🧴🧴🤩ИЗУЧИТЬ СЮЖЕТ
custom 53146797800360784133custom 53145048889677883612custom 53369570452560010152custom 53143982406348591861
«🥹» Если вы планировали вступить к нам, то, к сожалению, сейчас столкнулись с проблемой: из-за неполадок с серверами Teletype, на котором мы публикуем статьи проекта, часть материалов временно недоступна. 🤩Если в течение ближайших двух дней проблема не решится, мы начнём переносить все статьи на более доступный формат. Поэтому временно проект приостанавливает приём новых участников. Как только ситуация разрешится, м…
custom 53142824826762973105custom 53143982406348591863custom 53146797800360784133custom 53145048889677883612custom 53369570452560010152
.⊹ ⊱› 𝓗абор ОТКРЫТ! 「 🔠🔠/🔠🔠 」 🪧 в чате есть такие боты как: 🤩Ирис 🤩Зазывала 🤩Бункер 🤩Крокодил 🤩Quotly
custom 53145048889677883614custom 53142824826762973101custom 53143982406348591861custom 53146797800360784131
Sticker, posted without a caption
ꫂ᭪ 𓂃 ׄ › Бургерпентс / Владелец ➛ анон 𝓑 обязанности этого человека входит :: – Полное оформление канала и работу над сюжетом; — Продвижение ролевого проекта; — За соблюдением правил флуда/рп чата и контролем полномочий администрации; — Помощь новым участникам влиться; — Проверка анкет. ꫂ᭪ 𓂃 ׄ › Рулс / Старший Админ [РЕСТ] ➛ анон 𝓑 обязанности этого человека входит — Проверку анкет; — За соблю…
File, posted without a caption
Sticker, posted without a caption
❌❌🤩🤩🔤ступление ❌❌🪧🪧🪧🪧🪧🪧🪧 🍙Прежде чем поставить бронь на своего желаемого персонажа, убедитесь, что вы ознакомились со следующими материалами : 🤩Правила 🤩в особенности узнали о нашей системе глав и команд 🤩Сюжет 🤩Изучили шаблон анкеты ❌❌🪧🪧🪧🪧🪧🪧🪧 🔠. 🔤тобы поставить бронь и отправить анкету, пишите в нашего бота: @Booktale_ANKETY_bot 🔠. 🔤нкета всегда пишется до вступления и на написании её дается 5 дней. 🔠. 🔤аша анкета…
Sticker, posted without a caption
❌❌🤩🤩✨🤩оп.инфо ❌❌ 🪧🪧🪧🪧🪧🪧 🔠аинтересовались нашим проектом? Тогда обязательно загляните в раздел «ДОП.ИНФО». Там собрана вся информация, которая понадобится перед вступлением: шаблон анкеты, список занятых ролей и многое другое. 🤍🤍🔠АЙТИ В ДОП.ИНФО ❌❌ 🪧🪧🪧🪧🪧🪧 🪽Back to navigation. . .
File, posted without a caption
Sticker, posted without a caption
Showing the 12 most recent of 20 posts we hold for @BookTaleRP_Info. 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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“BOOKTALE 𝖱𝖯” (@BookTaleRP_Info), 44 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/BookTaleRP_Info.
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.