Telegram RegisterThe public register of Telegram
Telegram profile photo for Sae Itoshi.

Channel

Sae Itoshi.

@Itohi_Sae

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

222subscribers

+10 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1003241500010
TypeChannel
Username@Itohi_Sae
CreatedBetween 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/Itohi_Sae

Growth

2122222176 August 2026 — 212 subscribers6 August 2026 — 214 subscribers7 August 2026 — 214 subscribers13 August 2026 — 222 subscribers6 August 202613 August 2026
4 measurements spanning 6 days, net +10. 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 211–224 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 01:03222+8
7 Aug 2026, 03:32214no change
6 Aug 2026, 19:52214+2
6 Aug 2026, 16:40212first reading

Engagement

19 posts held, back to 6 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
17.7%
avg views ÷ 222 subscribers
Avg views / post
39.3
19 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
19
of 19 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 held19 (6 August 20266 August 2026)
Views total747
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 03:32 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.

Recent posts

6 Aug 2026, 13:20 UTC51 viewsread 7 August 2026
Photo

ㅤ‌ ⏝ֽ😻𝐖𝐇𝐀𝐓 ❓ ִִ ✨ ݁ 🧪 😻 𝑡ℎ𝑖𝑠 𝑖𝑠 ִִ ◝ 🃏 🩷 𝐍𝐞𝐬𝐬 𝐀𝐥𝐞𝐱𝐢𝐬🤍𝐝𝐚𝐢𝐥𝐲&𝑐𝑓⋮ ✨ — нравится прекрасный Несс ֺ ⏝︶⏝⏝ֽ 𓂂 .🐾 ◟ ݁ ищешь контент с ним ❓ ֺ🤩 🍭 𝑠𝑢𝑏𝑠𝑐𝑟𝑖𝑏𝑒 ❗️🤩

6 Aug 2026, 13:15 UTC45 viewsread 7 August 2026
Photo

