Channel
@KOmediatg
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
11subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002366286498 |
|---|---|
| Type | Channel |
| Username | @KOmediatg |
| Description | Сайт: http://Komedia.tech Агенство, предоставляющее медиа услуги под ключ. г. Москва, МО Качество, удобство, выгода! |
| Created | Between 1 September 2024 and 27 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/KOmediatg |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 06:30 | 11 | no change |
| 9 Aug 2026, 13:03 | 11 | first reading |
6 posts held, back to 27 September 2024 — 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 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 6 posts for this entry, the most recent from 9 December 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
Ваш идеальный свадебный день — это наше призвание! Счастливые моменты, искренние эмоции и яркие впечатления — мы создаем свадьбы под ключ с настоящим вкусом! 📸 Наши профессиональные фотографы запечатлеют каждый миг вашего незабываемого праздника✨ С нами ваш день станет поистине особенным. Для приобретения услуг или связи с менеджером - @KOmediauserbot #фото_KOmedia
А наша команда успевает отправлять бэкстейдж! На площадке было два фотографа, видеограф и рилсмейкер💗
Видео с корпоратива BELKINA × BELEVTSEVA Для приобретения услуг или связи с менеджером - @KOmediauserbot #видео_KOmedia
Обращаясь к KOmedia, вы получаете не только квалифицированного фотографа, но и целый спектр связанных услуг: от организации съемки до профессиональной обработки фото🌷 Мы обеспечиваем синхронизацию работы всех участников вашего мероприятия, что гарантирует отсутствие накладок и максимальную слаженность🌷 Свадьба — это важное событие, и каждую деталь стоит доверить профессионалам. Выбирая комплексные услуги, вы получа…
Стильные репортажные рилсы для салона🔥 Для приобретения услуг или связи с менеджером - @KOmediauserbot #рилс_KOmedia
🚩Сегодня была съемка в Тульской области! Мы всегда готовы брать ваши мероприятия за Москвой. Для этого нужно написать нашему менеджеру и мы обсудим все детали⚡️ Для приобретения услуг или связи с менеджером - @KOmediauserbot
Showing the 6 most recent of 6 posts we hold for @KOmediatg. 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 — 1,204,182 of 1,481,217entries 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“KOmedia” (@KOmediatg), 11 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/KOmediatg.
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.