Telegram RegisterThe public register of Telegram
Telegram profile photo for COMMUNICATION KF

Channel

COMMUNICATION KF

@communicationkf

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

6,728subscribers

+101 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002238910344
TypeChannel
Username@communicationkf
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live2 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/communicationkf

Growth

6,1896,7986,493.57 August 2026 — 6,627 subscribers7 August 2026 — 6,620 subscribers10 August 2026 — 6,679 subscribers13 August 2026 — 6,594 subscribers17 August 2026 — 6,189 subscribers20 August 2026 — 6,723 subscribers23 August 2026 — 6,757 subscribers27 August 2026 — 6,798 subscribers30 August 2026 — 6,775 subscribers2 September 2026 — 6,728 subscribers6,7287 August 20262 September 2026
10 measurements spanning 26 days, net +101. 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 6,098–6,889 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 05:436,728-47
30 Aug 2026, 15:256,775-23
27 Aug 2026, 05:076,798+41
23 Aug 2026, 23:396,757+34
20 Aug 2026, 09:536,723+534
17 Aug 2026, 11:536,189-405
13 Aug 2026, 18:256,594-85
10 Aug 2026, 12:316,679+59
7 Aug 2026, 20:116,620-7
7 Aug 2026, 13:476,627first reading

Engagement

54 posts held, back to 31 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 10 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.47%
avg views ÷ 6,728 subscribers
Avg views / post
368
35 posts measured
Reaction rate
1.37%
reactions ÷ views · ER floor
Posts in window
37
of 54 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. It is computed over the 10 of 35 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 20 August 2026
Posts held54 (31 July 202620 August 2026)
Views total12,890
Reactions total58
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 10:03 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

Video runtime
2h 30m
Average length
50m 19s

Measured directly from 3 videos 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.

Reaction mix

119 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 20.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52829991220082214352420.2%
custom 52512778035249908362016.8%
custom 53507020358198339891916.0%
custom 53529533588921494851815.1%
custom 52468359526424346661512.6%
custom 53551986733052166881512.6%
custom 543174736432071608154.20%
custom 543176646404028335932.52%

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

Measured over the 54 most recent posts we hold, published 31 July 2026 to 20 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

20 Aug 2026, 07:21 UTC99 viewsread 20 August 2026

Результаты конкурса: 🥳 Победители: 1. 𝗚 𝗛 𝗢 𝗦 𝗧 𝗰𝗺𝗯𝗸🦅¹ (@Graft_adenzman) 2. Uzbek | bro 🇺🇿 (@Ruscha_gapirma_manga) 3. Kemal Azamov 💱 (@azemov_battles) 4. • ꯭꯭꯭𝐒꯭𝛐꯭𝛌꯭𝛊꯭𝚑꯭𝛃𝛆꯭𝛋꯭꯭꯭ [꯭꯭꯭🇸🇦꯭꯭]꯭ • (@solihajon_admin) 5. Лазизбек (@sunnatovich_LL) Проверить результаты ✅

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

19 Aug 2026, 20:34 UTC362 viewsread 20 August 2026

привет, работяги. До 06:00 23 августа у нас судная ночь. Значит можно делать все, кроме: •Рейдов •Боты запрет •Реклам •Шаблоны можно •Спам запрет •18+ и шок контента •Угрозам чату •СПАМИТЬ ПР ГРАММОМ ЗАПРЕТ ВСЕМ •Форса •Посторонние звуки+войс мод(все разрешено от мнение большинства) https://t.me/communicationxchat Наслаждайтесь.

Signed amur ЧХ

19 Aug 2026, 19:23 UTC848 views20 reactionsread 20 August 2026

🌟🌟🌟🌟 1-5 месту - 🧸 🌟🌟🌟🌟🌟🌟🌟🌟 ☺️ПОДПИСКА - @communicationxchat ☺️ ☺️ПОДПИСКА - @antidot_ua ☺️ 🤩конец на 350 кнопок🤩

custom 535295335889214948511custom 53551986733052166885custom 52512778035249908364

Signed Best Random Bot 🎁 [Конкурсный бот для розыгрышей | Рандомайзер]

19 Aug 2026, 19:17 UTC321 viewsread 20 August 2026
Photo

🔠🔠🔠🔠🔠 🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠 🌟Участвуйте в наших других конкурсах! Вдруг именно вы выиграете? ㅤㅤ ㅤㅤ🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠 ㅤㅤㅤㅤㅤ @tnekoff 🌺Проводилось в канале COMMUNICATION 🌺Наш чатик — тык 🌺Наш бот — тык тык 🌺Наш тикток — тыкниㅤㅤㅤㅤㅤㅤㅤㅤㅤ 🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠

Signed amur ЧХ

19 Aug 2026, 03:37 UTC347 views3 reactionsread 20 August 2026
Photo

включаем уведомления, каждый день будет так😜

custom 53529533588921494852custom 52512778035249908361

Signed любимый бывший

18 Aug 2026, 16:15 UTC992 viewsread 20 August 2026
Photo

🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠🔠 🌟Суть баттла заключается в том, что вы кидаете нам в личные сообщения СВОЕ видео/фото АБСОЛЮТНО анонимно. 🤩19 АВГУСТА — 18:30МСК🤩 🌟ПРАВИЛА: 🖋️ 🍎На видео/фото должны быть исключительно, лишь вы там; 🍎Тот, кто наберет больше реакций переходит на следующий тур; 🍎Правила конкурса могут меняться во время самой игры.(вы за это будете предупреждены в канале); 🍎ПРИГЛОСКА ДРУЗЕЙ +ШАНС К ПОБЕДЕ; 🍎Фотки/Видео без л

Signed amur ЧХ

17 Aug 2026, 18:55 UTC386 views8 reactionsread 20 August 2026
Photo

196

custom 52512778035249908365custom 53529533588921494852custom 53551986733052166881

Signed CANNABIS C.V

17 Aug 2026, 18:52 UTC329 views1 reactionsread 20 August 2026

первым 4 кто отгадает мой рост скинут мишку

custom 52512778035249908361

Signed CANNABIS C.V

17 Aug 2026, 18:51 UTC321 views1 reactionsread 20 August 2026
Photo

21 да

custom 52512778035249908361

Signed CANNABIS C.V

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

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

“COMMUNICATION KF” (@communicationkf), 6,728 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/communicationkf.

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.