Telegram RegisterThe public register of Telegram
Telegram profile photo for Kuroshitsuji | Black Butler Zine

Channel

Kuroshitsuji | Black Butler Zine

@kurozine20

On this record: Topic · Previous handles · Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry

344subscribers

+207 since we began measuring on 31 August 2026

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

Register entry

Telegram ID-1004415117837
TypeChannel
Username@kurozine20
Created28 August 2026 — measured — dated from the channel’s first post
First recorded31 August 2026
Last confirmed live12 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/kurozine20

Topic

Art & design — 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 8 October 2026 and assigned it the closest of 31 fixed categories, at 44% 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 why it has no browse page of its own yet.

Previous handles

@kurozine20 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@kuroartbook
held 31 August 2026 – 31 August 2026

Growth

137344240.531 August 2026 — 137 subscribers31 August 2026 — 137 subscribers31 August 2026 — 147 subscribers8 October 2026 — 342 subscribers12 October 2026 — 344 subscribers31 August 202612 October 2026
5 measurements spanning 42 days, net +207. 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 106–375 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 15:29344+2
8 Oct 2026, 19:22342+195
31 Aug 2026, 17:24147+10
31 Aug 2026, 14:15137no change
31 Aug 2026, 14:00137first reading

Engagement

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

ERR · 30 days
136.4%
avg views ÷ 344 subscribers
Avg views / post
469
13 posts measured
Reaction rate
7.64%
reactions ÷ views · ER floor
Posts in window
13
of 18 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 8 October 2026
Posts held18 (28 August 2026 – 8 October 2026)
Views total6,099
Reactions total466
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Oct 2026, 19:22 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.

Reaction mix

519 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 43.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤22443.2%
custom 538870585637002547812724.5%
custom 54451496465591509737414.3%
🔥6712.9%
💔275.20%

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

Measured over the 18 most recent posts we hold, published 28 August 2026 to 8 October 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

8 Oct 2026, 09:44 UTC182 views5 reactionsread 8 October 2026
Forwarded from @uchihazinePhoto

Срок оформления предзаказов постепенно подходит к концу. Если еще не успели оформить — поспешите.

❤5

8 Oct 2026, 09:25 UTC206 views31 reactionsread 8 October 2026
Photo

- и давненько не было нашей рубрики веселья. сиэль как всегда, а себастьян догнал гробовщика. попытался. все равно циркачи впереди, как и грелль. не везет демонюге.

❤22custom 53887058563700254789

8 Oct 2026, 09:13 UTC205 views37 reactionsread 8 October 2026
Photo

- еще немного, и мы погрузимся в удивительную тишину работы...

❤27custom 54451496465591509736custom 53887058563700254784

27 Sept 2026, 07:28 UTC535 views48 reactionsread 8 October 2026
Photo

Photo, posted without a caption

custom 544514964655915097325❤14custom 53887058563700254789

27 Sept 2026, 06:00 UTC516 views65 reactionsread 8 October 2026

— в связи с производственной необходимостью и грамотного распределения ресурса организатора, чтобы проект вышел достойным и качественным, сроки сдвигаются. набор продлевается до 15 октября.

custom 538870585637002547841💔19❤5

24 Sept 2026, 07:30 UTC596 views56 reactionsread 8 October 2026
Photo

- рубрика для веселья - держу в курсе. Себастьян немного поднажал, вы посмотрите. Может же, когда хочет. Но всё ещё уступает Циркачам - и в целом можно понять почему...

❤29custom 544514964655915097314custom 538870585637002547813

21 Sept 2026, 10:06 UTC620 views40 reactionsread 8 October 2026

- пс, дорогие фандомовцы и не только, а вы ведь понимаете, что осталось около 10 дней до окончания набора? (я не считаю сегодняшний денек, он уже в разгаре)

❤29custom 538870585637002547811

19 Sept 2026, 10:15 UTC631 views24 reactionsread 8 October 2026
Forwarded from @olaytrinketsPhoto

━━━━➳༻🕸🕷🕸༺➳━━━━ На Лондонские улицы опускается ночной туман. Город засыпает. Выползают пауки... Первой главе Темного Дворецкого исполнилось 20 лет, второму сезону вот-вот 16, а для моего канала пришло большое событие — я отпечатала свой первый крупный проект — Темная Мафия — возможно, первая настольная игра по Темному Дворецкому🥰 И помимо своей радости, я хочу также поделится частью этих коробочек, разыграв две из …

custom 544514964655915097312❤7custom 53887058563700254785

19 Sept 2026, 10:15 UTC491 views13 reactionsread 8 October 2026

Любопытный розыгрыш — очаровательная мафия! Приглашаю поучаствовать. 😘

❤9custom 53887058563700254784

18 Sept 2026, 18:39 UTC524 views38 reactionsread 8 October 2026

- мне нравится тот факт, что алоис обогнал себастьяна и даже гробовщика. думаю, алоис был бы счастлив от этого.

❤30💔8

18 Sept 2026, 18:37 UTC551 views44 reactionsread 8 October 2026
Photo

- рубрика держу в курсе. сиэль держит позиции, грелль дышит в спину, а себастьян.... дуралей? всех с пятничкой!

❤33custom 538870585637002547810custom 54451496465591509731

17 Sept 2026, 11:22 UTC531 views31 reactionsread 8 October 2026

- Тем временем у нас до конца набора осталось 3 недели!

🔥25custom 54451496465591509735custom 53887058563700254781

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

Polls

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.

28 Aug 2026, 08:57 UTCAnonymous Poll402 voters

🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤

  1. Да, хотелось бы поучаствовать👼38%
  2. Да, хотелось бы приобрести🧸26%
  3. Да, хотелось бы понаблюдать☦26%
  4. Люблю тыкать кнопочки🎀32%

The shares total 122%, 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 18 most recent posts we hold, published 28 August 2026 to 8 October 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.

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 1 registered channel — 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.

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

“Kuroshitsuji | Black Butler Zine” (@kurozine20), 344 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/kurozine20.

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.