лол эра будет 8 числа потому что 9 буду пиздец занят
custom 52111710553175792632
Signed кокчи очма чмо ᵏᵃᶻᵉ ᵒʷⁿ

Channel
@Kaze_Ren
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
648subscribers
+160 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003539978601 |
|---|---|
| Type | Channel |
| Username | @Kaze_Ren |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/Kaze_Ren |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 10:57 | 648 | +27 |
| 27 Aug 2026, 16:24 | 621 | +42 |
| 20 Aug 2026, 09:17 | 579 | +62 |
| 12 Aug 2026, 21:53 | 517 | +26 |
| 6 Aug 2026, 19:55 | 491 | +3 |
| 6 Aug 2026, 18:48 | 488 | no change |
| 6 Aug 2026, 08:26 | 488 | first reading |
20 posts held, back to 31 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 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
33 reactions across 3 posts, in 12 distinct kinds. The most used accounts for 18.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5269423323091078606 | 6 | 18.2% | |
| 🔥 | 4 | 12.1% | |
| custom 5219731483484245668 | 3 | 9.09% | |
| custom 5220123429314776253 | 3 | 9.09% | |
| custom 5271860622542269161 | 3 | 9.09% | |
| custom 5314654216390732636 | 3 | 9.09% | |
| custom 5211171055317579263 | 2 | 6.06% | |
| custom 5240434346837441494 | 2 | 6.06% | |
| custom 5287527877259074557 | 2 | 6.06% | |
| custom 5397816800559800813 | 2 | 6.06% | |
| 💘 | 2 | 6.06% | |
| custom 5240411227028486659 | 1 | 3.03% |
Custom emoji. 10 of the rows above are 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 3 of the 20 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 33 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 July 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.
лол эра будет 8 числа потому что 9 буду пиздец занят
custom 52111710553175792632
Signed кокчи очма чмо ᵏᵃᶻᵉ ᵒʷⁿ
🌸 || 06.08.2026 本日、二つの美しき一族 @Naylin_Flood 🤩 @Kaze_Ren 同盟を結びます ───────────୨ৎ─────────── 🤩 皆様とご縁を結べたことを嬉しく思います。 🤩 この絆が永く続くことを願っております。 「絆は運命を超える」 ━─━─━─━─━─━─━─━─━─━─━─━
Signed кокчи очма чмо ᵏᵃᶻᵉ ᵒʷⁿ
Sticker, posted without a caption
Signed 𝗦ᥲ𝗻f𝗹𑄝ყwᧉׅr 𝕕ׄ᷼ꫀℓִℓִꪱᜒִᨻꭚִ +KR3
ㅤㅤ࣪ ✧🐾 ࣪ 𝙪𝙣𝙞𝙤𝙣𝙨 𝙡𝙞𝙨𝙩 😍カワ 𝆹 ᰍ · . ׁׅ · .࣪ ࣪ · .ׅ ׁ ׅ ࣪ ׁ ׅ . · .ׅ ׁ ׅ ࣪ ׅ . · . @Kontrixxinfo @evening_floods @wonderlight_info @KoreanFlood01 @may_flood_m @nonsensesfloodlife @kellyinfow @m4yb3l1nf0 @liminal_space_info @aFLOW_FLOOD @red_oceanfld @velrixflood @DailixFl00d @ENTERSKY9 @Zefchiik @L1RH0ME @dxfld2 @chaerinfo @arizonssfld @roarverseflood1 @banzye @sHiny_info12 https://t.me/w1neinfoflood @staro…
custom 52201234293147762532custom 52197314834842456681custom 52404343468374414941custom 52718606225422691611
Signed 𝗦ᥲ𝗻f𝗹𑄝ყwᧉׅr 𝕕ׄ᷼ꫀℓִℓִꪱᜒִᨻꭚִ +KR3
Sticker, posted without a caption
Signed 𝗦ᥲ𝗻f𝗹𑄝ყwᧉׅr 𝕕ׄ᷼ꫀℓִℓִꪱᜒִᨻꭚִ +KR3
ㅤㅤ࣪ ✧🐾 ࣪ 𝙘𝙡𝙚𝙖𝙣𝙞𝙣𝙜 😍カワ 𝆹 ᰍ · . ׁׅ · .࣪ ࣪ · .ׅ ׁ ׅ ࣪ ׁ ׅ . · .ׅ ׁ ׅ ࣪ ׅ . · . ࣪ ✧ ׁㅤ𝆹 🥹 недельная норма соо - 100. ࣪ ✧ ׁㅤ𝆹 🥹 чистка проводятся каждое воскресенье в 15:00 по мск. ࣪ ✧ ׁㅤ𝆹 🥹 вы считаетесь нью 3-4 дня. ࣪ ✧ ׁㅤ𝆹 🥹 рест можно брать максимум на месяц, можем выдать на срок больше при серьёзных обстоятельствах. ࣪ ✧ ׁㅤ𝆹 🥹 для рестников нормы нет.
Signed 𝗦ᥲ𝗻f𝗹𑄝ყwᧉׅr 𝕕ׄ᷼ꫀℓִℓִꪱᜒִᨻꭚִ +KR3
Sticker, posted without a caption
Signed 𝗦ᥲ𝗻f𝗹𑄝ყwᧉׅr 𝕕ׄ᷼ꫀℓִℓִꪱᜒִᨻꭚִ +KR3
ㅤㅤ࣪ ✧🐾 ࣪ 𝙞𝙣𝙞𝙩𝙞𝙖𝙡𝙨 😍カワ 𝆹 ᰍ · . ׁׅ · .࣪ ࣪ · .ׅ ׁ ׅ ࣪ ׁ ׅ . · .ׅ ׁ ׅ ࣪ ׅ . · . участникам ставить инициалы не обязательно, но желательно. администрации обязательно! копируются при нажатии ᵏᵃᶻᵉ ᵃᵈᵐ _ ᴷᵃᶻᵉ ᴿᵉᶰ _ ᴷᵃᶻᵉ ᶠᶫᵈ _ ᶫᵒᵛᵉ ᴷᵃᶻᵉ _ ᴷᵃᶻᵉ ᵐᵉᵐᵇᵉʳ _ ᵒᶰᶫʸ ᵏᵃᶻᵉ _ ᵒᵐᵉᵍᵃ ᴷᵃᶻᵉ _ ᵃᶫᵖʰᵃ ᴷᵃᶻᵉ _ ᴷᵃᶻᵉ ᶠᵒʳᵉᵛᵉʳ _ ᴷᵃᶻᵉ ᴿᵉᶰ ᶠᶫᵒᵒᵈ _ ᵏʳ +KR3
Signed 𝗦ᥲ𝗻f𝗹𑄝ყwᧉׅr 𝕕ׄ᷼ꫀℓִℓִꪱᜒִᨻꭚִ +KR3
Sticker, posted without a caption
Signed 𝗦ᥲ𝗻f𝗹𑄝ყwᧉׅr 𝕕ׄ᷼ꫀℓִℓִꪱᜒִᨻꭚִ +KR3
ㅤㅤ࣪ ✧🐾 ࣪ 𝙥𝙖𝙩𝙚𝙣𝙩 😍カワ 𝆹 ᰍ · . ׁׅ · .࣪ ࣪ · .ׅ ׁ ׅ ࣪ ׁ ׅ . · .ׅ ׁ ׅ ࣪ ׅ . · . с 01.07.26 наш флуд берет патент на название «Kaze Ren», «Казэ Рэн», и другие его производные. если влд, администрация либо же участники заметят такое же название, то мы имеем право попросить сменить. просьбы не будут услышаны — будут приняты другие меры. так же патент распространяется на старые и новые оформ…
Signed 𝗦ᥲ𝗻f𝗹𑄝ყwᧉׅr 𝕕ׄ᷼ꫀℓִℓִꪱᜒִᨻꭚִ +KR3
Sticker, posted without a caption
Signed 𝗦ᥲ𝗻f𝗹𑄝ყwᧉׅr 𝕕ׄ᷼ꫀℓִℓִꪱᜒִᨻꭚִ +KR3
ㅤㅤ࣪ ✧🐾 ࣪ 𝙪𝙣𝙞𝙤𝙣𝙨 😍カワ 𝆹 ᰍ · . ׁׅ · .࣪ ࣪ · .ׅ ׁ ׅ ࣪ ׁ ׅ . · .ׅ ׁ ׅ ࣪ ׅ . · . правила для заключения союза:: ➖пост с того кто предложил союз. ➖максимальная подписка 2:2. ➖рпт проводим через день. ➖папки: рп, вз, рп+вз. ➖заключаем союзы с 100+ пдп в инфо. ➖о смене юза следящего/допов всегда сообщать нашему следящему. причины разрыва:: ➖след не подписан на инфо, допы не подписаны спустя неделю. …
Signed 𝗦ᥲ𝗻f𝗹𑄝ყwᧉׅr 𝕕ׄ᷼ꫀℓִℓִꪱᜒִᨻꭚִ +KR3
Showing the 12 most recent of 20 posts we hold for @Kaze_Ren. 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.
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.
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.
Named by 10 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@Kaze_Ren named 2 handles 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“+KR3 ӄִׄαִ𝘇ׄꫀ ꭉׄꫀꬻ” (@Kaze_Ren), 648 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/Kaze_Ren.
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.