Telegram RegisterThe public register of Telegram
Telegram profile photo for закрыт? elegant

Channel

закрыт? elegant

@jjjkalelegant

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

61subscribers

-28 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-1003712923546
TypeChannel
Username@jjjkalelegant
CreatedBetween 1 February 2026 and 5 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/jjjkalelegant

Growth

6189757 August 2026 — 89 subscribers9 August 2026 — 89 subscribers14 August 2026 — 87 subscribers22 August 2026 — 84 subscribers29 August 2026 — 81 subscribers8 September 2026 — 65 subscribers16 September 2026 — 61 subscribers7 August 202616 September 2026
7 measurements spanning 40 days, net -28. 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 57–93 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 22:0161-4
8 Sept 2026, 21:2165-16
29 Aug 2026, 19:4681-3
22 Aug 2026, 16:3684-3
14 Aug 2026, 20:1587-2
9 Aug 2026, 15:1589no change
7 Aug 2026, 18:3789first reading

Engagement

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

Reaction mix

69 reactions across 8 posts, in 7 distinct kinds. The most used accounts for 27.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52449585751927225511927.5%
custom 51997931930292185901521.7%
custom 52467234846288322271014.5%
custom 5350501563926337794811.6%
custom 5397615010111335631811.6%
custom 527379728772053424557.25%
custom 520640773042788822545.80%

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

Measured over the 19 most recent posts we hold, published 5 July 2026 to 6 August 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

4 Aug 2026, 22:33 UTC11 viewsread 9 August 2026
Forwarded from @MurrMeowTi

4 —> 8О за рп крепко обниму

3 Aug 2026, 21:00 UTC12 viewsread 9 August 2026
Forwarded from @koobitt

3 >>>> 290 13 >>>> 300 за рп обниму

1 Aug 2026, 18:35 UTC26 views3 reactionsread 9 August 2026

я перееду в свой старый канал как буду готов, сейчас нет сил делать что-то новое.

custom 52449585751927225513

28 Jul 2026, 20:03 UTC48 views7 reactionsread 9 August 2026

чё с каналом делать, я к лету хотел 300, а в итоге нихуя.

custom 53505015639263377945custom 52449585751927225512

Signed K1TT3N 98XXD ksn azu krb

26 Jul 2026, 16:57 UTC54 views4 reactionsread 9 August 2026

я удалю этот блядсктц канал когда-нибудь, мне некогда его поднимать с этой дыры.

custom 52449585751927225513custom 51997931930292185901

Signed ksn

20 Jul 2026, 09:36 UTC72 views6 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 52449585751927225515custom 52467234846288322271

17 Jul 2026, 06:01 UTC77 views18 reactionsread 9 August 2026

Posted without readable text

custom 51997931930292185905custom 52737972877205342455custom 53976150101113356315custom 52449585751927225513

14 Jul 2026, 06:27 UTC72 views5 reactionsread 9 August 2026
Photo

Photo, posted without a caption

custom 52064077304278882254custom 52467234846288322271

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

Forward network

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.

Mentions

Named by 2 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.

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

“закрыт? elegant” (@jjjkalelegant), 61 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/jjjkalelegant.

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.