Channel
@kupyansk
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry
15,071subscribers
+65 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001375883849 |
|---|---|
| Type | Channel |
| Username | @kupyansk |
| Description | 🔵 Канал @kupyansk 🟡 Чат: @kupchat 📩 Зворотний зв'язок: @kupiansk_bot |
| Created | 15 November 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 59 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/kupyansk |
National news — 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 96% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 13:18 | 15,071 | -3 |
| 7 Nov 2026, 07:18 | 15,074 | -5 |
| 6 Nov 2026, 06:51 | 15,079 | -2 |
| 5 Nov 2026, 08:40 | 15,081 | -15 |
| 4 Nov 2026, 10:05 | 15,096 | -6 |
| 3 Nov 2026, 08:29 | 15,102 | -12 |
| 2 Nov 2026, 07:01 | 15,114 | -6 |
| 1 Nov 2026, 07:27 | 15,120 | -2 |
| 31 Oct 2026, 06:20 | 15,122 | -5 |
| 30 Oct 2026, 05:56 | 15,127 | -6 |
| 29 Oct 2026, 06:46 | 15,133 | -7 |
| 28 Oct 2026, 05:57 | 15,140 | -1 |
| 27 Oct 2026, 07:01 | 15,141 | +3 |
| 26 Oct 2026, 09:10 | 15,138 | -2 |
| 25 Oct 2026, 05:41 | 15,140 | -8 |
| 24 Oct 2026, 03:26 | 15,148 | +12 |
| 22 Oct 2026, 23:56 | 15,136 | +2 |
| 21 Oct 2026, 23:21 | 15,134 | +11 |
| 20 Oct 2026, 14:56 | 15,123 | -42 |
| 19 Oct 2026, 14:09 | 15,165 | first reading |
278 posts held, back to 5 August 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 65 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 8 November 2026 |
|---|---|
| Posts held | 278 (5 August 2026 – 8 November 2026) |
| Views total | 351,850 |
| Reactions total | 4,871 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Nov 2026, 17:45 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.
Lifetime counters from Telegram’s own channel header, read 8 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.
Measured directly from 125 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.
21,945 reactions across 278 posts, in 41 distinct kinds. The most used accounts for 17.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3,788 | 17.3% | |
| 😢 | 3,253 | 14.8% | |
| 🤬 | 2,941 | 13.4% | |
| 🙏 | 2,560 | 11.7% | |
| 🔥 | 2,495 | 11.4% | |
| 👍 | 844 | 3.85% | |
| 😁 | 741 | 3.38% | |
| ⚡ | 739 | 3.37% | |
| 💔 | 664 | 3.03% | |
| 💯 | 557 | 2.54% | |
| 💩 | 486 | 2.21% | |
| 🤣 | 474 | 2.16% | |
| 🤔 | 378 | 1.72% | |
| 👎 | 298 | 1.36% | |
| 😭 | 280 | 1.28% | |
| 👌 | 207 | 0.943% | |
| 🎉 | 185 | 0.843% | |
| 🤝 | 183 | 0.834% | |
| 🫡 | 149 | 0.679% | |
| 🤮 | 133 | 0.606% | |
| 21 further kinds | 590 | 2.69% |
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 278 of the 278 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 21,945 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 278 most recent posts we hold, published 5 August 2026 to 8 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @kupyansk. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 278 most recent posts we hold for this entry, published 5 August 2026 to 8 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 278 most recent posts we hold, published 5 August 2026 to 8 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 3 of 68 posts held from the last 30 days (4.41%) 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).
«Ми гуляли з ним по ХТЗ, по парку. О пів на шосту ранку я встаю, вийшов, взяв його і пішли гуляти. Погуляв, погодували — назад в машину. Там було застелено у нього все, він жодного разу навіть не насмітив у машині. Я біля машини пораюся і він біля мене». У Харкові родина переселенців з Куп'янського району була змушена тримати свого собаку Будулая в машині через відмову орендодавців пускати їх у квартиру з твариною. …
😢51❤21🙏11
📍 Ківшарівка з дрона @kupyansk
😢69💔11🙏7
Сьогодні вдень селище Шевченкове вкотре було атаковане ворогом. В результаті удару чотирьох реактивних дронів було пошкоджено приміщення суду, магазину будівельних матеріалів, декількох житлових будинків, адміністративні приміщення... На щастя, без людських жертв. ⛓ Сергій Старіков, начальник Шевченківської СВА @kupyansk
🤬66😢11🙏9
«Сброд извращенцев под предводительством беспринципного командира, готового на любую клоунаду ради медийки», - пишуть руські пропагандисти про 23-й полк Р.У.Г. А які ж скрєпи у їх «славетної» армії? Сексуальне насильство як покарання. Примус знімати знущання на камеру й зберігати записи в телефоні. Про це розповідає 62-річний російський військовополонений, який дякує бійцям полку Р.У.Г за порятунок.
🤯27🤮7💯3
Фух
😁41💯23🙏1
Шукаєте підробіток або основну роботу з вільним графіком? У Bolt Food зараз відкритий набір кур'єрів, і для новачків діє хороша акція — можна забрати +4 000 грн бонусу до основного заробітку. Працювати можна майже в будь-якому великому місті України (від Харкова до Мукачева) пішки, на велосипеді, самокаті чи авто. Як отримати бонус: 1. Реєстрація: перейдіть за посиланням до 30.11.2026 — https://bolt.eu/uk-ua/food…
❤11✍2😎2
📍 Куп'янщина, Дворічанський напрямок Відпрацювали по позиціях російських окупантів. 🌙«Northern Eagle» 151-ї ОМБр. @kupyansk
⚡34👍21🤝3
Владислав Ігнатенко на псевдо «Каспер» з селища Ківшарівка на Куп'янщині розпочав військовий шлях у 18 років — три роки відслужив у морській піхоті. Переживши окупацію та російський полон, наприкінці 2022 року чоловік добровільно повернувся до війська — боронив країну на Донеччині у складі 54-ї ОМБр. Командир взводу загинув 18 серпня 2026 року в районі Калеників, закривши власним тілом пораненого побратима. Поперед…
😢128🙏36🫡6
💥 Продовжуємо успішно нищити ворога у Куп’янську Бойова робота операторів дронів роти БпАК «Привид» 2 механізованого батальйону, батальйону безпілотних систем та мотопіхотного батальйону 41 окремої механізованої бригади — це злагоджені дії, холодний розрахунок і жодного шансу для окупантів. Кожен удар — просто ювелірний! У Куп’янську у ворога є лише два варіанти: здаватися у полон або залишитися у місті назавжди! 💥…
🔥93👌6🤝3
😏
💯24😁15💅1
П’ятеро працівниць Харківського обласного центру контролю та профілактики хвороб загинули внаслідок авіаудару РФ, повідомили в Міністерстві охорони здоров'я. Після деокупації одного з міст на Харківщині вони одними з перших повернулися до роботи. Власноруч розчищали пошкоджені приміщення, прибирали вибите скло й відновлювали лабораторії. @babel
😭111💔27🙏10
На Південно-Слобожанському напрямку противник п’ять разів атакував позиції наших підрозділів у бік населених пунктів Тернова, Захарівка, Охрімівка та Миколаївка. Дві з цих атак тривають. На Куп’янському напрямку ворог двічі штурмував в бік Радьківки.
🤬33🙏12😢3
Showing the 12 most recent of 278 posts we hold for @kupyansk. 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.
@kupyansk edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Чи є хоч хтось, кому не по цимбалах існування ФК Куп'янськ? 😑
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 278 most recent posts we hold, published 5 August 2026 to 8 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 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.
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.
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.
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“Куп'янськ 🇺🇦 Перший” (@kupyansk), 15,071 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/kupyansk.
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.