🌹🌹🌹🌹🌹🌹

Channel
Korean_Telecast
@korean_telecast1
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,815subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001799578041 |
|---|---|
| Type | Channel |
| Username | @korean_telecast1 |
| Created | 1 September 2022 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/korean_telecast1 |
Topic
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 08:20 | 2,815 | -9 |
| 5 Oct 2026, 07:42 | 2,824 | -6 |
| 26 Sept 2026, 22:15 | 2,830 | +7 |
| 17 Sept 2026, 20:38 | 2,823 | +6 |
| 13 Sept 2026, 11:16 | 2,817 | -3 |
| 9 Sept 2026, 12:41 | 2,820 | -3 |
| 4 Sept 2026, 13:20 | 2,823 | +10 |
| 1 Sept 2026, 08:56 | 2,813 | +6 |
| 29 Aug 2026, 11:08 | 2,807 | -3 |
| 26 Aug 2026, 18:08 | 2,810 | +6 |
| 24 Aug 2026, 01:04 | 2,804 | -5 |
| 20 Aug 2026, 15:36 | 2,809 | -2 |
| 17 Aug 2026, 21:46 | 2,811 | +3 |
| 14 Aug 2026, 15:34 | 2,808 | -2 |
| 8 Aug 2026, 05:59 | 2,810 | -2 |
| 7 Aug 2026, 16:47 | 2,812 | first reading |
Engagement
6 posts held, back to 1 September 2022 — 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 6 posts for this entry, the most recent from 4 June 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://t.me/+9DRaisf9_F9hNGQ8 🔺لینک عضویت کانال Korean Telecast🔺
دوستان برای اینکه کانال محافظ حذف نشه مجبورم هر ۱-۲ماه یه پیام اینجا بفرستم
🔺به دلیل رفت و آمد زیاد ، اگر از کانال اصلی لفت بدید بن میشید. در کانال محافظ جهت احتیاط عضو باشید.
🌍سلام عزیزان؛ به دنیای ما خوش آمدین. درب ورود کانال اصلی 🌈⭐️🦋 برای عضویت روی لینک بزنید. 🥳🤩 بفرمایین تو دم در بده! 🤭🚪 ☔️☔️☔️☔️☔️💜🇯🇴🇮🇳 💜☔️☔️☔️☔️☔️☔️ لـیـنـک عـضـویـت https://t.me/+LutP6vCsWsw4M2E0 ☔️☔️☔️☔️☔️💜🇯🇴🇮🇳💜☔️☔️☔️☔️☔️☔️
Channel created
Showing the 6 most recent of 6 posts we hold for @korean_telecast1. 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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Korean_Telecast” (@korean_telecast1), 2,815 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/korean_telecast1.
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.