Channel
@urabokuzine
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
43subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003761157652 |
|---|---|
| Type | Channel |
| Username | @urabokuzine |
| Created | 13 April 2026 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/urabokuzine |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 00:40 | 43 | +2 |
| 22 Aug 2026, 20:16 | 41 | -1 |
| 10 Aug 2026, 17:02 | 42 | no change |
| 6 Aug 2026, 19:51 | 42 | first reading |
11 posts held, back to 13 April 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 11 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
85 reactions across 9 posts, in 8 distinct kinds. The most used accounts for 37.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 32 | 37.6% | |
| 🔥 | 13 | 15.3% | |
| 🥰 | 10 | 11.8% | |
| custom 5397717956182446939 | 9 | 10.6% | |
| ❤🔥 | 9 | 10.6% | |
| 💋 | 5 | 5.88% | |
| 💘 | 4 | 4.71% | |
| custom 5398051155450304014 | 3 | 3.53% |
Custom emoji. 2 of the rows above are 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 9 of the 11 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 85 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 13 April 2026 to 3 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.
🤍 🤔 В нашем особняке Тасогаре в последнее время такой шум... Встречайте наших новых стражниц и стражей! … ~ Художницы/ки: 🌹 бордюра - тг 🤍Deadуля – тг 🌹 morinaga – тг 🤍Magnavarra – вк 🌹 личи – тг | вк 🤍Senku – тг 🌹 vissha – тг 🤍Yams – тг | вк 🌹 N,?iR – тг 🤍Hualin – тг 🌹 сушка – тг 🤍Дантист – тг | тикток 🌹 Lian – тикток 🤍lew – тг 🌹 min - тг Писательницы/ли: 🤍Vulpecula – фикбук 🌹 Lun – ао3 | вк
❤🔥5🔥2🥰2
Все приглашения были разосланы! В ближайшее время опубликуем список наших творцов♡
❤🔥4❤3🥰2
⭐️⭐️⭐️🤩 Набор завершён! 🤩 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 🤩Всем огромное спасибо за участие🙂 В связи с тем, что заявок оказалось слишком мало (12), мы принимаем абсолютно всех.❤️ 🤩Ответы будут отправлены в течение двух дней. Также мы приняли решение, что ещё ненадолго откроем формы, так что если вы забыли подать заявку, можете сделать это в течение этих двух дней.
❤6💘4🔥1
Напоминаем, что сегодня последний день приёма заявок! Набор закроется 16 мая в 2 часа ночи по мск
🥰4❤1
Мы боимся, что не сможем сделать страницы со всеми второстепенными персонаж(к)ами, поэтому будем очень рады, если вы напишете, кого хотите видеть в зине. Можно написать как в комментарии, так и в лс канала До конца набора осталось 4 дня!
💋5🥰2❤1
Будущие стражи Звельт, набор авторок и авторов является открытым до 19.05 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 Анкета для художниц/ков Анкета для писательниц/ей Анкета для косплеерш/ов 🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍🤍 В планах: -20-30 художниц и художников -5-8 писательниц и писателей -2-5 косплеерш и косплееров -Формат А5, мерч • Имейте ввиду, что информация может поменяться Желаем всем удачи!💜
custom 53977179561824469397❤4custom 53980511554503040143🔥1
Набор участниц и участников начнётся 21 апреля💜 Вопрос по поводу формата зина и мерча ещё будем решать, но сейчас больше склоняемся к печатному формату, чем к электронному
🔥9❤2
Проверка заинтересованности!
The shares total 144%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
❤6custom 53977179561824469392
Проверка интереса к электронному зину по "The betrayal knows my name" 🤍🤍🤍🤍🤍🤍🤍✝️🤍🤍🤍🤍🤍🤍🤍 Ваш отклик очень важен для нас и он решит дальнейшую судьбу зина В планах: 💜 Электронный формат 🤔 2-4 писателей/ниц 💚 15-25 художников/ниц • При бо́льшей заинтересованности, чем нами ожидается, возможна печать мерча, но, скорее всего, всё равно печатного зина не будет Все вопросы по поводу зина можно задать в личных сообщения…
❤9
Channel created
Channel photo updated
Showing the 11 most recent of 11 posts we hold for @urabokuzine. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Проверка заинтересованности!
The shares total 144%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 11 most recent posts we hold, published 13 April 2026 to 3 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
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.
@urabokuzine named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“The betrayal knows my name ZINE” (@urabokuzine), 43 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/urabokuzine.
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.