Telegram RegisterThe public register of Telegram
Telegram profile photo for TOPIK-UZB 공식 채널

Channel

TOPIK-UZB 공식 채널

@topik_kec

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

18,476subscribers

-837 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001427128930
TypeChannel
Username@topik_kec
Description우즈베키스탄 한국어능력시험(TOPIK) 공식 채널(TOPIK-UZB) Официальный канал Центра образования Республики Корея при Посольстве Республики Корея в Узбекистане Сайт: https://topiktashkec.uz
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/topik_kec

Topic

Job listings — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.

Growth

18,38519,43418,909.56 August 2026 — 19,313 subscribers6 August 2026 — 19,313 subscribers7 August 2026 — 19,306 subscribers8 August 2026 — 19,301 subscribers9 August 2026 — 19,298 subscribers10 August 2026 — 19,285 subscribers11 August 2026 — 19,280 subscribers12 August 2026 — 19,284 subscribers13 August 2026 — 19,274 subscribers14 August 2026 — 19,306 subscribers16 August 2026 — 19,434 subscribers17 August 2026 — 19,430 subscribers18 August 2026 — 19,427 subscribers19 August 2026 — 19,386 subscribers20 August 2026 — 19,353 subscribers21 August 2026 — 19,322 subscribers22 August 2026 — 19,296 subscribers24 August 2026 — 19,293 subscribers25 August 2026 — 19,232 subscribers26 August 2026 — 19,225 subscribers27 August 2026 — 19,219 subscribers28 August 2026 — 19,211 subscribers29 August 2026 — 19,199 subscribers30 August 2026 — 19,182 subscribers31 August 2026 — 19,162 subscribers1 September 2026 — 19,135 subscribers2 September 2026 — 19,106 subscribers4 September 2026 — 19,096 subscribers6 September 2026 — 19,008 subscribers10 September 2026 — 18,909 subscribers12 September 2026 — 18,860 subscribers14 September 2026 — 18,818 subscribers15 September 2026 — 18,781 subscribers17 September 2026 — 18,748 subscribers27 September 2026 — 18,596 subscribers4 October 2026 — 18,469 subscribers9 October 2026 — 18,400 subscribers13 October 2026 — 18,385 subscribers14 October 2026 — 18,412 subscribers15 October 2026 — 18,419 subscribers16 October 2026 — 18,435 subscribers17 October 2026 — 18,529 subscribers18 October 2026 — 18,785 subscribers19 October 2026 — 18,775 subscribers21 October 2026 — 18,772 subscribers22 October 2026 — 18,767 subscribers23 October 2026 — 18,757 subscribers24 October 2026 — 18,727 subscribers25 October 2026 — 18,717 subscribers26 October 2026 — 18,700 subscribers27 October 2026 — 18,656 subscribers28 October 2026 — 18,625 subscribers29 October 2026 — 18,596 subscribers30 October 2026 — 18,563 subscribers31 October 2026 — 18,551 subscribers1 November 2026 — 18,523 subscribers2 November 2026 — 18,504 subscribers3 November 2026 — 18,496 subscribers4 November 2026 — 18,476 subscribers18,4766 August 20264 November 2026
59 measurements spanning 90 days, net -837. 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 18,228–19,591 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)SubscribersChange
4 Nov 2026, 18:2618,476-20
3 Nov 2026, 17:3118,496-8
2 Nov 2026, 15:5418,504-19
1 Nov 2026, 13:1018,523-28
31 Oct 2026, 12:4118,551-12
30 Oct 2026, 11:5018,563-33
29 Oct 2026, 09:0618,596-29
28 Oct 2026, 05:2118,625-31
27 Oct 2026, 04:4018,656-44
26 Oct 2026, 03:0718,700-17
25 Oct 2026, 04:5818,717-10
24 Oct 2026, 07:3118,727-30
23 Oct 2026, 05:2818,757-10
22 Oct 2026, 04:0718,767-5
21 Oct 2026, 01:1118,772-3
19 Oct 2026, 21:3618,775-10
18 Oct 2026, 19:4618,785+256
17 Oct 2026, 18:0818,529+94
16 Oct 2026, 19:3718,435+16
15 Oct 2026, 22:0418,419first reading

Engagement

67 posts held, back to 30 July 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 60 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
32.9%
avg views ÷ 18,476 subscribers
Avg views / post
6,070
20 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
20
of 67 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 27 October 2026
Posts held67 (30 July 2026 – 27 October 2026)
Views total121,410
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 03:31 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈1,440
Videos
≈10
Links
≈289

