Telegram RegisterThe public register of Telegram
Telegram profile photo for Sell

Channel

Sell

@bayraktarua_kyiv

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

3subscribers

-8,738 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002044619986
TypeChannel
Username@bayraktarua_kyiv
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 November 2026
Measurements held21
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/bayraktarua_kyiv

Topic

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 11 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 3 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@dyvannabrigada/304467 Aug 2026, 17:30 UTC@bayraktarua_kyiv/13765 · this entry7 Aug 2026, 17:30 UTC1.00under a minute
@bayraktarua_kyiv/13847 · this entry12 Aug 2026, 06:15 UTC@dyvannabrigada/3051312 Aug 2026, 06:15 UTC1.00under a minute
@dyvannabrigada/3051812 Aug 2026, 11:26 UTC@bayraktarua_kyiv/13854 · this entry12 Aug 2026, 11:26 UTC1.00under a minute
@bayraktar_ua/651467 Aug 2026, 17:30 UTC@bayraktarua_kyiv/13765 · this entry7 Aug 2026, 17:30 UTC1.00under a minute
@bayraktar_ua/652059 Aug 2026, 21:19 UTC@bayraktarua_kyiv/13800 · this entry9 Aug 2026, 21:19 UTC1.00under a minute
@bayraktar_ua/6527612 Aug 2026, 11:26 UTC@bayraktarua_kyiv/13854 · this entry12 Aug 2026, 11:26 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@dyvannabrigada21 (8/8 hand-verifiable sample passed)1.00under a minute@dyvannabrigada (12–9)
@bayraktar_ua19 (8/8 hand-verifiable sample passed)1.00under a minute@bayraktar_ua (12–7)
@PPOhlopci6 (6/6 hand-verifiable sample passed)1.0022 minutes@PPOhlopci (4–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 22 of the 22 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 126 comparable posts for this entry, running 6 August 2026 to 28 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @dyvannabrigada. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

18,7414,3717 August 2026 — 8,741 subscribers7 August 2026 — 8,741 subscribers8 August 2026 — 8,732 subscribers11 August 2026 — 8,690 subscribers15 August 2026 — 8,646 subscribers18 August 2026 — 8,623 subscribers22 August 2026 — 8,591 subscribers25 August 2026 — 8,557 subscribers28 August 2026 — 8,531 subscribers1 September 2026 — 8,498 subscribers4 September 2026 — 8,457 subscribers10 September 2026 — 8,411 subscribers14 September 2026 — 8,367 subscribers18 September 2026 — 8,328 subscribers27 September 2026 — 8,241 subscribers5 October 2026 — 8,184 subscribers13 October 2026 — 1 subscribers20 October 2026 — 2 subscribers26 October 2026 — 3 subscribers2 November 2026 — 4 subscribers10 November 2026 — 3 subscribers37 August 202610 November 2026
21 measurements spanning 95 days, net -8,738. 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”.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
10 Nov 2026, 08:173-1
2 Nov 2026, 13:264+1
26 Oct 2026, 15:163+1
20 Oct 2026, 07:302+1
13 Oct 2026, 22:411-8,183
5 Oct 2026, 06:588,184-57
27 Sept 2026, 05:358,241-87
18 Sept 2026, 00:198,328-39
14 Sept 2026, 03:368,367-44
10 Sept 2026, 03:558,411-46
4 Sept 2026, 19:428,457-41
1 Sept 2026, 00:258,498-33
28 Aug 2026, 14:588,531-26
25 Aug 2026, 15:428,557-34
22 Aug 2026, 07:188,591-32
18 Aug 2026, 17:368,623-23
15 Aug 2026, 18:478,646-44
11 Aug 2026, 23:028,690-42
8 Aug 2026, 14:218,732-9
7 Aug 2026, 17:018,741first reading

Engagement

159 posts held, back to 6 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 25 pages 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 159 posts for this entry, the most recent from 28 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
22m 57s
Average length
32s

Measured directly from 43 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

371 reactions across 136 posts, in 3 distinct kinds. The most used accounts for 55.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥20455.0%
❤12032.3%
👍4712.7%

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

Measured over the 159 most recent posts we hold, published 6 August 2026 to 28 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

28 Aug 2026, 16:37 UTC≈2,510 views2 reactionsread 28 August 2026

❗️Є загроза масового удару по Київщині в найближчі 48 годин, — про це пишуть монітори з посиланням на розвідспільноту США Київ Байрактар | Надіслати новину

🔥2

28 Aug 2026, 14:06 UTC266 views3 reactionsread 28 August 2026
Photo

😢Російська атака пошкодила гіпермаркет Fozzy у Вишневому Магазин зазнав значних руйнувань і тимчасово не працює. Київ Байрактар | Надіслати новину

❤1👍1🔥1

28 Aug 2026, 11:44 UTC381 views1 reactionsread 28 August 2026
Photo

❌У Києві до понеділка частково обмежать рух мостом Метро Обмеження діятимуть із 20:00 28 серпня до 17:00 31 серпня. Київ Байрактар | Надіслати новину

🔥1

28 Aug 2026, 09:40 UTC399 views2 reactionsread 28 August 2026
Photo

💔Наслідки нічної атаки РФ у Вишневому на Київщині На кадрах — згорілі автомобілі, пошкоджене покриття та уламки ворожого безпілотника. Після удару в місті спалахнули пожежі, їхні наслідки наразі ліквідовують екстрені служби. Київ Байрактар | Надіслати новину

🔥2

28 Aug 2026, 07:33 UTC442 views1 reactionsread 28 August 2026
Photo

❗️Через Київ рухаються поїзди із суттєвими затримками Київ Байрактар | Надіслати новину

❤1

28 Aug 2026, 04:59 UTC507 views1 reactionsread 28 August 2026
Photo

😡Росіяни влучили у склади «Нової пошти» та пошкодили виробництво на Київщині Київ Байрактар | Надіслати новину

🔥1

27 Aug 2026, 19:57 UTC607 views6 reactionsread 28 August 2026
Photo

❤️‍🩹Попри загрозу повторних ударів, рятувальники продовжують гасити пожежі на Київщині Через масовані атаки їм доводиться переривати роботу та відходити у безпечні місця. Наразі пожежі ліквідовують на трьох локаціях. Київ Байрактар | Надіслати новину

👍4🔥2

26 Aug 2026, 19:49 UTC163 views1 reactionsread 26 August 2026

❗️Рух Kyiv City Express призупинили через ракетну небезпеку Пасажирів просять залишити зону залізничної інфраструктури та перейти в найближче укриття або відійти на 100–200 метрів. Київ Байрактар | Надіслати новину

❤1

26 Aug 2026, 18:16 UTC332 views1 reactionsread 26 August 2026
Photo

🔥У Петропавлівській Борщагівці загасили пожежу на складі Займання сталося сьогодні на вул. Соборній — горіла покрівля триповерхової складської будівлі. Вогонь охопив 375 кв. м. Пожежу ліквідували о 14:17. На місці працювали 18 рятувальників і 5 одиниць техніки. Київ Байрактар | Надіслати новину

👍1

26 Aug 2026, 16:04 UTC412 views4 reactionsread 26 August 2026
Photo

💔На Печерську від початку року через атаки РФ пошкоджено 91 будинок — на 60% більше, ніж торік Серед них 87 багатоквартирних і 4 приватні будинки. Загалом від початку повномасштабної війни в районі постраждали 207 багатоквартирних та 9 приватних будинків. Київ Байрактар | Надіслати новину

❤2🔥2

26 Aug 2026, 14:17 UTC405 viewsread 26 August 2026
Photo

❗️МОН рекомендує українським вишам ущільнити навчальний графік Університетам радять розглянути проведення занять по суботах восени 2026-го та навесні 2027 року, а також можливе продовження навчання влітку 2027-го. Київ Байрактар | Надіслати новину

26 Aug 2026, 10:58 UTC477 views3 reactionsread 26 August 2026
Video

❗️5 карет швидкої прибули на місце ДТП: є багато поранених Рух на Вишгородській біля «Макдональдса» дуже ускладнено, краще обуджайте. Київ Байрактар | Надіслати новину

🔥3

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

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.

Mentions

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

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

“Sell” (@bayraktarua_kyiv), 3 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/bayraktarua_kyiv.

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.