ððð ð ê± ððºðð ðº ððŸðŒðððœ . . â . . ððºððð¥¹ððºð²ð ðð€© ð§ª ð€ð¥¹ð·ÑбОÑÑ ÐœÐ°Ð³Ðž ðrom « blue - lock » ? ðªðð ðŸÑеÑÑ ÐµÐ¶ÐµÐŽÐœÐµÐ²ÐœÑй кПМÑÐµÐœÑ Ñ Ð»ÐµÐœÐžÐ²ÑÐŒ геМОеЌ ? ? â✠ðâ ðððŸð 𥹠ð€ðŸð ðŒð¬ððŸ . .

Channel
ð®ððŸððœðŸðð ð©ð¶ððŸ ðð¶ðŸðð.ã»
@seishironagidaily
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
20subscribers
+0 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003489513940 |
|---|---|
| Type | Channel |
| Username | @seishironagidaily |
| Created | Between 1 November 2025 and 31 March 2026 â estimated from Telegramâs id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/seishironagidaily |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 11:21 | 20 | -2 |
| 10 Sept 2026, 21:00 | 22 | +1 |
| 2 Sept 2026, 19:59 | 21 | +1 |
| 27 Aug 2026, 05:38 | 20 | no change |
| 26 Aug 2026, 20:46 | 20 | first reading |
Engagement
17 posts held, back to 21 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 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 17 posts for this entry, the most recent from 26 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 16s
- Average length
- 8s
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
23 reactions across 7 posts, in 2 distinct kinds. The most used accounts for 65.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5283258117126129039 | 15 | 65.2% | |
| custom 5202022388430057523 | 8 | 34.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 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 7 of the 17 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 23 reactions in total: the kind of figure the paragraph above means by âa reaction total printed elsewhere on the pageâ.
Measured over the 17 most recent posts we hold, published 21 August 2026 to 26 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
ð€© ð»ðð¶ððð»#seishironagi #art ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€© ð®ððŸððœðŸðð ð©ð¶ððŸ ðð¶ðŸðð.ã» cr on instagramð»boost
custom 52832581171261290393custom 52020223884300575231
ð¥©ð¥©ð¥©ð¥©ð¥©ð¥©ð¥©ð¥©ð¥©ð¥©ð¥© ð€©Hello, my dears. This daily is dedicated to Itoshi Rin from Blk.ð€© ð¡ð¥ð¥ð¥ð¥ð¥ð¥ð¥ð¥ð¥ð©¹ chat || boost || vp post || bot á á á á á á á á á á ð€©ð€© ððððððð€©ð€©ð€© ð€©dministración: ð€©ð€©ð€© ð:ÑаÑкаâПМа/ÐµÑ ð€ð€:вОкÑелÑâПМа/еÑ. ð€©aiting for you!!ð«§ð«§
ðð.ððð ðððððððððð ððð¢ð¥ð²_ððð§ððš_ðð¡ð®ððš âšâºïžâ© ððªð·ððžð¶ ðð±ðªð·ð·ð®ðµ: ððµðŸð® ððžð¬ðŽ ðððððð€© ??????? - owner [ðŠ] @thebestNesskisser -admin [ð€ð€] @Trexioo â admin [ðª] ððððððððððð ð€©ÐÑÑÑ - ÑÑЎа ðпÑеЎлПжка - ÑÑЎа Ðп пПÑÑ - ÑÑЎа â¡ïž@daily_Sendo_Shutoâ¬ ïž â¿â¿â¿â¿â¿â¿â¿â¿â¿â¿â¿â¿
ð€ait a ðeconð ! ããã ã̶﹫ðŠð¶ðð©â¯sð ð±ð®ð¶ð¹ð + ð°ð³ ОÑОÑе ÐºÑ Ð¿ÐŸ пÑелеÑÑМÑÐŒ кайМеÑÑÐ°ÐŒïŒ ãããã ã ãã ð¡hen ðelcome .á
ðð¥¹ðð¥¹ððŸð ðŒðððŸ ðð . . ð ðŒ ðð€©ð€©ðªœð¥¹ï¹«â¬ðð ððððððŠðð ð ðŒ пПМÑавОлÑÑ Ð¿ÐµÐ¹ÑОМг баММОÑÐ°Ñ ð€©ð€©ð€©ð€©ð€©ð€©ÐžÐ· blue lockâ𥹠ð ð€©ðŒ ðð ðððŠðð ОÑеÑе ЎейлОк пП МОЌâïž ððð€©ð» ðµð©ðŠð¯ â ððððððððð
á á ð€©â ðððððððððâŒïž ããð¥¹ð¥¹ ðÊ ÊáŽÉ¯áŽÊ áŽáŽ©áŽŠáŽÐœÐžÉÊáŽððð€© ðáŽáŽ©ÐžáŽÐžÑáŽáŽáŽÐž ð€© ÐœÐžÉáŽÐžÐ¹ ÑᎩáŽÊáŽÐœÑ ðð€©ð€©áŽ©ÑáŽáŽÏ¶ sððð...ð€ ðð â€ïž ðŸððð ðð ðð¥¹ðð®ðªðšðð ð¿ððð¡ð®ð€©ðð
â¯× â¯×ðð ÖŽ ðœð®ð ðšð¬ðð ð¢ð ââ⢠ð¥ âÖŽ ïž¶ пПМÑавОлÑÑ Ð¿ÐµÐ¹ÑОМг â ð â Ñ ÑÑгП à ОÑагО Оз ð»ð ð ð ïžµ ïžµ â ððð ÖŽ ОÑеÑÑ ÐºÐŸÐœÑÐµÐœÑ Ð¿ÐŸ МОЌ ? ê± â¡ïž ðððð ðð ðºðŒðŸ ð¿ðð ððð ! ÖŽ ð€©ð€© Öº
âºïžð ð ðаЌ МÑð¶Ð²ÑÑÑÑð ð¥¹ð²ðйМеÑð¬Ñ? ð§ÐŸÑОÑе â¬ÐžÐŽÐµÑÑ ð ЌМðⲠП ð®Ð¶ÐµÐŽÐœÐµÐ²ð£ÑÑ Ð°ÑÏПв?ðŸ â€ïžâºïžð°ÑОÑе пеâŽÐµÐ²ÐŸÐŽÑ and𥹠𥹠Мððв ðП МОá??ðð
ð€© ð»ðð¶ððð»#seishironagi #art ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€© ð®ððŸððœðŸðð ð©ð¶ððŸ ðð¶ðŸðð.ã» cr on instagramð»boost
custom 52832581171261290393custom 52020223884300575232
Ñ ÐŸÑОÑе пПÑОÑаÑÑ ÑаМÑОкО, заÑОÑПвкО, пеÑепОÑкО, пеÑÐµÐ²ÐŸÐŽÑ Ðž пÑПÑее пÑПÑее пП пеÑÑПМажаЌ О пейÑОМгаЌ Оз аМОЌе/ЌаМгО Blue Lock? ð€©ð€© ð«¥ð«¥ð«¥then... follow meâŒïž ð€©ð€©ð€©c'mon dude! i love so much my subscribers and i always keep in touch with them through communicationð€
ð€© ð»ðð¶ððð»#seishironagi #art ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€©ð€© ð®ððŸððœðŸðð ð©ð¶ððŸ ðð¶ðŸðð.ã» cr on instagramð»boost
custom 52832581171261290393custom 52020223884300575231
Showing the 12 most recent of 17 posts we hold for @seishironagidaily. 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
Republishes
Channels on the register whose posts this channel has forwarded.
@pricewels · 162 postsÝððŒððððððŽð¿ðŒðððâ âºàŽŠ
@KainessDaiIy · 7841 postððð®ðªðšðð ðððð¡ð®ðŽðð//
@RyusaeDaiIy · 3131 postã¢â¡âRin IáŽáŽshi dáŽily °á¯
@blUeLOCKKKKKD · 1071 postððð¢ð¥ð²_ððð§ððš_ðð¡ð®ððš
@daily_Sendo_Shuto · 1841 postð Kainess Daily/Cf âžâž
@kainessbllk · 2201 postпÑÐ°Ð¹Ñ Ð³Ð°Ð·ÐµÑМОÑÑ
@price_gazeta · 151 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
@bestNessirI · 1592 postsÑÑÑÑ
@aryosso · 651 postã¢â¡âRin IáŽáŽshi dáŽily °á¯
@blUeLOCKKKKKD · 1071 post﹫ðð§ð¬ð ð¹ð¶ðŸðð ᯬ ðŒð¿
@bnsedailycf · 2741 postððð¢ð¥ð²_ððð§ððš_ðð¡ð®ððš
@daily_Sendo_Shuto · 1841 postâ¡ã ðð ð¢ð¬ â ð¹ð¶ðŸðð ðŒð¿
@dailyhugosagi · 2871 postÝððŒððððððŽð¿ðŒðððâ âºàŽŠ
@KainessDaiIy · 7841 postððð®ðªðšðð ðððð¡ð®ðŽðð//
@RyusaeDaiIy · 3131 postXh
@Trexioo · 11 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channelâs posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@seishironagidaily named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleâs history â see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today â not that anything âdiedâ. How this is measured.
Never seen alive
References a handle that is not a live channel â we have no record it ever was one.
named in 1 post, 27 August 2026 â 27 August 2026
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 25 September 2026 â this entry's latest reading, not the date you are reading this.
âð®ððŸððœðŸðð ð©ð¶ððŸ ðð¶ðŸðð.ã»â (@seishironagidaily), 20 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/seishironagidaily.
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.