Telegram RegisterThe public register of Telegram

Channel

🔒 | joonaemi .ᐟ

@joonaemi

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

305subscribers

-1 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-1002920464334
TypeChannel
Username@joonaemi
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/joonaemi

Growth

305306305.57 Aug 2026, 13:32 — 306 subscribers8 Aug 2026, 07:49 — 306 subscribers8 Aug 2026, 12:42 — 305 subscribers7 Aug 2026, 13:328 Aug 2026, 12:42
3 measurements taken within a single day, 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 305–306 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 12:42305-1
8 Aug 2026, 07:49306no change
7 Aug 2026, 13:32306first reading

Engagement

11 posts held, back to 7 December 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 11 posts for this entry, the most recent from 10 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

619 reactions across 9 posts, in 12 distinct kinds. The most used accounts for 28.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
17828.8%
💔10617.1%
😭6510.5%
💘518.24%
❤‍🔥467.43%
custom 5411248142546921704447.11%
custom 5226745860863324582386.14%
365.82%
🕊315.01%
💋121.94%
🔥91.45%
custom 523789539410025625630.485%

Custom emoji. 3 of the rows above are 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 areTelegram’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 9 of the 11 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 619reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 7 December 2025 to 10 April 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

10 Apr 2026, 13:55 UTC339 views49 reactionsread 8 August 2026
Forwarded from @loveformaknaezPhoto

друзья, я не очень хотела поднимать эту тему, но, кажется, это необходимо. со вчерашнего дня в твиттере виллэнсвиля активно обсуждается аккаунт с хейтом джуёна ( @ 2gunanijiyo ). в основном хейт связан с неактивностью джуёна в баббл/фанс, отсутствием соло-эфиров, но помимо этого джуёна критикуют за отношение к фанатам, поведение на сцене и даже вокал. а ещё обвиняют в других неприятных вещах БЕЗ каких-либо доказател

💔39🕊4custom 541124814254692170442

16 Feb 2026, 15:45 UTC821 views106 reactionsread 8 August 2026
Photo

конец.🔒 наверное это было очевидно, да?… я пыталась собрать все свои силы и вернуться, но так и не смогла. мне очень тяжело отпускать своего ребенка, которого я растила так долго. кстати, 15 февраля май пинк принц было бы два года, если бы я не переехала на новый канал. я так благодарна всем, кто поддерживал меня на протяжении этих двух лет. без вас и вашей любви этот канал быстро бы закрылся. если бы не этот канал,

💔58😭316🕊5custom 52267458608633245823💋2❤‍🔥1

15 Jan 2026, 13:57 UTC919 views66 reactionsread 8 August 2026
Photo

( 260114 ) ☆ twt XH update || квак джисок, давай будем здоровы в этом году!! аа? и счастливы!! аааа? давай повеселимся, а??

34🕊10❤‍🔥7🔥6custom 522674586086332458232💋2custom 52378953941002562562

14 Jan 2026, 09:29 UTC867 views77 reactionsread 8 August 2026
Photo

▫️ ▫️▫️ happy jiseok day! ❤️ ▫️🐺: давайте смело и уверенно двигаться вперед в 2026 году! с днем рождения, а что касается подарка... я подарю его тебе где-то лет через 15 ♡ мой бро~ чу~♡

💘2623custom 5411248142546921704145❤‍🔥3💋2custom 52267458608633245822🔥1

13 Jan 2026, 10:19 UTC510 views49 reactionsread 8 August 2026
Forwarded from @junhanskkitoPhoto

GOOD FUCKING MORNING. джуп выложили пост, где сообщили о том, что эктиджи в последнее время очень активно преследуют сасэны ㅡ они фотографируют их в их личное время, преследуют и несколько раз пытались попасть в их общежития. последняя попытка взлома общежитие произошла совсем недавно и компания подала в полицию. джуп написали о том, что намерены бороться с сасэнами и дальше ㅡ заявлениями в полицию, добавлением

😭34💔9🕊5custom 52267458608633245821

31 Dec 2025, 21:17 UTC657 views66 reactionsread 8 August 2026

всех, у кого уже новый год, с праздником!!!❤️‍🩹❤️‍🩹❤️‍🩹

custom 541124814254692170425❤‍🔥1813custom 52267458608633245823🔥21💋1💘1

31 Dec 2025, 13:48 UTC684 views82 reactionsread 8 August 2026
Photo

друзья, с наступающим вас новым годом! спасибо вам всем большое, что остаетесь со мной, несмотря на все мои ресты, задержки в постах и даже переезд. спасибо, что провели со мной этот год. ❤️‍🩹

33💘22❤‍🔥13custom 52267458608633245827🕊32💋1custom 54112481425469217041

7 Dec 2025, 01:42 UTC879 views75 reactionsread 8 August 2026
Photo

джуен обновил фото профиля в баббл😭😭😭😭

4116custom 522674586086332458212💋3❤‍🔥1💘1🕊1

7 Dec 2025, 01:37 UTC781 views49 reactionsread 8 August 2026
Photo

фотографии от остальных мемберов((((🥺🥺🥺

2610custom 52267458608633245827❤‍🔥3💋1💘1🕊1

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

Citation-graph rank

Citation-graph rank — 547,517 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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 1 registered channel — 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.

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

“🔒 | joonaemi .ᐟ” (@joonaemi), 305 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/joonaemi.

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.