Channel
@kendu
On this record: Topic · Growth · Engagement · Posts · Posts recorded as deleted · Citations · Cite this entry
6,493subscribers
-715 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002099416164 |
|---|---|
| Type | Channel |
| Usernames | @kendu @kenduinu |
| Created | 19 February 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 53 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/kendu |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 52% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 17:19 | 6,493 | -1 |
| 11 Nov 2026, 01:30 | 6,494 | -17 |
| 7 Nov 2026, 17:46 | 6,511 | no change |
| 7 Nov 2026, 17:08 | 6,511 | -11 |
| 4 Nov 2026, 22:55 | 6,522 | no change |
| 4 Nov 2026, 19:21 | 6,522 | -10 |
| 2 Nov 2026, 00:46 | 6,532 | -3 |
| 1 Nov 2026, 13:56 | 6,535 | -15 |
| 30 Oct 2026, 10:16 | 6,550 | -4 |
| 29 Oct 2026, 12:49 | 6,554 | -13 |
| 27 Oct 2026, 13:44 | 6,567 | -2 |
| 26 Oct 2026, 06:01 | 6,569 | -5 |
| 24 Oct 2026, 16:56 | 6,574 | -9 |
| 22 Oct 2026, 23:49 | 6,583 | -8 |
| 21 Oct 2026, 16:04 | 6,591 | -14 |
| 19 Oct 2026, 13:10 | 6,605 | -6 |
| 18 Oct 2026, 13:37 | 6,611 | -15 |
| 16 Oct 2026, 02:56 | 6,626 | -6 |
| 15 Oct 2026, 11:40 | 6,632 | -28 |
| 12 Oct 2026, 17:10 | 6,660 | first reading |
4 posts held, back to 19 February 2024 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 23 pages 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 4 posts for this entry, the most recent from 27 September 2026. An engagement rate over an empty window would be a number about nothing.
🚨 STAY SAFE - IMPORTANT ✅ Admins will never DM you first ✅ Never connect your wallet for verification ✅ No airdrops or token migrations ✅ Always verify through official Kendu channels ✅ Ignore fake support accounts and advertisements If in doubt, ask publicly in the main chat.
🔥 Welcome to the Kendu Ecosystem Builders. Workers. Believers. No gimmicks. No shortcuts. We work. 🛡 Verify below to enter the community.
Kendu Inu (Portal) is being protected by @Safeguard Click below to verify you're human
Channel created
Showing the 4 most recent of 4 posts we hold for @kendu. 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.
We recorded 1 post on @kendu as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Named by 9 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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“Kendu Ecosystem (Portal)” (@kendu), 6,493 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/kendu.
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.