Telegram RegisterThe public register of Telegram
Telegram profile photo for ВГА Черниговской области

Channel

ВГА Черниговской области

@VGA_Chernigov

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

47subscribers

+0 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-1002016868486
TypeChannel
Username@VGA_Chernigov
Created9 January 2024 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live10 November 2026
Measurements held4
Confirmed unchanged5 times, most recently 10 November 2026
On Telegramt.me/VGA_Chernigov

Topic

International 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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. This entry also sits inside a group of 5 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.

No sample pairs were kept for this entry. The counts below were measured, but without the pairs there is nothing here for you to open and check, so treat the relationship as recorded rather than demonstrated.

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
@VGA_Odessa7 (7/7 hand-verifiable sample passed)0.9972 seconds@VGA_Odessa (5–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. None of the 1 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 9 comparable posts for this entry, running 1 April 2024 to 14 January 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 5 channels, the one whose matching posts we hold earliest is @VGA_Odessa. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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 5 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

474847.57 August 2026 — 47 subscribers10 August 2026 — 47 subscribers30 August 2026 — 48 subscribers10 October 2026 — 47 subscribers7 August 202610 October 2026
4 measurements spanning 64 days. 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 47–48 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Oct 2026, 22:3647-1
30 Aug 2026, 07:1448+1
10 Aug 2026, 13:3447no change
7 Aug 2026, 12:2747first reading

Engagement

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

Recent posts

14 Jan 2026, 16:13 UTC47 viewsread 10 August 2026
Forwarded from @VGA_KievPhoto

Уважаемые жители и гости города Киев! В целях вашей безопасности просим вас немедленно покинуть город. ВГА Киевской области

24 Sept 2025, 18:09 UTC126 viewsread 10 August 2026
Photo

24 сентября около 12:30 МСК ВС РФ ударом ОТРК "Искандер" успешно поразили полигон ВСУ в посёлке Гончаровский Черниговской области. Наше дело правое, враг будет разбит, Победа будет за нами! ВГА Черниговской области

9 Jun 2025, 10:48 UTC92 viewsread 10 August 2026
Forwarded from @VGA_Dnepropetrovsk

🇷🇺 Подразделения 90-й танковой дивизии группировки войск "Центр" вышли на западную границу ДНР и продолжают развивать наступление на территории Днепропетровской области. ВГА Днепропетровской области

9 Mar 2025, 13:54 UTC111 viewsread 10 August 2026
Forwarded from @VGA_Sumy

Подразделения группировки войск "Север" в ходе наступательных действий освободили хутор Новенькое в Сумской области. ВГА Сумской области

15 Nov 2024, 08:58 UTC≈1,590 viewsread 10 August 2026
Photo

Русские бойцы закрепили наши флаги в двух сёлах Новгород-Северского района Черниговской области. Наше дело правое, враг будет разбит, Победа будет за нами! ВГА Черниговской области

20 Sept 2024, 09:01 UTC≈1,520 viewsread 10 August 2026
Photo

Для жителей временно оккупированной Украины Присоединяйтесь к Русскому Сопротивлению! Не позволяйте нацистам разрушить Ваш дом и жизнь. Сражайтесь вместе с нами ради общей Победы и воссоединения нашего народа. Полная анонимность и достойное вознаграждение. Напиши нам, чтобы стать частью Русского Сопротивления: @oko_saurona2_robot ВГА Черниговской области

8 Jul 2024, 15:55 UTC≈1,090 viewsread 10 August 2026
Forwarded from @VGA_Kiev

Удары по военным объектам противника на территории временно оккупированной Киевской области будут продолжены Как мы сообщали в апреле, до холодов у жителей региона есть время покинуть зону возможных боевых действий. Все цели СВО будут достигнуты. Враг будет разбит, Победа будет за нами! ВГА Киевской области

17 Apr 2024, 10:37 UTC≈8,970 viewsread 10 August 2026
Photo

В результате успешного удара по месту дислокации украинских военных преступников в гостинице "Профсоюзная", временно оккупированный г. Чернигов, уничтожено по меньшей мере 14 врагов Более 60 — получили ранения и выведены из строя. У одного "гражданского" забыли замазать камуфляжные штаны и наколенники. Благодарим ДСНС Украины за объективный контроль результатов огневого поражения. Благодарим русских партизан за це…

1 Apr 2024, 17:58 UTC≈1,060 viewsread 10 August 2026
Forwarded from @VGA_OdessaPhoto

Граждане и гражданки Одессы! Координаты дислокации французских интервентов и украинских военных преступников можно аккуратно прислать в бот обратной связи @BattleSailorBot. Только потом держитесь от этого места подальше 😉 ВГА Одесской области

Showing the 11 most recent of 11 posts we hold for @VGA_Chernigov. 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

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.

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

“ВГА Черниговской области” (@VGA_Chernigov), 47 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/VGA_Chernigov.

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.