Telegram RegisterThe public register of Telegram
Telegram profile photo for 📰 Новини 🍁 Прилуки Оперативні

Channel

📰 Новини 🍁 Прилуки Оперативні

@pryluky_operative

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

27,289subscribers

+1,802 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001523404060
TypeChannel
Username@pryluky_operative
Description🗣 Незалежне медіа: першоджерело новин Прилуччини, моніторинг під час небезпеки. 📰 Ексклюзивні новини Прилук на сайті https://pryluky.club
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/pryluky_operative

Topic

Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 82% 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 why it has no browse page of its own yet.

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 word for word 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@pryluky_operative/83851 · this entry6 Aug 2026, 06:40 UTC@priluki/692386 Aug 2026, 06:41 UTC1.002 minutes
@pryluky_operative/83853 · this entry6 Aug 2026, 06:50 UTC@priluki/692406 Aug 2026, 07:25 UTC1.0035 minutes
@pryluky_operative/83960 · this entry7 Aug 2026, 09:11 UTC@priluki/693027 Aug 2026, 09:11 UTC1.00under a minute
@pryluky_operative/83962 · this entry7 Aug 2026, 09:50 UTC@priluki/693037 Aug 2026, 09:51 UTC1.00under a minute
@pryluky_operative/83970 · this entry7 Aug 2026, 10:23 UTC@priluki/693067 Aug 2026, 10:58 UTC1.0035 minutes
@pryluky_operative/83972 · this entry7 Aug 2026, 11:15 UTC@priluki/693077 Aug 2026, 11:35 UTC1.0020 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@priluki11 (8/8 hand-verifiable sample passed)1.002 minutesthis entry (101)

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. 1 of the 1 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 34 comparable posts for this entry, running 6 August 2026 to 8 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).

Across the whole group of 2, the earliest publisher we hold is @priluki. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 8 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

25,48727,28926,3886 August 2026 — 25,487 subscribers7 August 2026 — 25,494 subscribers8 August 2026 — 25,590 subscribers9 August 2026 — 25,631 subscribers10 August 2026 — 25,638 subscribers11 August 2026 — 25,656 subscribers12 August 2026 — 25,901 subscribers13 August 2026 — 25,922 subscribers14 August 2026 — 25,953 subscribers16 August 2026 — 25,966 subscribers17 August 2026 — 25,964 subscribers19 August 2026 — 25,957 subscribers20 August 2026 — 26,135 subscribers21 August 2026 — 26,156 subscribers22 August 2026 — 26,204 subscribers24 August 2026 — 26,213 subscribers25 August 2026 — 26,240 subscribers26 August 2026 — 26,355 subscribers27 August 2026 — 26,374 subscribers29 August 2026 — 26,385 subscribers30 August 2026 — 26,399 subscribers31 August 2026 — 26,409 subscribers1 September 2026 — 26,420 subscribers1 September 2026 — 26,421 subscribers3 September 2026 — 26,441 subscribers4 September 2026 — 26,494 subscribers7 September 2026 — 26,554 subscribers10 September 2026 — 26,793 subscribers12 September 2026 — 26,826 subscribers14 September 2026 — 26,847 subscribers15 September 2026 — 27,232 subscribers18 September 2026 — 27,289 subscribers6 August 202618 September 2026
32 measurements spanning 43 days, net +1,802. 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 25,217–27,559 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
18 Sept 2026, 03:3927,289+57
15 Sept 2026, 21:1727,232+385
14 Sept 2026, 05:1926,847+21
12 Sept 2026, 13:3926,826+33
10 Sept 2026, 12:3626,793+239
7 Sept 2026, 09:2026,554+60
4 Sept 2026, 17:2026,494+53
3 Sept 2026, 06:1426,441+20
1 Sept 2026, 22:4826,421+1
1 Sept 2026, 02:1326,420+11
31 Aug 2026, 03:3926,409+10
30 Aug 2026, 03:1426,399+14
29 Aug 2026, 02:4326,385+11
27 Aug 2026, 23:0526,374+19
26 Aug 2026, 20:0426,355+115
25 Aug 2026, 16:4226,240+27
24 Aug 2026, 13:5426,213+9
22 Aug 2026, 19:2326,204+48
21 Aug 2026, 11:1826,156+21
20 Aug 2026, 10:3826,135first reading

Engagement

1,008 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 61 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
19.7%
avg views ÷ 27,289 subscribers
Avg views / post
5,380
373 posts measured
Reaction rate
0.571%
reactions ÷ views · ER floor
Posts in window
373
of 1,008 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 369 of 373 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 23 September 2026
Posts held1,008 (6 August 202623 September 2026)
Views total2,008,078
Reactions total11,414
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Sept 2026, 17:07 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
43,000
Videos
6,760
Links
63,900

