Channel
@Kobudo_ninja
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
523subscribers
-10 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001374183399 |
|---|---|
| Type | Channel |
| Username | @Kobudo_ninja |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/Kobudo_ninja |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 14:00 | 523 | -1 |
| 4 Sept 2026, 16:17 | 524 | -4 |
| 27 Aug 2026, 10:57 | 528 | -2 |
| 20 Aug 2026, 02:43 | 530 | -2 |
| 12 Aug 2026, 22:36 | 532 | -1 |
| 6 Aug 2026, 18:31 | 533 | no change |
| 6 Aug 2026, 13:14 | 533 | first reading |
3 posts held, back to 20 October 2022 — 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 3 posts for this entry, the most recent from 7 March 2023. An engagement rate over an empty window would be a number about nothing.
ای آی دو (به ژاپنی: 居合道، Iaido) یک هنر رزمی ژاپنی است که دربرگیرنده جابجاییهای نرم، بیرون آوردن کنترل شده شمشیر از غلاف (سایا)، حمله به حریف ذهنی، پاک کردن تیغه از خون چیبوری و برگرداندن شمشیر به غلاف است. بنا بر سلیقه آموزشدهندگان، برخی از شاگردان (معمولاً شاگردان تازهکار) تمرینات خود را با شمشیر چوبی (بوکِن) و برخی دیگر با شمشیرهای با لبه کند (اییآیتو) شروع میکنند. هنرجویان اییآیدو را با نام اییآیدوکا می…
Signed Hadi忍法
Photo, posted without a caption
Signed Hadi忍法
Photo, posted without a caption
Signed Hadi忍法
Showing the 3 most recent of 3 posts we hold for @Kobudo_ninja. 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“武者の器” (@Kobudo_ninja), 523 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/Kobudo_ninja.
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.