Telegram RegisterThe public register of Telegram
Telegram profile photo for 💙💛ОПЕРАТИВНА БІЛКА 🐿️

Channel

💙💛ОПЕРАТИВНА БІЛКА 🐿️

@operativnabilka

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

7,596subscribers

-591 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-1001895284819
TypeChannel
Username@operativnabilka
Description🚨🫡Сповіщення тривог, моніторинг загроз Обговорення ситуації в країні та на фронті, тільки перевірені новини, та достовірна інформація від військових і жителів України☝️ 🇺🇦 Запропонувати новину , рекламу, чи співпрацю @MurkaHuliganka
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 November 2026
Measurements held27
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/operativnabilka

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 1 other registered channel. 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@kpszsu/720128 Aug 2026, 21:35 UTC@operativnabilka/624355 · this entry8 Aug 2026, 21:35 UTC1.00under a minute
@kpszsu/712482 Aug 2026, 17:08 UTC@operativnabilka/630681 · this entry18 Aug 2026, 04:26 UTC1.0015 days
@kpszsu/7345419 Aug 2026, 19:07 UTC@operativnabilka/631792 · this entry19 Aug 2026, 19:07 UTC1.00under a minute
@kpszsu/7446825 Aug 2026, 17:21 UTC@operativnabilka/637189 · this entry25 Aug 2026, 17:21 UTC1.00under a minute
@kpszsu/9496111 Nov 2026, 01:11 UTC@operativnabilka/698905 · this entry11 Nov 2026, 01:11 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
@kpszsu5 (5/5 hand-verifiable sample passed)1.00under a minute@kpszsu (5–0)

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. 5 of the 5 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 184 comparable posts for this entry, running 7 August 2026 to 15 November 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).

Recorded under the key clone_copy, last confirmed 16 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.

Growth

7,5968,1877,891.57 August 2026 — 8,187 subscribers8 August 2026 — 8,180 subscribers11 August 2026 — 8,169 subscribers14 August 2026 — 8,164 subscribers17 August 2026 — 8,143 subscribers20 August 2026 — 8,135 subscribers23 August 2026 — 8,118 subscribers26 August 2026 — 8,102 subscribers29 August 2026 — 8,090 subscribers1 September 2026 — 8,076 subscribers5 September 2026 — 8,050 subscribers10 September 2026 — 8,033 subscribers13 September 2026 — 8,034 subscribers17 September 2026 — 8,038 subscribers26 September 2026 — 7,982 subscribers5 October 2026 — 7,916 subscribers11 October 2026 — 7,870 subscribers14 October 2026 — 7,851 subscribers18 October 2026 — 7,811 subscribers21 October 2026 — 7,787 subscribers24 October 2026 — 7,757 subscribers27 October 2026 — 7,728 subscribers30 October 2026 — 7,712 subscribers2 November 2026 — 7,681 subscribers5 November 2026 — 7,666 subscribers8 November 2026 — 7,645 subscribers13 November 2026 — 7,596 subscribers7 August 202613 November 2026
27 measurements spanning 98 days, net -591. 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 7,507–8,276 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
13 Nov 2026, 11:187,596-49
8 Nov 2026, 18:117,645-21
5 Nov 2026, 12:497,666-15
2 Nov 2026, 21:167,681-31
30 Oct 2026, 14:387,712-16
27 Oct 2026, 13:557,728-29
24 Oct 2026, 05:117,757-30
21 Oct 2026, 00:477,787-24
18 Oct 2026, 03:567,811-40
14 Oct 2026, 20:287,851-19
11 Oct 2026, 22:387,870-46
5 Oct 2026, 05:417,916-66
26 Sept 2026, 08:557,982-56
17 Sept 2026, 14:018,038+4
13 Sept 2026, 21:418,034+1
10 Sept 2026, 08:218,033-17
5 Sept 2026, 08:178,050-26
1 Sept 2026, 04:478,076-14
29 Aug 2026, 13:528,090-12
26 Aug 2026, 20:478,102first reading

Engagement

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

ERR · 30 days
1.27%
avg views ÷ 7,596 subscribers
Avg views / post
96.7
518 posts measured
Reaction rate
1.07%
reactions ÷ views · ER floor
Posts in window
518
of 914 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 75 of 518 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 16 November 2026
Posts held914 (7 August 2026 – 16 November 2026)
Views total50,079
Reactions total110
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 08: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

Photos
≈53,800
Videos
≈36,600
Links
≈383,000

Lifetime counters from Telegram’s own channel header, read 16 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
2m 43s
Average length
41s

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

299 reactions across 146 posts, in 5 distinct kinds. The most used accounts for 75.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏22675.6%
🤬6020.1%
😢82.68%
😁31.00%
🔥20.669%

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

Measured over the 914 most recent posts we hold, published 7 August 2026 to 16 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.

Recent posts

Telegram’s own ‘edited’ marker: 248 of 518 posts held from the last 30 days (47.9%) 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).

16 Nov 2026, 08:02 UTC2 viewsread 16 November 2026

🛸 Одеса та громада · Одеська обл. Загроза БПЛА. Перейдіть в укриття!

Signed operativnabilka