Lifetime counters from Telegram’s own channel header, read 23 September 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
49m 05s
Average length
37s

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

28,916 reactions across 972 posts, in 11 distinct kinds. The most used accounts for 43.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤬12,53843.4%
😢5,43218.8%
👍4,82916.7%
🔥1,7275.97%
❤‍🔥1,7185.94%
😁8983.11%
🙏5761.99%
👎5701.97%
👀3521.22%
😍1990.688%
🫡770.266%

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 984 of the 1,000 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 29,092 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 6 August 2026 to 23 September 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.

Telegram Stars

Stars received
65
across the posts below
Posts paid on
13
of 1,000 we hold a reading for · 1%
Most on one post
50
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @pryluky_operative. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 6 August 2026 to 23 September 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.

Recent posts

23 Sept 2026, 17:05 UTC≈1,540 views1 reactionsread 23 September 2026
Photo

⚡️ Реактивний БпЛА курсом на Київщину через Прилуцький район 🛡Новини Прилуки

🙏1

23 Sept 2026, 16:57 UTC≈2,240 views39 reactionsread 23 September 2026
Photo

🟥🟥🟥 🔴 19:57‍​‌‌ Повітряна‌​​ тривога​​​ у‌‌‌ Прилуцькому районі 🟡 Жовтий​​‌ рівень​​‌ небезпеки‌​‌ —​‌‌ дронова загроза 🛡 Новини Прилуки

🤬27🙏12

23 Sept 2026, 16:46 UTC≈2,820 views17 reactionsread 23 September 2026

🪖🪖🪖 Актуальні‍​‌‌ загрози‌​​​ на Чернігівщині: ⚡️ Реактивний БпЛА​​‌ на‌‌​​ Сумщині‌​​ у‌‌​‌ напрямку​‌‌ Коропа (Чернігівщина) 🛡 Новини Прилуки

🤬8🙏7🔥1😢1

23 Sept 2026, 15:28 UTC≈4,720 views50 reactionsread 23 September 2026

США надіслали Росії запрошення на саміт G20 у Маямі, де ймовірно можуть відбутися переговори Зеленського, Путіна та Трампа. Саміт заплановано на 14–15 грудня. Зеленський раніше заявляв про готовність зустрітися з Путіним у Маямі. 🛡Новини Прилуки

👀28👍15🤬4😍2👎1

23 Sept 2026, 15:17 UTC≈4,870 views17 reactionsread 23 September 2026

🪖🪖🪖 Актуальні‍​‌‌‌ загрози​​​​ на Чернігівщині: ⚡️ Реактивні БпЛА​‌‌‌ повз​​‌​ Славутич​‌‌​ у‌​‌‌ напрямку Київщини 🛡 Новини Прилуки

🤬13🙏4

23 Sept 2026, 14:43 UTC≈5,940 views188 reactionsread 23 September 2026
Video

❗️ Швидка не‍​ повинна‌ виїжджати,‌ щоб‌ когось​​ прокапати​ чи​ поміряти​ тиск.‌‌ Вона‌ приїжджає,​ якщо​ є‌​ загроза​ життю,‌ —‌ міністр​‌ охорони​ здоров'я Ляшко 🛡 Новини Прилуки

🤬161👍14👀12😢1

23 Sept 2026, 14:37 UTC≈5,800 views26 reactionsread 23 September 2026

🟩🟩🟩 🟢 17:37‍​‌‌ Відбій‌​​​ повітряної​​‌ тривоги‌‌​​ у‌​​ Прилуцькому районі ⏲ Тривога‌‌​‌ тривала​‌‌ 49 хв. 🛡 Новини Прилуки

🙏20❤‍🔥3👍3

23 Sept 2026, 14:33 UTC≈5,870 views28 reactionsread 23 September 2026

🪖🪖🪖 Актуальні‍​ загрози‌‌ на Чернігівщині: ⚡️ Реактивний БпЛА‌​ на​​ півночі​ Чернігівщини​‌ на/повз‌‌ Ріпки​​ у‌​ південно-західному напрямку ⏲ 46 хв.​ триває‌‌ повітряна​‌ тривога​‌ у‌ Прилуцькому районі 🛡 Новини Прилуки

🤬14🙏12😢2

23 Sept 2026, 14:20 UTC≈6,190 views76 reactionsread 23 September 2026
Video

❗️Атаки рф по Києву: вже 43 людини постраждало — КМВА Наразі вогнеборці ліквідували всі загоряння, спричинені ворожими атаками. 🛡Новини Прилуки

🤬40😢27🙏5👀2👍2

