╭─────── ⚽️ ✧.* │ 𝑵𝑬𝑾 𝑴𝑨𝑻𝑪𝑯... ✦.* │ ┄> 𝑰𝑺𝑨𝑮𝑰 𝒀𝑶𝑰𝑪𝑯𝑰 . ➴ 🧩 ╰─────────────── ... 🌿 ... ┌───────────────────┐ «Тᴀʍ, ᴦдᴇ ᴨᴏбᴇдиᴛᴇᴧи, ᴇᴄᴛь и ᴨᴩᴏиᴦᴩᴀʙɯиᴇ. Еᴄᴧи я хᴏчу иᴄᴨᴏᴧниᴛь ᴄʙᴏю ʍᴇчᴛу, ᴨᴩидᴇᴛᴄя ᴄᴏᴋᴩуɯиᴛь чужую.» └───────────────────┘ ~ Пᴩиʙᴇᴛ! Нᴀ ᴄʙяɜи Иᴄᴀᴦи Йᴏичи. Бᴧю ᴧᴏᴋ нᴀучиᴧ ʍᴇня ʙᴄᴇᴦдᴀ ᴄʍᴏᴛᴩᴇᴛь ᴛᴏᴧьᴋᴏ ʙᴨᴇᴩᴇд, ʍнᴏᴦᴏ ᴛᴩᴇниᴩᴏʙᴀᴛьᴄя и ᴨᴏᴄᴛᴏяннᴏ ᴩᴀɜʙиʙᴀᴛь ᴄʙᴏи нᴀʙыᴋи. Эᴛᴏ ʍᴏй ᴧичный ᴋᴀнᴀᴧ, ᴦдᴇ я дᴇᴧюᴄь ᴄʙᴏиʍи ʍыᴄᴧя…

