Telegram RegisterThe public register of Telegram
Telegram profile photo for 21:21

Channel

21:21

@jekatti

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

252subscribers

-17 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001829251654
TypeChannel
Username@jekatti
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 7 October 2026
On Telegramt.me/jekatti

Topic

Memes & entertainment — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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.

Growth

252269260.57 August 2026 — 269 subscribers8 August 2026 — 269 subscribers14 August 2026 — 267 subscribers20 August 2026 — 266 subscribers4 September 2026 — 264 subscribers11 September 2026 — 260 subscribers25 September 2026 — 256 subscribers7 October 2026 — 252 subscribers7 August 20267 October 2026
8 measurements spanning 61 days, net -17. 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 249–272 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Oct 2026, 03:55252-4
25 Sept 2026, 06:17256-4
11 Sept 2026, 22:39260-4
4 Sept 2026, 11:39264-2
20 Aug 2026, 20:33266-1
14 Aug 2026, 01:56267-2
8 Aug 2026, 08:49269no change
7 Aug 2026, 11:43269first reading

Engagement

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

What this channel posts

Video runtime
27s
Average length
27s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

144 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 37.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53146764342565446925437.5%
custom 54045929232180407803725.7%
custom 53326875857707534963524.3%
custom 54586042286143200551812.5%

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 7 of the 7 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 144 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 11 June 2026 to 26 July 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.

Recent posts

26 Jul 2026, 06:55 UTC47 views12 reactionsread 8 August 2026
Photo

if they say why? why? tell them that it's human nature 🍏🪨

custom 53146764342565446926custom 54045929232180407804custom 54586042286143200552

22 Jul 2026, 08:10 UTC89 views18 reactionsread 8 August 2026
Photo

стареть тяжело 😈

custom 531467643425654469211custom 54045929232180407804custom 53326875857707534963

5 Jul 2026, 04:40 UTC124 views17 reactionsread 8 August 2026
Photo

office siren 🖤🤩🤩

custom 53146764342565446927custom 53326875857707534964custom 54586042286143200554custom 54045929232180407802

25 Jun 2026, 15:39 UTC150 views27 reactionsread 8 August 2026
Photo

🤍🌸знаешь, ты самый яркий день в году самое яркое воспоминание 🤍

custom 531467643425654469213custom 54045929232180407807custom 53326875857707534966custom 54586042286143200551

18 Jun 2026, 12:13 UTC143 views26 reactionsread 8 August 2026
Photo

coffee is made for rainy weather ☕️🥐

custom 540459292321804078012custom 53326875857707534966custom 53146764342565446925custom 54586042286143200553

16 Jun 2026, 14:07 UTC134 views26 reactionsread 8 August 2026
Photo

культурно посвящаюсь в этой жизни у меня травма из за алексея серова, ибо он творил на сцене самый настоящий треш (на самом деле претензий нет, крутой чувак, и без комплексов ! !) а на лсп я чуть не расшибла себе голову, ибо ОЧЕНЬ хотелось поближе видеть (или хотя бы просто видеть) олега 🤩 из бонусов у меня наконец то есть трек лист с концерта 👼 ну и хлопай ресницами и взлетай

custom 533268758577075349611custom 54045929232180407807custom 54586042286143200555custom 53146764342565446923

11 Jun 2026, 13:00 UTC131 views18 reactionsread 8 August 2026

моя секретарша 😺

custom 53146764342565446929custom 53326875857707534965custom 54586042286143200553custom 54045929232180407801

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

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

“21:21” (@jekatti), 252 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/jekatti.

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.