Telegram RegisterThe public register of Telegram
Telegram profile photo for KаtanaAgency

Channel

KаtanaAgency

@k4tanaAgency

On this record: Growth · Engagement · Posts · Citations · Cite this entry

64subscribers

-1 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003607112333
TypeChannel
Username@k4tanaAgency
Created1 January 2026 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live17 September 2026
Measurements held3
Confirmed unchanged4 times, most recently 17 September 2026
On Telegramt.me/k4tanaAgency

Growth

646564.58 August 2026 — 65 subscribers10 August 2026 — 65 subscribers23 August 2026 — 64 subscribers8 August 202623 August 2026
3 measurements spanning 15 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 64–65 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 05:0464-1
10 Aug 2026, 02:1765no change
8 Aug 2026, 02:5065first reading

Engagement

3 posts held, back to 1 January 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 3 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 Jul 2026, 03:18 UTC81 viewsread 10 August 2026

ВСЕ КАНАЛЫ АГЕНСТВА ╋━━ ᯓ китя | dontoffend 1.9k | вп 500+ - @lonely_kotik_666 ᯓ девчонка из Токио 1.8k пдп | вп 800+ - @Lonely_kotik_666 ᯓ viالتها₊˚⊹ ᰔ 1.4k пдп вп - @luvluvlvv ᯓ aesthèria 761 пдп | вп 600+ - @wifexwsw ᯓ clos3 my 3y3s 739 пдп | вп 500+ - @dolllskillll ᯓ вояжев 426 пдп | вп 300+ - @Shidhkxdxz

1 Jan 2026, 21:47 UTC579 viewsread 10 August 2026
Video

----- Katana Agency ----- ⬜⬜⬜⬜ ⬜⬜⬜⬜ ⬜⬜⬜⬜ ⬜ ⬜⬜⬜⬜ ⬜⬜⬜⬜⬜⬜⬜ для того что бы попасть в агентство нужно написать в бота - @KatanaAg3ncybot подписчиков должно быть 800+

Showing the 3 most recent of 3 posts we hold for @k4tanaAgency. 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.

Mentions

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.

Cite this entry

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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“KаtanaAgency” (@k4tanaAgency), 64 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/k4tanaAgency.

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.