23 Sept 2026, 14:07 UTC≈6,290 views26 reactionsread 23 September 2026

⚠️ Актуальні загрози‍​‌ на‌‌ Чернігівщині​​ (станом​​ на 17:07) ⚡️ 1 реактивний​‌ БпЛА‌‌ курсом​​ на Короп ⏲ 20 хв.‌​ триває​‌ повітряна‌​ тривога‌​ у‌‌ Прилуцькому районі 🛡 Новини Прилуки

🤬15🙏10😍1

23 Sept 2026, 13:58 UTC≈6,470 views39 reactionsread 23 September 2026

⚠️ Актуальні загрози‍​‌ на‌‌ Чернігівщині​​ (станом​​ на 16:58) ⚡️ 1 реактивний​‌ БпЛА‌‌ курсом​​ на Славутич ⏲ 11 хв.‌​ триває​‌ повітряна‌​ тривога‌​ у‌‌ Прилуцькому районі 🛡 Новини Прилуки

🤬23🙏16

23 Sept 2026, 13:48 UTC≈21,600 views61 reactionsread 23 September 2026

⚡️ Реактивний БпЛА курсом на Припутні 🛡Новини Прилуки

🙏31🤬21😢9

Showing the 12 most recent of 1,008 posts we hold for @pryluky_operative. 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.

Posts edited after publishing

@pryluky_operative edited 1 post 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.

First edit seen
9 August 2026
Most recent edit
9 August 2026

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 6 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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

