Telegram RegisterThe public register of Telegram
Telegram profile photo for Моя Полтава

Channel

Моя Полтава

@poltava91

On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry

58,577subscribers

-150 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001720513683
TypeChannel
Username@poltava91
Description⚡️ Важливі та актуальні новини Полтави Посилання для друзів - https://t.me/+dqFw6P6qVvAwNzI0 з реклами @alex_reklama_ua
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 November 2026
Measurements held62
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/poltava91

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 9 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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
@poltava91/43601 · this entry10 Sept 2026, 16:54 UTC@chernigov_chernigiv1/4510010 Sept 2026, 17:00 UTC1.005 minutes
@chernigov_chernigiv1/4795718 Oct 2026, 16:17 UTC@poltava91/45744 · this entry18 Oct 2026, 16:17 UTC1.00under a minute
@poltava91/43554 · this entry9 Sept 2026, 16:03 UTC@chernigov_chernigiv1/450309 Sept 2026, 16:35 UTC0.9531 minutes
@chernigov_chernigiv1/4509510 Sept 2026, 15:04 UTC@poltava91/43600 · this entry10 Sept 2026, 15:04 UTC0.84under a minute
@chernigov_chernigiv1/4764114 Oct 2026, 16:08 UTC@poltava91/45427 · this entry14 Oct 2026, 16:08 UTC0.83under 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
@chernigov_chernigiv16 (5/6 hand-verifiable sample passed)0.9272 secondsthis entry (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. 2 of the 2 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 1,086 comparable posts for this entry, running 7 August 2026 to 12 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_source, last confirmed 13 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

58,38558,86758,62658,5777 August 202611 November 2026
62 measurements spanning 96 days, net -150. 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 58,313–58,939 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)SubscribersChange
11 Nov 2026, 16:0158,577-30
9 Nov 2026, 23:0958,607+31
8 Nov 2026, 17:4058,576-29
7 Nov 2026, 07:5058,605-8
6 Nov 2026, 06:1758,613-19
5 Nov 2026, 03:3758,632-46
4 Nov 2026, 06:1658,678+10
3 Nov 2026, 04:2658,668+18
2 Nov 2026, 00:3758,650-2
31 Oct 2026, 22:4858,652+28
31 Oct 2026, 00:1158,624+33
30 Oct 2026, 03:0958,591+28
29 Oct 2026, 03:0758,563-6
28 Oct 2026, 03:2558,569-19
27 Oct 2026, 05:1958,588-5
26 Oct 2026, 04:0958,593+10
25 Oct 2026, 04:5858,583-6
24 Oct 2026, 07:1058,589-8
23 Oct 2026, 07:3658,597+1
22 Oct 2026, 05:0758,596first reading

Engagement

3,287 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 197 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
10.4%
avg views ÷ 58,577 subscribers
Avg views / post
6,120
1,071 posts measured
Reaction rate
0.581%
reactions ÷ views · ER floor
Posts in window
1,071
of 3,287 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 November 2026
Posts held3,287 (7 August 2026 – 13 November 2026)
Views total6,551,300
Reactions total38,060
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 11:10 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
≈18,600
Videos
≈2,640
Links
≈40,700

Lifetime counters from Telegram’s own channel header, read 13 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
28m 43s
Average length
33s

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

35,824 reactions across 998 posts, in 8 distinct kinds. The most used accounts for 41.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏14,82341.4%
🤬13,48537.6%
❤4,01011.2%
👍1,1903.32%
😱1,0522.94%
😁5921.65%
👎4491.25%
🔥2230.622%

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 1,000 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 35,824 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 16 October 2026 to 13 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.

Advertising

Ad load
0.2%
2 of 1,000 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
6,060
over 2 measured posts
Median views · rest
6,590
over 998 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 16 October 2026 to 13 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 1,028 of 1,071 posts held from the last 30 days (96.0%) 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).

13 Nov 2026, 11:01 UTC612 views8 reactionsread 13 November 2026

БпЛА на Глобине ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

🤬5🙏3

13 Nov 2026, 10:56 UTC≈1,220 views14 reactionsread 13 November 2026
Photo

🚨 Чоловік загинув у ДТП на Полтавщині Біля села Почаївка автомобіль врізався у відбійник. Після аварії водій і пасажирка вийшли на дорогу, де чоловіка збило інше авто. 49-річний чоловік помер у кареті швидкої, 57-річну пасажирку госпіталізували. ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

😱13👍1

13 Nov 2026, 10:42 UTC≈2,720 views27 reactionsread 13 November 2026

❗️Вибухова хвиля пошкодила будинок на Полтавщині через падіння БпЛА У Піщанській громаді Кременчуцького району вибило шибки в приватному будинку. Інформації про постраждалих немає. ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

🙏14😱6🤬5👍1😁1

13 Nov 2026, 10:37 UTC≈3,130 views18 reactionsread 13 November 2026

🚨 ПОЛТАВСЬКА ОБЛАСТЬ - ОГОЛОШЕНА ПОВІТРЯНА ТРИВОГА Загроза БпЛА ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

🙏10🤬6👍1👎1

13 Nov 2026, 10:13 UTC≈4,030 views18 reactionsread 13 November 2026
Photo

🚨 Чоловік потрапив під колеса вантажівки на трасі Полтава – Кременчук ДТП сталася поблизу села Бутенки. Водій вантажівки наїхав на пішохода. Постраждалого з травмами госпіталізували. ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

😱12🙏5🔥1

13 Nov 2026, 10:03 UTC≈4,240 views10 reactionsread 13 November 2026

❎ ПОЛТАВСЬКА ОБЛАСТЬ - ВІДБІЙ ТРИВОГИ ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

🙏7❤2👎1

13 Nov 2026, 09:31 UTC≈5,440 views70 reactionsread 13 November 2026

❗️Вибух у Кременчуці ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

🤬38🙏30❤1👍1

13 Nov 2026, 09:23 UTC≈6,000 views44 reactionsread 13 November 2026

Бандероль на Кобеляки 2х Бандеролі на Велику Багачку ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

🙏27🤬17

13 Nov 2026, 09:17 UTC≈6,450 views41 reactionsread 13 November 2026

Бандероль курсом на Машівкку 2х Бандеролі курсом на Опішню ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

🤬22🙏14❤2😱2👍1

13 Nov 2026, 09:14 UTC≈6,650 views39 reactionsread 13 November 2026

Бандероль на Хорол Бандероль на Чутове ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

🙏20🤬16❤1👍1😱1

13 Nov 2026, 09:14 UTC≈6,310 views34 reactionsread 13 November 2026

Бандероль на Кременчук ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

🙏21🤬11👍1👎1

13 Nov 2026, 09:12 UTC≈6,400 views17 reactionsread 13 November 2026
Photo

🌫️ Густий туман накриє Полтавщину Вдень очікується туман, видимість на дорогах становитиме 200–500 метрів. Оголошено жовтий рівень небезпечності. ㅤ Надіслати новину @mypoltava_bot 👉ПІДПИСАТИСЯ

😱8🙏7❤2

Showing the 12 most recent of 3,287 posts we hold for @poltava91. 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

@poltava91 edited 6 posts 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
1 September 2026
Most recent edit
3 October 2026

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

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

“Моя Полтава” (@poltava91), 58,577 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/poltava91.

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.