Теперь я буду находится в сообществе телеграм каналов «Swag» 👀
custom 52247130313672820986custom 53574286675699482005custom 54429904075856471622

Channel
@nazenkakakawai
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
12subscribers
+3 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003967892877 |
|---|---|
| Type | Channel |
| Username | @nazenkakakawai |
| Created | 1 August 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/nazenkakakawai |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 13:20 | 12 | +1 |
| 4 Sept 2026, 08:57 | 11 | +1 |
| 28 Aug 2026, 00:13 | 10 | +1 |
| 12 Aug 2026, 11:48 | 9 | no change |
| 11 Aug 2026, 20:00 | 9 | first reading |
5 posts held, back to 1 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 5 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
32 reactions across 3 posts, in 7 distinct kinds. The most used accounts for 21.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5355036456685422193 | 7 | 21.9% | |
| custom 5357428667569948200 | 7 | 21.9% | |
| custom 5224713031367282098 | 6 | 18.8% | |
| custom 5436109324516607541 | 4 | 12.5% | |
| custom 5357584845465730934 | 3 | 9.38% | |
| custom 5424976210939628139 | 3 | 9.38% | |
| custom 5442990407585647162 | 2 | 6.25% |
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 3 of the 5 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 1 August 2026 to 11 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.
Теперь я буду находится в сообществе телеграм каналов «Swag» 👀
custom 52247130313672820986custom 53574286675699482005custom 54429904075856471622
Posted without readable text
Сегодня я посетил очень красивый костел, который находится неподалёку от Лиды в деревне «Белогруда». Бывая в храме, не телом только бывай в нем, а более духом. Встань, где потише, и, видя умом Господа перед собою, изливай перед Ним свою душу
custom 53550364566854221937custom 53575848454657309343custom 54361093245166075412
🫰Information about me: 😁Пиривет я nazen, Сентябрь, Дева (18.09) В данном телеграм-канале будет представлена моя жизнь «за кадром». Сюда буду постить кружочки, голосовые и фото разного типа. Буду рад каждому новому подписчику 👼 instagram | tiktok | contact with me | boost
custom 54249762109396281393custom 53574286675699482002custom 54361093245166075412
Channel created
Showing the 5 most recent of 5 posts we hold for @nazenkakakawai. 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.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Нейзен” (@nazenkakakawai), 12 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/nazenkakakawai.
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.