16 Nov 2026, 07:57 UTC63 views1 reactionsread 16 November 2026

🟡 Одеський р-н · Одеська обл. Повітряна тривога · жовтий рівень

🙏1

Signed operativnabilka

16 Nov 2026, 07:57 UTC63 viewsread 16 November 2026

🟢 Відбій повітряної тривоги Харківський р-н · Харківська обл. Харків та громада · Харківська обл.

Signed operativnabilka

16 Nov 2026, 07:56 UTC93 viewsread 16 November 2026

💥 24 вибухи за добу: під ударами РФ три громади Чернігівщини Протягом 15 листопада росіяни атакували вісім прикордонних сіл. 🔹 Новгород-Сіверська: Михальчина-Слобода — 2 вибухи; Бучки — 4. 🔹 Семенівська: Луб'яне — 3; Сергіївське — 1; Лісківщина — 1; Прогрес — 1. 🔹 Сновська: Гута-Студенецька — 2; Хрінівка — 10. ⚠️ Росіяни застосовували артилерію, FPV-дрони та скиди вибухівки з безпілотників.

Signed Євгеній

16 Nov 2026, 07:56 UTC93 viewsread 16 November 2026

⚡️ Оперативна інформація Дніпропетровська область Одеська область

Signed operativnabilka

16 Nov 2026, 07:52 UTC119 viewsread 16 November 2026

🔴 Самарівський р-н · Дніпропетровська обл. Повітряна тривога · червоний рівень

Signed operativnabilka

16 Nov 2026, 07:50 UTC141 viewsread 16 November 2026

🟡 Миколаївський р-н · Миколаївська обл. Повітряна тривога · жовтий рівень

Signed operativnabilka

16 Nov 2026, 07:48 UTC127 viewsread 16 November 2026

⚡️ Оперативна інформація Київська область Одеська область

Signed operativnabilka

16 Nov 2026, 07:48 UTC134 viewsread 16 November 2026

🔴 Павлоградський р-н · Дніпропетровська обл. Повітряна тривога · червоний рівень

Signed operativnabilka

16 Nov 2026, 07:47 UTC132 viewsread 16 November 2026

🟢 Відбій повітряної тривоги Білгород-Дністровський р-н · Одеська обл. Одеський р-н · Одеська обл.

Signed operativnabilka

16 Nov 2026, 07:41 UTC176 viewsread 16 November 2026
Photo

Не будь стороннім глядачем. Приєднуйся до нас і знищуй ворога разом з найкращими. Обирай свій шлях у 46 оаембр. Будь серед своїх. 📄 Заповнюй анкету: https://forms.gle/HmiEYzAF78ZMAgrX8 ⌨️ Пиши у наш чат-бот: https://t.me/sorok_shosta_hr_bot 📌 Всі вакансії бригади: https://46dshv.mil.gov.ua/recruiting/

Signed 𝓜𝓾𝓻𝓴𝓪 𝓗𝓾𝓵𝓲𝓰𝓪𝓷𝓴𝓪

16 Nov 2026, 07:41 UTC137 viewsread 16 November 2026

🟢 Відбій повітряної тривоги Березівський р-н · Одеська обл. Миколаївський р-н · Миколаївська обл. Вознесенський р-н · Миколаївська обл.

Signed operativnabilka

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

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.

Виплати ЗСУ ТРО ССО НГУ СБС
@vyplaty_zsu · 43,126
Telegram ranks this channel #5 of 64 here — alongside 63 others — read 2 September 2026
Новини Ізмаїл || Новости Измаил 🌱🍃
@izmailnovostii · 25,852
Telegram ranks this channel #11 of 52 here — alongside 51 others — read 14 September 2026
UA HiMARS 18+🫡
@war_ua_22 · 19,436
Telegram ranks this channel #13 of 80 here — alongside 79 others — read 3 October 2026
Чисте небо Київська область та Київ.
@chyste_nebo · 273,138
Telegram ranks this channel #22 of 83 here — alongside 82 others — read 14 August 2026
Інформатор Дніпро | Радар
@dnipro_informator · 29,600
Telegram ranks this channel #39 of 77 here — alongside 76 others — read 6 September 2026
НУ І НОВІК
@ny_i_novik · 20,902
Telegram ranks this channel #44 of 78 here — alongside 77 others — read 30 September 2026
Правда Васильків 🇺🇦
@Vasylkiv_Vasilkov · 24,153
Telegram ranks this channel #44 of 75 here — alongside 74 others — read 18 September 2026
НУ І ДНІПРО! 🇺🇦
@ny_i_dnipro · 289,947
Telegram ranks this channel #44 of 72 here — alongside 71 others — read 10 August 2026
Дніпровський пише
@dnipro_pishet · 52,273
Telegram ranks this channel #51 of 79 here — alongside 78 others — read 24 August 2026
ДНІПРО LIVE 24/7 🇺🇦 ДНЕПР РАДАР ТРИВОГА
@live_dnepr · 25,406
Telegram ranks this channel #52 of 78 here — alongside 77 others — read 14 September 2026

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

“💙💛ОПЕРАТИВНА БІЛКА 🐿️” (@operativnabilka), 7,596 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/operativnabilka.

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.