Lifetime counters from Telegram’s own channel header, read 5 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
53s
Average length
53s

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.

Recent posts

Telegram’s own ‘edited’ marker: 0 of 20 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

27 Oct 2026, 04:16 UTC≈6,690 viewsread 5 November 2026
Photo

❗️ Diqqat ❗️ 109-TOPIK PBT imtihonida ishtirok etuvchilar uchun ma’lumot. Buxoro davlat universiteti Xorijiy tillar fakulteti boshqa manzilga ko‘chirilganligi sababli, TOPIK I imtihonini Buxoro davlat universitetida topshirish uchun ariza bergan ishtirokchilar imtihon kuni quyidagi manzilga kelishlari kerak: 📍 Buxoro shahri, Muhammad Iqbol 2-tor ko‘chasi, 23-uy Iltimos, imtihon o‘tkaziladigan yangi manzil …

27 Oct 2026, 04:16 UTC≈4,300 viewsread 5 November 2026
Photo

❗️Внимание❗️ Информация для участников 109-го экзамена TOPIK PBT. В связи с переездом факультета иностранных языков Бухарского государственного университета участники, подавшие заявку на сдачу TOPIK I в Бухарском государственном университете, должны прибыть на экзамен по следующему адресу: 📍 г. Бухара, 2-й проезд Мухаммада Икбола, 23 Просим заранее ознакомиться с новым местом проведения экзамена и учитыва…

27 Oct 2026, 04:16 UTC≈4,340 viewsread 5 November 2026
Photo

❗️ 안내❗️ 제109회 TOPIK PBT 응시자를 위한 안내입니다. 부하라 국립대학교 외국어학과 이전에 따라, 부하라 국립대학교에서 TOPIK I 시험에 응시 신청한 분들은 시험 당일 아래 주소로 오시기 바랍니다. 📍우즈베키스탄 부하라시 무함마드 이크볼 제2통로 23동 (23, 2nd Muhammad Iqbol Passage, Bukhara, Uzbekistan) 시험장 주소가 변경되었으니, 사전에 새로운 시험장 위치를 확인하시고 이동 계획에 참고해 주시기 바랍니다.

18 Oct 2026, 05:07 UTC≈9,280 viewsread 5 November 2026

❗️ DIQQAT❗️ 108-TOPIK PBT IMTIHONI O‘TKAZILADIGAN JOY O‘ZGARTIRILDI 2026-yil 18-oktabr kuni taxminan soat 06:00 da Namangan davlat pedagogika institutida sodir bo‘lgan yong‘in sababli 108-TOPIK PBT imtihoni o‘tkaziladigan joy shoshilinch ravishda o‘zgartirilganini ma’lum qilamiz. 📍 Eski manzil: Namangan davlat pedagogika instituti 📍 Yangi manzil: Namangan shahridagi Kimyo xalqaro universiteti filiali Namangan davl…

17 Oct 2026, 15:31 UTC≈7,280 viewsread 5 November 2026

Jizzax Davlat Pedagogika Universiteti (A bino) 지작 국립 사범 대학교 (A 건물)

17 Oct 2026, 15:31 UTC≈6,460 viewsread 5 November 2026

Buxoro Davlat Pedagogika Instituti 부하라국립 사범대학교

17 Oct 2026, 15:31 UTC≈6,650 viewsread 5 November 2026

Andijon Davlat Chet Tillari Instituti 안지잔 국립외국어 대학교

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

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.

Mentions

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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

KIUT | Rasmiy kanal
@kiut_official · 44,831
Telegram ranks this channel #27 of 54 here — alongside 53 others — read 26 August 2026
🇰🇷 Korean Language | 한국 🇰🇷
@korean_language_kpop_dorama · 62,130
Telegram ranks this channel #38 of 78 here — alongside 77 others — read 21 August 2026
Корейский язык 🇰🇷
@koreanlanguage2023 · 60,083
Telegram ranks this channel #78 of 86 here — alongside 85 others — read 22 August 2026
Школа корейского l Korean Simple
@ksdemo · 25,333
Telegram ranks this channel #80 of 80 here — alongside 79 others — read 13 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“TOPIK-UZB 공식 채널” (@topik_kec), 18,476 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/topik_kec.

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.