Telegram RegisterThe public register of Telegram
Telegram profile photo for Прилуки 🇺🇦

Channel

Прилуки 🇺🇦

@priluki_ru

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

506subscribers

-9 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-1001770933057
TypeChannel
Username@priluki_ru
Created6 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live10 November 2026
Measurements held9
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/priluki_ru

Topic

Local community — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 4 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
@priluki_ru/677 · this entry13 Jan 2023, 10:39 UTC@novgorodseversky_ru/68213 Jan 2023, 10:39 UTC1.00under a minute
@novgorodseversky_ru/68516 Jan 2023, 14:18 UTC@priluki_ru/681 · this entry16 Jan 2023, 14:18 UTC1.00under a minute
@priluki_ru/683 · this entry16 Jan 2023, 15:24 UTC@novgorodseversky_ru/68716 Jan 2023, 15:24 UTC1.00under a minute
@priluki_ru/686 · this entry18 Jan 2023, 08:27 UTC@novgorodseversky_ru/69118 Jan 2023, 08:27 UTC1.00under a minute
@priluki_ru/677 · this entry13 Jan 2023, 10:39 UTC@nezhin_ru/68513 Jan 2023, 10:40 UTC1.00under a minute
@priluki_ru/683 · this entry16 Jan 2023, 15:24 UTC@nezhin_ru/68916 Jan 2023, 15:25 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
@novgorodseversky_ru9 (8/8 hand-verifiable sample passed)1.00under a minute@novgorodseversky_ru (5–4)
@nezhin_ru8 (8/8 hand-verifiable sample passed)1.00under a minuteeven
@nosovka_ru8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (5–3)

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. None of the 5 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 13 comparable posts for this entry, running 13 January 2023 to 14 February 2023. 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 4 channels, the one whose matching posts we hold earliest is @nosovka_ru. That is a statement about our reading window, not a claim of authorship.

Recorded under the key 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 4 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

506515510.57 August 2026 — 515 subscribers8 August 2026 — 515 subscribers15 August 2026 — 513 subscribers22 August 2026 — 511 subscribers12 September 2026 — 513 subscribers6 October 2026 — 512 subscribers14 October 2026 — 511 subscribers21 October 2026 — 508 subscribers10 November 2026 — 506 subscribers7 August 202610 November 2026
9 measurements spanning 95 days, net -9. 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 505–516 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Nov 2026, 08:59506-2
21 Oct 2026, 03:06508-3
14 Oct 2026, 03:18511-1
6 Oct 2026, 10:37512-1
12 Sept 2026, 20:19513+2
22 Aug 2026, 03:52511-2
15 Aug 2026, 09:38513-2
8 Aug 2026, 04:04515no change
7 Aug 2026, 19:57515first reading

Engagement

19 posts held, back to 13 January 2023 — 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 page 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 19 posts for this entry, the most recent from 14 February 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
34s
Average length
17s

Measured directly from 2 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.

Recent posts

14 Feb 2023, 08:40 UTC≈8,860 viewsread 8 August 2026
Photo

На железнодорожной станции в Прилуках горел поезд Прошедшей ночью на станции в Прилуках произошло возгорание поезда — огнем повреждено электрооборудование и внутренняя облицовка кабины машиниста. Причины возгорания неизвестны, их устанавливают специалисты.

30 Jan 2023, 09:47 UTC≈4,980 viewsread 8 August 2026
Forwarded from @chernigov_ruPhoto

Черниговский паралимпиец Дмитрий Суярко завоевал «бронзу» на Чемпионате мира по лыжным гонкам Наш земляк занял почетное третье место на Чемпионате мира по лыжным гонкам и биатлону среди спортсменов с нарушенным опорно-двигательным аппаратом и проблемами со зрением. Отметим, что сейчас соревнования проходят в швейцарском городе Эстерсунд.

24 Jan 2023, 13:21 UTC≈4,650 viewsread 8 August 2026

🟢 Воздушная тревога в Черниговской области отменена

24 Jan 2023, 12:38 UTC≈4,640 viewsread 8 August 2026

❗️В Черниговской области объявлена воздушная тревога

23 Jan 2023, 13:43 UTC≈4,530 viewsread 8 August 2026
Forwarded from @chernigov_ruPhoto

Павла Халимона уволили с должности заместителя председателя фракции «Слуга народа» после расследования СМИ Сначала в свет вышла публикация в СМИ с расследованием о том, что Халимон приобрел дом в центре Киева по заниженной цене, а затем глава фракции заявляет об увольнении чиновника. «Если ты народный депутат и у тебя есть пару лишних миллионов гривен, то ты должен помочь своей стране — это твой долг», — прокоммент…

23 Jan 2023, 10:42 UTC≈1,740 viewsread 8 August 2026

❗️Внимание❗️ Сегодня с 12:00 до 16:00 вблизи Шестовицы будут слышны контролируемы взрывы — уничтожение боеприпасов.

19 Jan 2023, 08:17 UTC≈1,690 viewsread 8 August 2026

❗️В Черниговской области объявлена воздушная тревога

18 Jan 2023, 13:39 UTC≈1,700 viewsread 8 August 2026

Исполняющим обязанности министра внутренних дел назначили Игоря Клименко Кабмин Украины назначил главу нацполиции Игоря Клименко на должность министра внутренних дел после сегодняшней гибели Дениса Монастырского в результате крушения вертолета в Броварах.

18 Jan 2023, 12:35 UTC≈1,680 viewsread 8 August 2026

❗️В Чернигове и области ожидается усиление ветра Черниговский областной центр по гидрометеорологии предупреждает местных жителей о желтом уровне опасности. Сегодня, 18 янвая, в регионе ожидается усиление ветра до 15-20 м/с. Будьте аккуратны!

18 Jan 2023, 09:40 UTC≈1,670 viewsread 8 August 2026
Forwarded from @chernigov_ruVideo

Кадры с места крушения вертолета в Броварах — погибло руководство МВД В сети начали распространяться кадры с места падения вертолета в одном из жилых кварталов. На месте происшествия экстренные службы почти закончили ликвидировать последствия аварии. Информация о пострадавших постоянно обновляется. Теперь известно, что в результате крушения, погибли 18 человек, включая руководство МВД, которое летело на вертолете о…

18 Jan 2023, 08:27 UTC776 viewsread 8 August 2026

❗️В Киевской области погибло 16 человек — среди них двое детей В результате крушения вертолета в Броварах погибло 16 человек — из них два ребенка. Сейчас в больнице находятся 22 человека, среди которых 10 детей. Отметим, что на борту был глава ведомства Денис Монастырский и его заместитель Евгений Енин.

18 Jan 2023, 07:36 UTC760 viewsread 8 August 2026
Forwarded from @chernigov_ruVideo

В Киевской области вертолет потерпел крушение рядом с детским садом Сегодня в Броварах произошла страшная ситуация — вертолет сотрудников МЧС упал на многоквартирный дом, совсем рядом с детским садом. Уже появилась информация об одном погибшем и пяти пострадавших. На данный момент специалисты уже приступили к расследованию. По предварительной информации, падение вертолета — результат работы украинской ПВО.

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

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

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.

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.

“Прилуки 🇺🇦” (@priluki_ru), 506 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/priluki_ru.

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.