27 Jul 2026, 09:51 UTC33 viewsread 15 August 2026
Sticker
Sticker, posted without a caption
Channel
камиширность
@Kamishiro_union
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1004448100170 |
|---|---|
| Type | Channel |
| Username | @Kamishiro_union |
| Created | 27 July 2026 — measured — dated from the channel’s first post |
| First recorded | 15 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Kamishiro_union |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 06:31 | 1 | no change |
| 8 Aug 2026, 10:19 | 1 | first reading |
Engagement
7 posts held, back to 27 July 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2916.7%
- avg views ÷ 1 subscribers
- Avg views / post
- 29.2
- 6 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 7
- of 7 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.
| Window | Rolling 30 days · latest post in window 27 July 2026 |
|---|---|
| Posts held | 7 (27 July 2026 – 27 July 2026) |
| Views total | 175 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Aug 2026, 06:31 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
- Photos
- 3
- Links
- 3
Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
27 Jul 2026, 09:51 UTC33 viewsread 15 August 2026
Photo
ㅤㅤ ㅤㅤㅤ 𝗨𝗡𝗜𝗢𝗡𝗦 #N ㅤㅤ ㅤ• Сᴧᴇдящая Камиширо 𝗙𝗹𝗼𝗼𝗱'𝒂𝒅𝒊 𝗜𝗡𝗙𝗢: @adoi77 𝗟𝗜𝗙𝗘: @adi_flood_life 【𝕻𝗮𝘀֟֟፝𝖘꯭𝟏𝕠𝗇】 𝗜𝗡𝗙𝗢: @pass1oninf 𝗟𝗜𝗙𝗘: @pass1onlif 🌫°.𝙀lus𝔗ve ¦︎◖︎𝘀✗︎𝔠ret𝓼』 𝗜𝗡𝗙𝗢: @ELsec_inf0 𝗟𝗜𝗙𝗘: @ELsec_h0m3 ░⃝ℂ𝚑𝗮✶꯱⊹𝐒𝗖𝐫𝕚ᑭᎿֺ𓈒⁅ 𝗜𝗡𝗙𝗢: @CS_inf0 𝗟𝗜𝗙𝗘: @CS_lif 𝓘𝓁𝕴𝖓𝖈𝖔𝖌𝖓𝖎𝖙𝖔 𝕽𝖔𝖞𝖆𝖑𝖊. 𝗜𝗡𝗙𝗢: @RI_INF 𝗟𝗜𝗙𝗘: @RI_LFE ── . „ 𝒞ri𝖒veín𝗶𝖘e. ❪ 釲 ❫ 𝗜𝗡𝗙𝗢: @Crimveinise 𝗟𝗜𝗙𝗘: @Home_Crimveinise ㅤ ﹫ 𝓦𝗘𝗜𝓝︩︪𝗘𝗡 𝗧ꪮ`𝗧𝗘𝗡. ᛝ 𝗜𝗡𝗙𝗢: @Info_WT …
27 Jul 2026, 09:50 UTC30 viewsread 15 August 2026
Sticker
Sticker, posted without a caption
27 Jul 2026, 09:50 UTC29 viewsread 15 August 2026
Photo
ㅤㅤ ㅤㅤㅤ 𝗨𝗡𝗜𝗢𝗡𝗦 #М ㅤㅤ ㅤ• Сᴧᴇдящая Камиширо ʜᴀᴠᴇɴ ᴏғ ᴛʜᴇ ᴍᴏᴏɴ 𝗜𝗡𝗙𝗢: @hvm_info 𝗟𝗜𝗙𝗘: @hvm_life ㅤ⎯ 𝐄𝗌𝖼𝖺𝗉𝗂𝗌𝗆 . ⧽ ♟ 𝗜𝗡𝗙𝗢: @ESC4P1SM_INF 𝗟𝗜𝗙𝗘: @ESC4P1SM_LIF ‹‹◞𝐓𝐄𝐓𝐒𝐔⸝⸝𝐆𝐀𝐊𝐔๋࣭ ⭑›› 𝗜𝗡𝗙𝗢: @TETSU_info 𝗟𝗜𝗙𝗘: @TETSU_life
27 Jul 2026, 09:50 UTC25 viewsread 15 August 2026
🌺
27 Jul 2026, 09:49 UTC25 viewsread 15 August 2026
Photo
❌❌❌❌ navigation . 🍭 repost time - среда ❌❌ @shH1r0bot #M - Участвуют в чистках #N - не участвуют в чистках ❌Union list #M Union list #N
27 Jul 2026, 09:49 UTCviews —
Channel created
Showing the 7 most recent of 7 posts we hold for @Kamishiro_union. 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 — 248,909 of 1,480,688entries 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.
Names
Channels on the register whose handles appear in this channel's posts.
: 𝟒𝗗𝟏..`𝐥𝐢𝐟𝐞**
@adi_flood_life · 1891 post𝓐𝘥𝘪 • 𝗜𝗡𝗙𝗢 • (+14) . . .
@adoi77 · 2871 post᎒ 𝟲𝟲̶ٞ𝟲ׁ.« 𝐀̸𝗦ִؗٺ𝐓̴𝐑ׄ͠𝐄͟𝗔̴̷
@AstreaINF · 9761 post᎒ 𝟲𝟲̶ٞ𝟲ׁ.« 𝐀̸𝗦ִؗٺ𝐓̴𝐑ׄ͠𝐄͟𝗔̴̷. ؘؔ𝐋ۘ𝕴ۨ𝐅ᰬ𝕰۟
@AstreaLIFE · 5961 postׄ ׁ ִ ◌⃘۫⟡ ֪ 𝐂𝐋𝕰𝐌𝐀𝐓𝐈𝐒 ˳ ִ ۫ ᯏֵ۫ 𝖎𝖓𝖋𝖔
@CL3MAT1S_1NF0 · 2581 postׄ ׁ ִ ◌⃘۫⟡ ֪ 𝐂𝐋𝕰𝐌𝐀𝐓𝐈𝐒 ˳ ִ ۫ ᯏֵ۫ 𝖑𝖎𝖋𝖊
@CL3MAT1S_L1FE · 1961 post── . „ 𝒞ri𝖒v͟͟e͟͟ín𝗶𝖘e. ❪ 釲 ❫
@Crimveinise · 2011 post𝕴𝒏𝗳𝑜 𔗂꯭ֺ 𝕮𝐡ɑׁׅ𔓕ִꑄ ִ𝆹𝅥 𓈒𝐒𝕔𝖗ꪱׁׁׁׅׅׅᏢɨ ۫𝆬⃝ ִֺ𝅄𝆹ִֺ𝅥ৎ
@CS_inf0 · 3051 post𝕷𝒊𝗳𝑒 ░⃝ℂ𝚑𝗮✶꯱⊹𝐒𝗖𝐫𝕚ᑭᎿֺ𓈒⁅
@CS_lif · 2231 postᰔ.𝙀lu͟͟s͟͟𝔗ve ¦︎◖︎𝘀✗︎𝔠ret𝓼 ʚɞ 𝙃𝟎mℰ
@ELsec_h0m3 · 2431 postღ.𝙀lu͟͟s͟͟𝔗ve ¦︎◖︎𝘀✗︎𝔠ret𝓼 ʚɞ 𝐼𝗡f𝒪
@ELsec_inf0 · 3191 postㅤ⎯ 𝐄𝗌𝖼𝖺𝗉𝗂𝗌𝗆 . ⧽ ♟️
@ESC4P1SM_INF · 4661 post𝗅𝗂𝐟𝖾 𝄒ᅠ⎯ 𝐄𝗌𝖼𝖺𝗉𝗂𝗌𝗆 . ⧽ ♟️
@ESC4P1SM_LIF · 2951 post── . 𝗵𝗼𝗺𝗲 „ 𝒞ri𝖒v͟͟e͟͟ín𝗶𝖘e. ❪ 釲 ❫
@Home_Crimveinise · 1531 postʜᴀᴠᴇɴ ᴏғ ᴛʜᴇ ᴍᴏᴏɴᶫᶦᶠᵉ
@hvm_life · 4291 postㅤ ﹫ 𝗜𝗡`𝗙𝗢 #𝓦𝗧. ᛝㅤ
@Info_WT · 5811 post◌𓈒 ׁ⑅ 𓏪̣̣ᣟ݂ ᶦᶰᶠᵒ 𐌑ᥲᧁ𝔦ᥴꪖꪶ 𝔉ᥣꪮᥕꫀ𝔯𝔰 . . .
@MF1nf · 921 post◌𓈒 ׁ⑅ 𓏪ᣟ݂ ᶫᶦᶠᵉ 𐌑ᥲᧁ𝔦ᥴꪖꪶ 𝔉ᥣꪮᥕꫀ𝔯𝔰 . . .
@MF_l1f · 771 post𝐈𝒏𝖥𝕺【𝕻𝗮𝘀֟֟፝𝖘꯭𝟏𝕠𝗇】
@pass1oninf · 1601 post𝕷𝐈𝒇𝖤【𝕻𝗮𝘀֟֟፝𝖘꯭𝟏𝕠𝗇】
@pass1onlif · 1561 post𝓘𝓁𝕴𝖓𝖈𝖔𝖌𝖓𝖎𝖙𝖔 𝕽𝖔𝖞𝖆𝖑𝖊. 𝑳𝑰𝑭𝑬
@RI_LFE · 3381 post(. 𝗍𝖾𝘁𝗌υ𝗀α𝗄.μㅤㅤ𝗶𝗻𝗳𝗼
@TETSU_info · 3191 post‹‹◞𝐓𝐄𝐓𝐒𝐔⸝⸝𝐆𝐀𝐊𝐔๋࣭ ›› 𝐋𝐈𝐅𝐄
@TETSU_life · 2131 postㅤ ﹫ 𝗟𝗜`𝗙𝗘 #𝓦𝗧. ᛝ
@WT_Life · 2901 post
@adi_flood_life · 1891 post𝓐𝘥𝘪 • 𝗜𝗡𝗙𝗢 • (+14) . . .
@adoi77 · 2871 post᎒ 𝟲𝟲̶ٞ𝟲ׁ.« 𝐀̸𝗦ִؗٺ𝐓̴𝐑ׄ͠𝐄͟𝗔̴̷
@AstreaINF · 9761 post᎒ 𝟲𝟲̶ٞ𝟲ׁ.« 𝐀̸𝗦ִؗٺ𝐓̴𝐑ׄ͠𝐄͟𝗔̴̷. ؘؔ𝐋ۘ𝕴ۨ𝐅ᰬ𝕰۟
@AstreaLIFE · 5961 postׄ ׁ ִ ◌⃘۫⟡ ֪ 𝐂𝐋𝕰𝐌𝐀𝐓𝐈𝐒 ˳ ִ ۫ ᯏֵ۫ 𝖎𝖓𝖋𝖔
@CL3MAT1S_1NF0 · 2581 postׄ ׁ ִ ◌⃘۫⟡ ֪ 𝐂𝐋𝕰𝐌𝐀𝐓𝐈𝐒 ˳ ִ ۫ ᯏֵ۫ 𝖑𝖎𝖋𝖊
@CL3MAT1S_L1FE · 1961 post── . „ 𝒞ri𝖒v͟͟e͟͟ín𝗶𝖘e. ❪ 釲 ❫
@Crimveinise · 2011 post𝕴𝒏𝗳𝑜 𔗂꯭ֺ 𝕮𝐡ɑׁׅ𔓕ִꑄ ִ𝆹𝅥 𓈒𝐒𝕔𝖗ꪱׁׁׁׅׅׅᏢɨ ۫𝆬⃝ ִֺ𝅄𝆹ִֺ𝅥ৎ
@CS_inf0 · 3051 post𝕷𝒊𝗳𝑒 ░⃝ℂ𝚑𝗮✶꯱⊹𝐒𝗖𝐫𝕚ᑭᎿֺ𓈒⁅
@CS_lif · 2231 postᰔ.𝙀lu͟͟s͟͟𝔗ve ¦︎◖︎𝘀✗︎𝔠ret𝓼 ʚɞ 𝙃𝟎mℰ
@ELsec_h0m3 · 2431 postღ.𝙀lu͟͟s͟͟𝔗ve ¦︎◖︎𝘀✗︎𝔠ret𝓼 ʚɞ 𝐼𝗡f𝒪
@ELsec_inf0 · 3191 postㅤ⎯ 𝐄𝗌𝖼𝖺𝗉𝗂𝗌𝗆 . ⧽ ♟️
@ESC4P1SM_INF · 4661 post𝗅𝗂𝐟𝖾 𝄒ᅠ⎯ 𝐄𝗌𝖼𝖺𝗉𝗂𝗌𝗆 . ⧽ ♟️
@ESC4P1SM_LIF · 2951 post── . 𝗵𝗼𝗺𝗲 „ 𝒞ri𝖒v͟͟e͟͟ín𝗶𝖘e. ❪ 釲 ❫
@Home_Crimveinise · 1531 postʜᴀᴠᴇɴ ᴏғ ᴛʜᴇ ᴍᴏᴏɴᶫᶦᶠᵉ
@hvm_life · 4291 postㅤ ﹫ 𝗜𝗡`𝗙𝗢 #𝓦𝗧. ᛝㅤ
@Info_WT · 5811 post◌𓈒 ׁ⑅ 𓏪̣̣ᣟ݂ ᶦᶰᶠᵒ 𐌑ᥲᧁ𝔦ᥴꪖꪶ 𝔉ᥣꪮᥕꫀ𝔯𝔰 . . .
@MF1nf · 921 post◌𓈒 ׁ⑅ 𓏪ᣟ݂ ᶫᶦᶠᵉ 𐌑ᥲᧁ𝔦ᥴꪖꪶ 𝔉ᥣꪮᥕꫀ𝔯𝔰 . . .
@MF_l1f · 771 post𝐈𝒏𝖥𝕺【𝕻𝗮𝘀֟֟፝𝖘꯭𝟏𝕠𝗇】
@pass1oninf · 1601 post𝕷𝐈𝒇𝖤【𝕻𝗮𝘀֟֟፝𝖘꯭𝟏𝕠𝗇】
@pass1onlif · 1561 post𝓘𝓁𝕴𝖓𝖈𝖔𝖌𝖓𝖎𝖙𝖔 𝕽𝖔𝖞𝖆𝖑𝖊. 𝑳𝑰𝑭𝑬
@RI_LFE · 3381 post(. 𝗍𝖾𝘁𝗌υ𝗀α𝗄.μㅤㅤ𝗶𝗻𝗳𝗼
@TETSU_info · 3191 post‹‹◞𝐓𝐄𝐓𝐒𝐔⸝⸝𝐆𝐀𝐊𝐔๋࣭ ›› 𝐋𝐈𝐅𝐄
@TETSU_life · 2131 postㅤ ﹫ 𝗟𝗜`𝗙𝗘 #𝓦𝗧. ᛝ
@WT_Life · 2901 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“камиширность” (@Kamishiro_union), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/Kamishiro_union.
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.