Telegram RegisterThe public register of Telegram
Telegram profile photo for KANZAKI SOUMA!

Channel

KANZAKI SOUMA!

@KanzakiSouma_ES

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

35subscribers

-3 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1003812955184
TypeChannel
Username@KanzakiSouma_ES
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live13 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/KanzakiSouma_ES

Growth

353836.513 August 2026 — 38 subscribers13 August 2026 — 38 subscribers21 August 2026 — 37 subscribers6 September 2026 — 36 subscribers13 September 2026 — 35 subscribers13 August 202613 September 2026
5 measurements spanning 32 days, net -3. 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 35–38 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 18:5835-1
6 Sept 2026, 14:3536-1
21 Aug 2026, 14:2837-1
13 Aug 2026, 14:0638no change
13 Aug 2026, 04:0338first reading

Engagement

20 posts held, back to 12 August 2026the 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 12 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
150.0%
💔150.0%

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 2 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 2 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 12 August 2026 to 12 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.

Recent posts

12 Aug 2026, 16:44 UTC5 viewsread 13 August 2026

Хм? Ах, добрый вечер, Цукинага-доно, рад встрече! Не следует волноваться, никакого потопа не было. Аой просто чуть не утонул в море, а я всего лишь помог ему добраться до сюда, потому мы оба и намокли!

12 Aug 2026, 15:11 UTC7 viewsread 13 August 2026

Хм? А ты разве не обронил их в воду?

12 Aug 2026, 15:11 UTC7 viewsread 13 August 2026

Прошу меня простить, мне следовало действовать быстрее... Что ж, надеюсь, фен здесь всё же есть.

12 Aug 2026, 14:54 UTC7 viewsread 13 August 2026

Хм? Ты уверен? Что ж, тогда отправляемся туда!

12 Aug 2026, 13:54 UTC7 viewsread 13 August 2026

Слушай, мне кажется, бесполезно просто так ходить кругами. Нам необходимо найти иной способ отыскать нужный дом, иначе мы так до самой ночи будет бродить...

12 Aug 2026, 13:25 UTC7 viewsread 13 August 2026

Аой?! Пожалуйста, оставайся в сознании, а то я же совсем не имею представления, что делать в подобных ситуациях!

12 Aug 2026, 13:20 UTC7 viewsread 13 August 2026

Я не уверен, что открывать каждую дверь - хорошая идея... А оставлять тебя одного в таком состоянии было бы очень безрассудным решением, ввиду твоего плохого самочувствия. Поэтому ты отправишься со мной. К слову, если тебе уже лучше, и ты чувствуешь, что можешь самостоятельно ходить, дай мне знать, чтобы я тебя отпустил.

12 Aug 2026, 13:11 UTC7 viewsread 13 August 2026

Но как мы его отыщем, если мы понятия не имеем, где находится ваш дом?

12 Aug 2026, 12:58 UTC6 viewsread 13 August 2026

Несу-несу! Хмм, интересно, как долго нам ещё осталось идти? Я не совсем понимаю, в каком направлении нам следует идти, так что, возможно, нам придется довольно долго плутать...

12 Aug 2026, 12:57 UTC6 viewsread 13 August 2026

Прости меня, пожалуйста, но я отказываюсь участвовать в этом.

12 Aug 2026, 12:53 UTC5 viewsread 13 August 2026

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

12 Aug 2026, 12:47 UTC7 viewsread 13 August 2026

Уу, как много вопросов... Прости, но я без понятия, где может находиться твой брат. Возможно, он в своём доме? Но я не знаю, где именно располагается его дом. Жуков? Нет, жуков я не боюсь, но какова цель твоего вопроса?

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

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.

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.

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

“KANZAKI SOUMA!” (@KanzakiSouma_ES), 35 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/KanzakiSouma_ES.

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.