ㅤ🩷 ₍ ᩙ ͡( 𝐒𝐓𝐎𝐏 🎀 ⤸ ꒱ ִִ ݁ ︶ 𝖻𝗅𝗎𝖾 𝗅𝗈𝖼𝗄 ִִ 𝒹𝒶𝒾𝓁𝓎 ◝ 💘 ⋮ 🌟 — хочется ֺ ⏝︶ ⏝⏝ֽ . контента ◟ ݁ по блю локу ?? ֺ🥹 𝑠𝑢𝑏𝑠𝑐𝑟𝑖𝑏𝑒 !!! 🌟🌟

6 Aug 2026, 13:10 UTC43 viewsread 7 August 2026
Photo

🗝 ₍ ᩙ ͡( 𝐒𝐓𝐎𝐏 ❗️ ⤸ ꒱ ִִ ݁ ︶ 𝖵𝗂𝗏𝗂𝖺𝗇 𝖧𝗒𝗀𝗈 ִִ 𝒹𝒶𝒾𝓁𝓎 ◝ ⋮ ❤️ — хочется ֺ ⏝︶ ⏝⏝ֽ . контента ◟ ݁ с Хьюго ??? ⚙️ 🌟 ֺ 𝑠𝑢𝑏𝑠𝑐𝑟𝑖𝑏𝑒 ❗️

6 Aug 2026, 13:05 UTC44 viewsread 7 August 2026
Photo

⠀ꆭ ˓ ── «Я перестал мечтать, так что и ты тоже перестань. Иначе реальность тебя сломает» ― 🌟ㅤׂㅤ 🫗 ㅤ𐧾 ۪ Welcome to. . ֓ ︵᷼ ۪ ֓ ︵᷼ 𝐕𝐢𝐯𝐢𝐚𝐧 𝐇𝐲𝐠𝐨 ׄ ⋮ ׄ ׅ𝒃𝒍𝒐𝒈𝃛𝃛ુ

6 Aug 2026, 10:24 UTC30 viewsread 7 August 2026
Forwarded from @SACRIFICEDISPPhoto

.⭐️ give in to temptation in ⭐️. the name of Sacrifice Dispatch TĤE DAY ØF THE ASÇENSĮON ÒF — 01.08.26 ŞO7LS Sacrifice Dispatch предоставляет возможность высказать свое мнение о фд Блю Лока. Неважно, будет это перс/пейринг из аниме, контент-мейкер, типуха из флуда либо же вы захотите просто пообщаться, — вы останетесь ПОЛНОСТЬЮ АНОНИМНЫМ 🌟🌟 Be ready for a redemption arc Is

6 Aug 2026, 09:20 UTC53 viewsread 7 August 2026
Forwarded from @MERCHbllkPhoto

. . . хочу показать своего плюш наги...🫥 — кто-то подскажет,где можно купить мерч с отоей?🫥 — у меня есть мерч, но хочу его продать. . . 🫥 🥹задавался подобными вопросами?ˎˊ˗ ⤷ 👀👀👀👀 👀👀👀👀 👀👀👀 💭💭💭💭💭💭💭💭💭💭 создан именно для тебя ! 🧊🧊 ㅤ ㅤ

6 Aug 2026, 09:15 UTC31 viewsread 7 August 2026
Forwarded from @price_kaeru

ㅤ 🌸🥹𝗿𝗻𝗶𝘀 𝐝𝐚𝐢𝐥𝐲𝐜𝐟 ︶⏝ ◜ понравилась химия между ֗֗ ⏜ двумя парнями из 𝐛𝐥𝐥𝐤 🖤 🤩 и вы хотите видеть ⸝⸝ ︶ 🤩больше контента с ними ❓ ִ 🤩🤩 ֺ ꒱ ꒱ 𝒕𝒉𝒆𝒏. . . ⏜

6 Aug 2026, 09:10 UTC33 viewsread 7 August 2026
Forwarded from @pricewelsPhoto

🎀⎯ׅ⎯ׄ𝓌𝓌 ִ ℛ𝐢𝐧 𝐈𝐭𝐨𝐬𝐡𝐢 🎀 🎁 ⏝ִ ︶ нравится 🔤тоши 🔤ин 🤍 🤍🤍 из 𝐛𝐥𝐮𝐞 𝐥𝐨𝐜𝐤❓🥹 ⏜꯭ֺ︵𓈒࡙ ֺ⁃ 𝒐𝒓 ищешь контента по нему⁉️ 🤩🕯🤩𝖳𝗁𝖾𝗇 𝖼𝗈𝗆𝖾 𝗁𝖾𝗋𝖾.🤩🤩🤩🤩

6 Aug 2026, 09:05 UTC34 viewsread 7 August 2026
Forwarded from @dailynagisagiPhoto

🎀 ⋮ 𝑐𝑓𝑑𝑎𝑖𝑙𝑦 ִ 𝑁𝑎𝑔𝑖𝐼𝑠𝑎𝑔𝑖 ㅤㅤㅤㅤ 👘👘 . 𝐬𝐮𝐛𝐬𝐜𝐫𝐢𝐛𝐞 🤩 любишь дуэт ленивого гения и бога адаптации 🥹。⎯ из 𝑏𝑙𝑢𝑒 𝑙𝑜𝑐𝑘🥹 🌟🌟

6 Aug 2026, 09:02 UTC38 viewsread 7 August 2026
Forwarded from @kaiserdai1yVideo

ㅤ⠀⠀ㅤ⠀⠀ 🥀ㅤ᷼⏜ְ www.Kaiser.com 🖤 ㅤ⠀⠀♡゙ 𝑊𝐴𝐼𝑇 ̶ W̶A̶I̶T̶ 𝖆 𝖇𝖎𝖙. . . 🐾 🥹🍼🍼 ➖скαℓι кαηαℓ c ⲉⲿⲉⲇⲏⲉⲃⲏыⲙ ⲕⲟⲏⲧⲉⲏⲧⲟⲙ ⲡⲟ 𝐊𝐚𝐢𝐬𝐞𝐫 𝐌𝐢𝐜𝐡𝐚𝐞𝐥 из 𝕭𝖑𝖚𝖊 𝕷𝖔𝖈𝖐?? ㅤ⠀💭 ᙢᗝᒋᗪᗣ ɜᥲх᧐дᥙ ‼️ 𝅥𝄀 🥡

6 Aug 2026, 08:55 UTC33 viewsread 7 August 2026
Forwarded from @pricewelsPhoto

🎀🥹🔔🥹😊𝖾𝗅𝖼𝗈𝗆𝖾 𝗍𝗈 . . 🎁 🍼 🎀🤩🤩🪽🥹﹫ℬ𝑛𝑠𝑒𝑑𝑎𝑖𝑙𝑦𝑐𝑓 🎀 🍼 понравился пейринг баннисаэ 🤩🤩🤩🤩🤩🤩из blue lock❓🥹 🎀 🤩🍼 𝑜𝑟 𝑚𝑎𝑦𝑏𝑒 ищете дейлик по ним⁉️ 🎀🎀🤩😻 𝘵𝘩𝘦𝘯 ⇌ 𝒔𝒖𝒃𝒔𝒄𝒓𝒊𝒃𝒆

6 Aug 2026, 08:50 UTC35 viewsread 7 August 2026
Forwarded from @GAMELOCK_BLLKNETPhoto

🔥🔤elcome to GAME LOCK❗️ 💬___🤩🌟🌟🤩⌨🤩 ⭐️⭐️🔤 данной сетке вы можете следить за развитием блюлоковцев во время того, как они попадают в виртуальный мир, становясь игроками с настоящими способностями! 😀😀😀😀🔇💬💬💬 🖱️ 🔤дём вас здесь!😝

Showing the 12 most recent of 19 posts we hold for @Itohi_Sae. 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 — 74,097 of 1,481,217entries 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.

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 17 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.

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

“Sae Itoshi.” (@Itohi_Sae), 222 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Itohi_Sae.

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.