Channel
@KayenProtocol
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
70subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002351911119 |
|---|---|
| Type | Channel |
| Username | @KayenProtocol |
| Description | Wrapped Napoli Official |
| Created | 3 March 2025 — measured — dated from the channel’s first post |
| First recorded | 17 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 1 |
| On Telegram | t.me/KayenProtocol |
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 20:00 | 70 | first reading |
2 posts held, back to 3 March 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 3 March 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 17 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.
3 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 100.0% |
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 1 of the 2 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 3reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 2 most recent posts we hold, published 3 March 2025 to 3 March 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
𝐕𝐄𝐑𝐈𝐅𝐘 𝐘𝐎𝐔 𝐀𝐑𝐄 𝐇𝐔𝐌𝐀𝐍‼️ 𝘛𝘰 𝘨𝘢𝘪𝘯 𝘢𝘤𝘤𝘦𝘴𝘴 𝘢𝘯𝘥 𝘐𝘯 𝘰𝘳𝘥𝘦𝘳 𝘵𝘰 𝘱𝘳𝘦𝘷𝘦𝘯𝘵 𝘵𝘩𝘦 𝘤𝘳𝘦𝘢𝘵𝘪𝘰𝘯 𝘰𝘧 𝘢𝘤𝘤𝘰𝘶𝘯𝘵𝘴 𝘣𝘺 𝘴𝘱𝘢𝘮 𝘣𝘰𝘵𝘴 𝘰𝘳 𝘩𝘶𝘮𝘢𝘯 𝘴𝘱𝘢𝘮𝘮𝘦𝘳𝘴. ⚠️ Note: We don’t save CAPTCHA results. If you are presented with email or SMS verification, we only save a cryptographic hash of your email or phone number which is not permanently associated with the account. Because hash functions are one-way functions, it is impossible to derive your phone numbe…
❤3
Channel created
Showing the 2 most recent of 2 posts we hold for @KayenProtocol. 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.
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.
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.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“WNAP” (@KayenProtocol), 70 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/KayenProtocol.
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.