🛡 Прилуки Оперативні
@priluki · 64,343
#1
Небайдужі Прилучани | Прилуки
@nebaiduzhiprk · 15,573
#2
Лачен пише
@lachentyt · 1,554,565
#3
🔴 Прилуки Особливі 🔴
@pryluky_ua · 1,898
#4
Труха⚡️Чернігів
@chernigiv_truexa · 162,850
#5
Суспільне Чернігів
@suspilnechernihiv · 194,209
#6
Небайдужі Прилучани | Прилуки
@nebaiduzhiprlk · 1,472
#7
Карта повітряних тривог 🇺🇦
@alarmua · 941,699
#8
Прилуки на зв'язку!
@prk_alarm · 4,115
#9
❗️Новини Чернігова та області - Челайн
@CheLineTv · 11,205
#10
Ічнянщина інформаційно
@ichnya · 4,197
#11
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 725,843
#12
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 905,765
#13
🇺🇦 Поліція Чернігівської області
@gunpChernihiv · 2,382
#14
ПІВНІЧ
@pivnic · 3,022
#15
Україна Online: Новини | Політика
@UaOnlii · 1,575,421
#16
Киевский Движ
@k_dvizh · 465,905
#17
Тактична Рукавичка/НІЖИН
@taktychna_rukavuchkaa · 46,478
#18
Новий Чернігів Телеканал
@newch_tv · 1,412
#19
Прилуки на зв'язку! | Радар | Шахеди та ракети | Світло
@pryluky · 7,152
#20
Плітки в Ніжині, в Україні та світі
@plitki_v_nizhyni · 19,932
#21
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 394,900
#22
Чернігів Оперативний
@ChernigivOperative · 60,102
#23
Хуйовий Чернігів | Чернигов
@h_chernihiv · 34,026
#24
Тотальна Зрада
@totallzrada · 266,323
#25
Куди летить? | Тривога
@radar_raketaa · 502,859
#26
Х ЧЕРНІГІВ 🔥 X CHERNIHIV 🔥 НОВИНИ 🔥 X CHE
@xchernihiv · 3,727
#27
Love Chernihiv | Новини Чернігів
@lovechernihiv · 52,142
#28
ЗАХИСТ ТА ІНШЕ( НІЖИН )
@nizhyn_zahist · 9,651
#29
Новини Чернігівщини
@newchnews · 25,466
#30
НЕЖАТИН: Новини Ніжинщини💙та💛України
@nezhatin · 8,501
#31
🔊Чому тривога?🚨| Повітряна тривога | Ракетна небезпека | єРадар |
@tryvoga_chomu · 275,418
#32
Балсанка
@Balsanka_News · 3,226
#33
ГУ ДСНС України в Івано-Франківській області
@ifdsns · 2,687
#34
🔊ПРИЛУКИ NEWS🇺🇦
@priluki_41 · 445
#35
Ніжин / Офіційно
@info_nizhyn · 22,906
#36
Сирени Чернігівщина🇺🇦
@sirena_chernihiv · 800
#37
Херсонщина Моніторинг🇺🇦
@kherson_monitoring · 66,369
#38
ХАБ. ЧЕРНІГІВ ТА ОБЛАСТЬ "НЕЗЛАМНІСТЬ"
@chernihivnewshub · 3,626
#39
Доброго вечора, ми з Чернігова!
@dobrogovechorachernigiv · 1,500
#40
Ринда моніторить
@kudy_letyt · 143,342
#41
Робота та послуги Прилуки
@work_priluki · 7,012
#42
💡Прилуки Енергетичні
@prk_watcher · 570
#43
Труха⚡️Україна
@truexanewsua · 3,127,306
#44
Николаевский Ванёк
@vanek_nikolaev · 2,636,316
#45
Труха⚡️Київ
@truexakyiv · 918,218
#46
ТСН новини / ТСН.ua
@tch_channel · 737,756
#47
ЛОК «Дружба» 5 зміна
@lokdruzba5 · 168
#48
🇺🇦 В'ячеслав Чаус/ Чернігівська ОДА (ОВА)
@chernigivskaODA · 34,701
#49
Чернігівський обласний центр з гідрометеорології
@chernihivchm · 413
#50
Патрульна поліція Чернігівської області
@chernihivpatrolpolice · 1,178
#51
Чернігівський фонтан⛲️
@chernihiv_fontan · 3,736
#52
Батальйон «Монако» | Україна | Новини
@batalionmonako · 710,211
#53
ТІМ+ TV
@timtvprk · 443
#54
Пресслужба Чернігівської міської ради
@chernihivrada · 3,481
#55
Олександр ЛОМАКО | Офіційно про Чернігів
@lomako_oleksandr · 3,311
#56
Ми Україна. Ексклюзив
@weukrainetv_ex · 1,562
#57
Робота в Прилуках
@robota_priluki · 4,872
#58
Чернігівщина: політика і компромат
@politicompr · 2,956
#59
Ніжин Оперативно
@nizhyn_operatively · 19,326
#60
КИЇВ24 | ТЕРМІНОВО
@kyivtv · 10,126
#61
Труха⚡️Мариуполь
@truexa_mariupol · 486
#62
Патрульна поліція Вінницької області
@patrolpolice_vinnytsia · 1,760
#63
Запорізька обласна прокуратура
@zap_gp_gov_ua · 1,026
#64
Поліція Вінницької області 🇺🇦
@vinnpol · 4,561
#65
Дмитро Брижинський
@bryzynskyi · 5,270
#66
Миколаївський обласний центр з гідрометеорології
@mykolaiv_hmc · 1,548
#67
Корюківські партизани
@partizanyofkrk · 6,060
#68
Еспресо Захід
@espreso_zahid · 2,116
#69
ДСНС Миколаїв
@dsns_mykolaiv · 2,593
#70
ДСНС Запоріжжя
@gu_dsns_zp · 3,190
#71
Arsenal Art Space
@ArsenalArtSpace · 339
#72
Батя пише
@tro_prk · 840
#73
Головне управління ДСНС України у Житомирській області
@DSNS_Zhytomyr · 1,715
#74
Військово-Морські Сили ЗС України | UA Navy
@ukrainian_navy · 12,158
#75
Поліція Рівненщини
@NPU_Rivne · 6,704
#76
24 Канал | Новини України
@channel24_ua · 201,996
#77
Nizhyn Post
@nizhyn_post · 4,445
#78
ITV media group | Новини Рівного
@itv_mg · 4,626
#79
Новости Днепра | Новини Дніпра
@dnipro_news · 1,443
#80
Херсонська обласна прокуратура
@phogovua · 2,368
#81
Кіровоградська ОДА/ОВА
@kirovohradskaODA · 5,239
#82
felicita catherina
@withsunshine · 452
#83
Числові ігри долі
@numerologyway · 741
#84

Read from Telegram’s recommendation API, most recently 11 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

🛡 Прилуки Оперативні
@priluki · 64,343
Telegram ranks this channel #2 of 71 here — alongside 70 others — read 21 August 2026
Чернігів ⚡️Новини
@chernihiv_insider · 23,514
Telegram ranks this channel #36 of 85 here — alongside 84 others — read 18 September 2026
Тактична Рукавичка/НІЖИН
@taktychna_rukavuchkaa · 46,478
Telegram ranks this channel #37 of 66 here — alongside 65 others — read 27 August 2026
Ніжин / Офіційно
@info_nizhyn · 22,906
Telegram ranks this channel #39 of 68 here — alongside 67 others — read 19 September 2026
Новини Чернігівщини
@newchnews · 25,466
Telegram ranks this channel #42 of 88 here — alongside 87 others — read 14 September 2026

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.

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

“📰 Новини 🍁 Прилуки Оперативні” (@pryluky_operative), 27,289 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/pryluky_operative.

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.