Telegram RegisterThe public register of Telegram
Telegram profile photo for ` 𝒊-𝒔𝒂𝒏 𝒊𝒏𝒇𝒐

Channel

` 𝒊-𝒔𝒂𝒏 𝒊𝒏𝒇𝒐

@i_0427

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

667subscribers

-1 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002511088842
TypeChannel
Username@i_0427
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/i_0427

Growth

667668667.511 Aug 2026, 06:32 — 668 subscribers11 Aug 2026, 06:45 — 668 subscribers11 Aug 2026, 23:02 — 667 subscribers11 Aug 2026, 06:3211 Aug 2026, 23:02
3 measurements taken within a single day, net -1. 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 667–668 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 23:02667-1
11 Aug 2026, 06:45668no change
11 Aug 2026, 06:32668first reading

Engagement

14 posts held, back to 2 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 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
23.7%
avg views ÷ 667 subscribers
Avg views / post
158
14 posts measured
Reaction rate
15.0%
reactions ÷ views · ER floor
Posts in window
14
of 14 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 6 August 2026
Posts held14 (2 August 20266 August 2026)
Views total2,214
Reactions total333
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 06:45 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.

What this channel posts

Video runtime
1m 07s
Average length
34s

Measured directly from 2 videos 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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 521745076565576896818756.2%
custom 536638046174656914314643.8%

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

Measured over the 14 most recent posts we hold, published 2 August 2026 to 6 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

6 Aug 2026, 10:08 UTC159 views28 reactionsread 11 August 2026
Photo

𝜗℘ྀི . ׄ #inst┊03.08 ꒱ #無所属

custom 521745076565576896828

6 Aug 2026, 10:07 UTC137 views20 reactionsread 11 August 2026
Video

𝜗℘ྀི . ׄ #twt┊04.08 ꒱ 【Новый пост в TikTok】 Аи (Mushozoku) × Ан (XaaXaa) сделали совместный чеки. ※Видео, накопленные с июля, выкладываю последовательно. #無所属 † #TikTok

custom 521745076565576896820

6 Aug 2026, 09:59 UTC137 views20 reactionsread 11 August 2026
Photo

𝜗℘ྀི . ׄ #twt┊03.08 ꒱ Сольный тур Mushozoku «Прогулка по руинам без возврата» Вчера прошёл второй день в Кансае, Шинсайбаши. Спасибо за этот день! В этом году это уже третий ванман в Шинсайбаши. Лайв в Кобе (Санномия) был очень эмоциональным, но с чётким разделением на «спокойствие и активность». А вот концерт в Осаке (Шинсайбаши) был просто безумным. Не только визуал, но и сама атмосфера на этих двух выступлениях

custom 521745076565576896820

2 Aug 2026, 08:12 UTC222 views27 reactionsread 11 August 2026
Video

𝜗℘ྀི . ׄ #inst┊02.08 ꒱ Шинсайбаши. Мозг нелегально потребляет счастье. #無所属

custom 536638046174656914320custom 52174507656557689687

2 Aug 2026, 08:02 UTC211 views23 reactionsread 11 August 2026
Photo

𝜗℘ྀི . ׄ #twt┊02.08 ꒱ Я раньше выступал в Осаке, но в этот раз нам наконец удалось провести первый сольный концерт в Кобе — родном городе моего партнера. Моя давняя мечта сбылась. Сольный тур Mushozoku «Прогулка по руинам без возврата» Сендай и Кобе — места, где несколько лет назад, в период пандемии, наши лайвы были отменены. Прошло немало времени, но я бесконечно благодарен за то, что сейчас мы наконец можем рад

custom 536638046174656914314custom 52174507656557689689

2 Aug 2026, 07:52 UTC170 views22 reactionsread 11 August 2026
Photo

𝜗℘ྀི . ׄ #twt┊26.07 ꒱ BugSumi 2026, Нагоя. Выступали там как Mushozoku. Спасибо за такое количество людей, что пришлось даже вводить ограничение на вход. Мы сейчас в сольном туре, поэтому Нагоя может ждать нас в августе на полуфинал. Также мы выступим в Токио на BugSumi 2026. Еще увидимся! Ах да, я только что вернулся из Айти домой. #無所属

custom 521745076565576896817custom 53663804617465691435

2 Aug 2026, 07:42 UTC138 views19 reactionsread 11 August 2026

𝜗℘ྀི . ׄ #twt┊26.07 ꒱ 【Пару слов про фото】 Сюда ведь вход только в белом? Жутко жалею, что проигнорировал дресс-код. Ждём вас сегодня на BugSumi в Нагое! Только вышел из дома в Токио, уже весь потный. Скоро приму душ. Быть грязным достаточно и на концертах. #無所属

custom 536638046174656914311custom 52174507656557689688

2 Aug 2026, 07:32 UTC137 views24 reactionsread 11 August 2026
Photo

𝜗℘ྀི . ׄ #twt┊25.07 ꒱ Аи и Рито Mushozoku × XANVALA 【Пару слов про фото】 Наказанные за проделки в школе собрались для совместного фото, надеясь на создание легенды, но даже не подозревали, как сильно потом будут жалеть. ※ Всё это выдумка. Мои слова не имеют никакого отношения к реальным лицам или организациям. #無所属

custom 536638046174656914314custom 521745076565576896810

2 Aug 2026, 07:22 UTC143 views28 reactionsread 11 August 2026
Photo

𝜗℘ྀི . ׄ #twt┊25.07 ꒱ Аи и Рито Mushozoku × NICOLAS 【Пару слов про фото】 Кастинг на озвучку «Токийских мстителей» ведь здесь проходит? Я пройду его самым физическим, примитивным и фетишистским способом. #無所属

custom 536638046174656914318custom 521745076565576896810

2 Aug 2026, 07:12 UTC147 views25 reactionsread 11 August 2026
Photo

𝜗℘ྀི . ׄ #twt┊24.07 ꒱ Мероприятие, организованное Аи и Рито Mushozoku 「Принудительный хэдбэнг -※Без какого-либо принуждения -」 Аи и Рито Mushozoku / XANVALA / NICOLAS Сегодняшнее событие состоялось благодаря проверенной комбинации групп, которые уже проводили 2МАН и удачно выступали вместе, а также благодаря вам и вашей безоговорочной поддержке. По сути, этот 3МАН являлся 4МАН, если считать фанатов на площадке. Сп

custom 536638046174656914317custom 52174507656557689688

2 Aug 2026, 07:02 UTC159 views22 reactionsread 11 August 2026
Photo

𝜗℘ྀི . ׄ #twt┊24.07 ꒱ Жду вас сегодня в harevutai! Не забудьте головы. #無所属

custom 521745076565576896815custom 53663804617465691437

2 Aug 2026, 06:52 UTC145 views21 reactionsread 11 August 2026

𝜗℘ྀི . ׄ #twt┊23.07 ꒱ Пусть сегодняшний день будет будничным и ничем не примечательным. С добрым утром #無所属

custom 536638046174656914312custom 52174507656557689689

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

Citation-graph rank

Citation-graph rank — 1,273,093 of 1,480,944entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“` 𝒊-𝒔𝒂𝒏 𝒊𝒏𝒇𝒐” (@i_0427), 667 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/i_0427.

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.