Channel
@YunjinResident
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,072subscribers
-66 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001766736339 |
|---|---|
| Type | Channel |
| Username | @YunjinResident |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/YunjinResident |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 19 Sept 2026, 16:38 | 1,072 | -7 |
| 14 Sept 2026, 18:20 | 1,079 | -6 |
| 11 Sept 2026, 08:20 | 1,085 | -6 |
| 7 Sept 2026, 00:00 | 1,091 | -6 |
| 2 Sept 2026, 01:52 | 1,097 | -2 |
| 29 Aug 2026, 23:14 | 1,099 | -3 |
| 27 Aug 2026, 01:24 | 1,102 | -3 |
| 24 Aug 2026, 01:55 | 1,105 | -9 |
| 20 Aug 2026, 05:06 | 1,114 | -4 |
| 16 Aug 2026, 21:28 | 1,118 | -8 |
| 13 Aug 2026, 23:14 | 1,126 | -6 |
| 11 Aug 2026, 02:21 | 1,132 | -5 |
| 7 Aug 2026, 19:05 | 1,137 | -1 |
| 7 Aug 2026, 02:03 | 1,138 | first reading |
18 posts held, back to 27 October 2023 — 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 18 posts for this entry, the most recent from 21 July 2026. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 20 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
kgn
kgn
Hi yun, pake twb comeback ssera yukkk
#LeSserafimBurningHot
ㅤㅤㅤㅤㅤ ㅤㅤㅤㅤ 𝙄𝙉𝙃𝙀𝙍𝙀𝙉𝙏 𝘾𝙊𝙐𝙍𝘼𝙂𝙀 ㅤㅤ 𝘼𝙉𝘿 𝙐𝙉𝙍𝙄𝙑𝘼𝙇𝙇𝙀𝘿 𝙎𝙏𝙍𝙄𝘿𝙀. ㅤㅤㅤㅤ 🖤🖤🖤🔯🖤🌧️🌧️ ㅤㅤㅤ𝐑𝐨𝐚𝐫 𝐨𝐟 𝐢𝐦𝐩𝐞𝐭𝐮𝐬𝐞𝐬 𝐫𝐞𝐯𝐞𝐫𝐛𝐞𝐫𝐚𝐭𝐞𝐝 ㅤㅤㅤ𝐭𝐚𝐧𝐭𝐚𝐦𝐨𝐮𝐧𝐭 𝐭𝐨 𝐚𝐧 𝐢𝐫𝐫𝐞𝐟𝐮𝐭𝐚𝐛𝐥𝐞 ㅤㅤㅤ𝐦𝐚𝐧𝐝𝐚𝐭𝐞 𝐞𝐪𝐮𝐚𝐥𝐥𝐲 𝐩𝐮𝐥𝐯𝐞𝐫𝐮𝐥𝐞𝐧𝐜𝐞 ㅤㅤㅤ𝐮𝐩𝐡𝐞𝐚𝐯𝐚𝐥 𝐟𝐫𝐨𝐥𝐢𝐜𝐤𝐞𝐝 𝐨𝐫𝐛𝐢𝐭𝐢𝐧𝐠 𝐭𝐡𝐞 ㅤㅤㅤ𝐨𝐜𝐜𝐮𝐩𝐚𝐧𝐜𝐲 𝐨𝐟 𝐩𝐞𝐫𝐭𝐢𝐧𝐞𝐧𝐭 𝐭𝐨 𝐭𝐡𝐞𝐦. ㅤㅤ 𝐅𝐞𝐫𝐯𝐞𝐧𝐜𝐲 𝐚𝐢𝐦𝐢𝐧𝐠 𝐟𝐨𝐫 𝐚 𝐠𝐨𝐯𝐞𝐫𝐧𝐚𝐧𝐜𝐞 ㅤㅤ 𝐭𝐡𝐚𝐭 𝐢𝐬 𝐟𝐨𝐫𝐭𝐡𝐜𝐨𝐦𝐢𝐧𝐠 𝐰𝐢𝐭𝐡 #LeSserafimBurningHot. 𝐓𝐫𝐮𝐜𝐮𝐥𝐞𝐧𝐜𝐞 𝐰𝐚𝐬 𝐝𝐞𝐞𝐩-𝐫𝐨𝐨𝐭𝐞𝐝 𝐰𝐢𝐭𝐡𝐢𝐧 𝐭𝐡𝐞 𝐤𝐧𝐨𝐭𝐭𝐞𝐝 𝐜𝐨𝐫𝐝 𝐝𝐞𝐫𝐢𝐯𝐞𝐝 𝐟𝐫𝐨𝐦 𝐭𝐡𝐞 𝐥𝐞𝐬𝐬𝐞𝐧𝐢𝐧𝐠 𝐨𝐟 𝐩
Hi yun
hi yunries
Sticker, posted without a caption
LE SSERAFIM “Smart” OFFICIAL MV https://youtu.be/KNexS61fjus?si=P5uczptcDXdgpQgs
Sticker, posted without a caption
LE SSERAFIM (르세라핌) - 'EASY' OFFICIAL M/V https://youtu.be/bNKXxwOQYB8?si=Spnll9Uquwm7xWHm
Showing the 12 most recent of 18 posts we hold for @YunjinResident. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 48 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Yunjin Resident” (@YunjinResident), 1,072 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/YunjinResident.
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.