Channel
—𝓻𝓮𝓸𝓷𝓪𝓰𝓲 𝓭𝓪𝓲𝓵𝔂 ᝰ.ᐟ
@reo_nagi
On this record: Growth · Engagement · Posts · Citations · Cite this entry
45subscribers
+10 since we began measuring on 13 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004345499288 |
|---|---|
| Type | Channel |
| Username | @reo_nagi |
| Created | Between 1 June 2026 and 31 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/reo_nagi |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 14:00 | 45 | +10 |
| 13 Sept 2026, 06:22 | 35 | no change |
| 13 Sept 2026, 05:47 | 35 | first reading |
Engagement
20 posts held, back to 12 September 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.
- ERR · 30 days
- 26.1%
- avg views ÷ 45 subscribers
- Avg views / post
- 11.8
- 20 posts measured
- Reaction rate
- 0%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 20 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. It is computed over the 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 September 2026 |
|---|---|
| Posts held | 20 (12 September 2026 – 13 September 2026) |
| Views total | 235 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Sept 2026, 06: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.
Recent posts
Спасибо большое за голоса! #щп
🦇ㅤִ ︵ 𝖕𝖍𝐨𝖇𝖎𝐚 ݄ 𝐜𝐨𝐧𝖋𝐞𝐬𝐬𝖎𝖔𝐧 ⏝ ︶ боитесь ִ высоты ? 𝒐𝒓 𝒎𝒂𝒚𝒃𝒆 у вас ֺ ︶ ⏝ ㅤㅤклаустрофобия ? ⎯ׄ🤩 поделитесь своими мыслями 🎀⸝⸝ по поводу фобий ִ 𝖙𝐚𝐤𝖊𝖇𝐨𝐭 ❪ 𝐦𝐩𝖕𝖔𝐬𝐭 ❫ 𝐧𝐚𝐯𝖎𝖌𝖆𝐭𝐢𝐨𝐧
ㅤ 𝐥𝐨𝐨𝐤 𝐡𝐞𝐫𝐞 ! 𝒾𝓉𝓈 𝒶 . . . 🔗🔗 ⏝︶ 𝐝𝐚𝐢𝐥𝐲𝐜𝐟🥹𝑟𝑖𝑛 𝑖𝑡𝑜𝒔𝒉𝑖 ◞ ִ понравился этот ⸝⸝ 💕 ︵⏜ 🩸 очаровательный юноша ֔ 𝑎𝑛𝑑 ִ вы желаете видеть ⏝ ⏝︶⏝ больше контента ֔🎇 ㅤ◟ 𝐰𝐢𝐭𝐧 ִ ✨ ֺ 𝖍𝐢𝐦 🗒 ⏝︶ 🔗🔗 ┊ 𝖙𝖍𝐞𝐧 . . . скорее ➡️ подписывайся !
ㅤִ ︵ㅤ𝖎𝐧𝐟𝐨 𝑐𝑜𝑛𝒻𝑒𝑠𝑠𝑖𝑜𝑛 ܄ 📍 хотите оценку ﹠ совет ︶ 🎀 ֔ по оформлению вашего инфо and ִ 𝓌𝓌 ◟ вы в поисках ⁽ 🥂 ₎ взаимных просмотров 、 мью 、 реакций 、 𝐞𝐭𝐜 🦢 ㅤ₍ 𝐧𝐚𝐯𝐢𝖌𝐚𝐭𝐢𝐨𝐧 🤩 𝖒𝐩 𝖕𝐨𝐬𝐭 ⁾ ㅤ✍️ ܄ㅤ𝐛𝐨𝐭 𝟒 𝑦𝑜𝑢𝒓 𝒕𝑎𝑘𝑒𝑠 ◞ ◞ ㅤㅤ ⸝⸝ ㅤ𝓸𝐰𝐧𝐞𝐫 : 𝐤𝐚𝐞𝐫𝐮
︶⏝ ﹫𝖽𝖺𝗂𝗅𝗒𝗌𝗉𝖺𝗋𝗑𝗂𝖾🎀 ۫ 🎁 ◟ ִ вам понравилась ⏜🗒🗒 🌸 недотёпа в маске Искорка ⇇ 𓈒. вместе с её виртуальным ꒱ ꒱ 🤩 ⎯ׅ⎯ׄ образом Искры ︶ ִ ︶ ︵ׄ⏜ 𝐚𝐧𝐝 ищете с ней ┊❤️❤️ 🎁⁝🤩 больше контента ❓
ִ ︵ ︵ 𝐤𝐚𝐢𝐬𝐚𝐞 𝒅𝒂𝒊𝒍𝒚𝒄𝓯 🤩🤩◞ 🥡 ︎⇉ полюбились двое ֺ 🌟 ⏝ прекрасных парней из 𝐛𝐥𝐥𝐤 ֔ ꒱ и вы желаете видеть ⏜🍹 ⎯ׅ⎯ׄ больше контента с ними ? 🤩🤩🤩 𝓼𝓸𝓸. . . 𝓳𝐨𝐢𝐧 𝐮𝐬 ! ✨
ㅤ 🌸🥹𝗿𝗻𝗶𝘀 𝐝𝐚𝐢𝐥𝐲𝐜𝐟 ︶⏝ ◜ понравилась химия между ֗֗ ⏜ двумя парнями из 𝐛𝐥𝐥𝐤 🖤 🤩 и вы хотите видеть ⸝⸝ ︶ 🤩больше контента с ними ❓ ִ 🤩🤩 ֺ ꒱ ꒱ 𝒕𝒉𝒆𝒏. . . ⏜
ㅤ 𝐥𝐨𝐨𝐤 𝖍𝐞𝐫𝐞 ! 𝒾𝓉𝓈 𝒶 . . . 🦉🦉🦉 ⏝︶ 𝗇𝖺𝗀𝗂𝗋𝗂𝗇🥹𝒅𝒂𝒊𝒍𝒚𝒄𝒇 ◞ ◟ всей ֺ 💕֔ душой фанатеете ︶︵ по пейрингу ┊ 🤩🤩 ⎯ׅ🎂ㅤ 𝐧𝐚𝐠𝐢 ⤫ 𝐫𝐢𝐧 ︵⏜ ㅤㅤ𝑤𝑎𝑛𝑡 ִ больше контента ⏝︶⏝ с ними 🦢ִ ❤️ 🔗🔗 ┊ 𝖙𝖍𝐞𝐧 . . . скорее ➡️ подписывайся !
֔ㅤ⎯ׅ⎯ׄ𝖆𝖓𝐢𝐦𝐞 ִ ︵ 𝑚𝑒𝑒𝑡 ⋮ ✨ ㅤ𝓌𝓌 ִ ⎯ׄдавно мечтал ִ найти ܄᧓ ᷼ ᷼ новых ܄🕯 ֺ знак𑄝мых ❩❩ ᧔❤️֔ ִ 𝖔𝐫 партнёра、⏝ ͝ ⏝ ︶︶ кот𑄝рые шарят ◞ ⎯ׅ⎯ׄ𓋜 𑣲︭܄⤿ ֺ за аниме ? ┊🔮 ⏝︶ ◟ 𝖓𝐚𝐯𝐢𝐠𝐚𝐭𝐢𝐨𝐧 ͝ ᛝ ͝ 𝖒𝖕𝐩𝐨𝐬𝐭 🤩 ᛝ ⏝︶⏝ 𝗯𑄝𝐭 ִ ❤️
ㅤ 𝐥𝐨𝐨𝐤 𝐡𝐞𝐫𝐞 ! 𝒾𝓉𝓈 𝒶 . . . 🍭 ︶ ִ ⏝ 𝐥𝐨𝐯𝐞 ﹠ 𝐡𝐚𝐭𝐞 ִ 𝓌𝓌 𝑏𝑙𝑢𝑒 𝑙𝑜𝑐𝑘❤️◟ 𝗉𝖺𝗂𝗋𝗂𝗇𝗀𝗌𝐜𝐟 ㅤ⸝⸝ ㅤжелаете обсудить ܄ тематику пейрингов ︶ ⎯ׄ🌸 ◟ между персонажами франшизы 𝐛𝐥𝐮𝐞 𝐥𝐨𝐜𝐤 🗒 ︶ ⏝ ◟ 𝐦𝐩𝐢𝐚𝐫 ⸝ 𝐛𝐨𝐭 ִ 😺 ֺ 𝐧𝐚𝐯𝐢𝐠𝐚𝐭𝐢𝐨𝐧
✨֔🦢𝐨𝐯𝐞𝐫𝐡𝐞𝐚𝐫𝐝🥹𝑏𝑙𝑢𝑒 𝑙𝑜𝑐𝑘 𝑐𝑓 ִ ◟ で ܄ здесь вы можете ︵ ⏜ ⏝ ︶ поговорить о ֺ 💎 ִ ִ любой теме、 касающейся ⏝ 🗝🗒франшизы 𝖻𝗅𝗎𝖾 𝗅𝗈𝖼𝗄 ◞ ⏝ 𝓶𝐩 𝐩𝐨𝐬𝐭 🗒 𝓷𝐚𝐯𝐢𝐠𝐚𝐭𝐢𝐨𝐧🦢
Showing the 12 most recent of 20 posts we hold for @reo_nagi. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
@price_kaeru · 97 posts⟨⟨ 𝐚𝐫𝐞 𝐲𝐨𝐮 𝐭𝐨𝐨 ? ⟩⟩ ⋮ 𝑐𝑜𝑛𝑓 ִ
@areyoutoocf · 391 post𖹭ㅤ𝐫𝐢𝐧 𝐢𝐭𝐨𝐬𝐡𝐢ㅤ𝑑𝑎𝑖𝑙𝑦 ִ 𝑐𝑓
@dailyrinitoshi · 4081 post𝗚𝗔𝗠𝗘 𝗟𝗢𝗖𝗞! 𝗕𝗟𝗟𝗞 𝗡𝗘𝗧.
@GAMELOCK_BLLKNET · 541 post♡𝅥፝֟𝄀、Ꭵ𝗻꯭︠︠𝗳𝒐 ⋮ 𝖼ᦅִ͠𝓷𝗳͜𝗲̶ꮪꮪ⃨𝐢𝗈n◞
@infoconfes · 2711 post𝐈𝐬𝐚𝐠𝐢 𝐘𝐨𝐢𝐜𝐡𝐢
@Isagi_Yoichi_blog · 291 postㅤᨦ 𝐛𝐥𝐥𝐤 𝐬𝐡𝐢𝐩𝐬 ⋮ 𝑐𝑜𝑛𝑓
@loveandhatebllkships · 781 postㅤ𝐧𝐚𝐠𝐢𝐫𝐢𝐧ㅤ𔖳ㅤ𝑑𝑎𝑖𝑙𝑦ִ 𝑐𝑓
@NagiRins · 1331 post𝐨𝐯𝐞𝐫𝐡𝐞𝐚𝐫𝐝 𖹭 𝑏𝑙𝑢𝑒 𝑙𝑜𝑐𝑘 𝑐𝑓
@overheardbllk · 621 postprice anime meet
@priceanimemeet · 141 postmp bllk quizzes
@pricebllikquiz · 201 post- 𝗉𝗋𝗂𝖼𝖾 𝗌𝖾𝗂𝗌 ‹𝟹
@priceseis · 21 post۶ㅤ𝐩𝐡𝐨𝐛𝐢𝐚ㅤ𝑐𝑜𝑛𝑓𝑒𝑠𝑠𝑖𝑜𝑛
@yourphobiacf · 241 post
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“—𝓻𝓮𝓸𝓷𝓪𝓰𝓲 𝓭𝓪𝓲𝓵𝔂 ᝰ.ᐟ” (@reo_nagi), 45 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/reo_nagi.
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.