Telegram RegisterThe public register of Telegram
Telegram profile photo for Миргород ЩДК?

Channel

Миргород ЩДК?

@mirgorodlive

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Telegram's recommendations · Cite this entry

25,971subscribers

+1,564 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001790421933
TypeChannel
Username@mirgorodlive
DescriptionНадіслати новину(реклама)- @Alex080819 Миргород чат - @chatmirgo Всі питання відносно чату ЩДК - @dobrunya29 Спільнота 18+
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 live10 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/mirgorodlive

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 6 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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
@mirgorodlive/39713 · this entry12 Aug 2026, 12:13 UTC@hommirgorod/205712 Aug 2026, 12:13 UTC1.00under a minute
@mirgorodlive/39863 · this entry19 Aug 2026, 14:08 UTC@hommirgorod/206719 Aug 2026, 14:08 UTC1.00under a minute
@hommirgorod/216221 Oct 2026, 14:00 UTC@mirgorodlive/41624 · this entry21 Oct 2026, 14:01 UTC1.00under a minute
@mirgorodlive/41691 · this entry23 Oct 2026, 10:20 UTC@hommirgorod/216423 Oct 2026, 10:21 UTC1.00under a minute
@typove_dubno/3079410 Aug 2026, 09:39 UTC@mirgorodlive/39644 · this entry10 Aug 2026, 11:05 UTC1.0086 minutes
@mirgorodlive/39713 · this entry12 Aug 2026, 12:13 UTC@typove_dubno/3083312 Aug 2026, 12:16 UTC1.004 minutes
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
@hommirgorod20 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (16–4)
@typove_dubno7 (7/7 hand-verifiable sample passed)1.0013 minutesthis entry (4–3)
@ok_kremen6 (6/6 hand-verifiable sample passed)0.957 minutes@ok_kremen (5–1)
@hellonovograd6 (6/6 hand-verifiable sample passed)0.9924 minuteseven
@Voiennyi_Kostopil5 (5/5 hand-verifiable sample passed)1.003.9 hoursthis entry (4–1)
@truexapoltava5 (5/5 hand-verifiable sample passed)0.9638 hours@truexapoltava (4–1)

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. 17 of the 17 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 561 comparable posts for this entry, running 6 August 2026 to 10 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @hommirgorod. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, 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 2 registered channels linked by matching posts. 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

24,38625,97125,178.57 August 202610 November 2026
64 measurements spanning 95 days, net +1,564. 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 24,148–26,209 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
10 Nov 2026, 00:0925,971+50
8 Nov 2026, 12:5025,921+49
7 Nov 2026, 07:5925,872+83
6 Nov 2026, 06:3925,789+63
5 Nov 2026, 03:0925,726+59
4 Nov 2026, 04:0825,667+98
3 Nov 2026, 02:5025,569+81
2 Nov 2026, 02:3725,488+73
1 Nov 2026, 00:2925,415+24
30 Oct 2026, 20:5625,391+23
29 Oct 2026, 19:5825,368+13
28 Oct 2026, 23:0525,355+26
27 Oct 2026, 23:2725,329+28
26 Oct 2026, 21:5625,301+30
25 Oct 2026, 20:3825,271+9
24 Oct 2026, 23:1625,262+13
23 Oct 2026, 20:4725,249+29
22 Oct 2026, 19:5825,220+10
21 Oct 2026, 18:0625,210+27
20 Oct 2026, 13:0625,183first reading

Engagement

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

ERR · 30 days
27.3%
avg views ÷ 25,971 subscribers
Avg views / post
7,090
716 posts measured
Reaction rate
0.633%
reactions ÷ views · ER floor
Posts in window
716
of 1,666 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 11 November 2026
Posts held1,666 (6 August 2026 – 11 November 2026)
Views total5,075,912
Reactions total32,144
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Nov 2026, 08:55 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
≈11,800
Videos
≈1,540
Links
≈18,300

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

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

43,914 reactions across 999 posts, in 68 distinct kinds. The most used accounts for 33.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏14,58433.2%
🤬9,24321.0%
❤7,29016.6%
👍2,5655.84%
🖕1,9684.48%
😢1,8004.10%
🤡1,0282.34%
👎1,0172.32%
😁5441.24%
😱5171.18%
😭5021.14%
🤯3730.849%
🤮2620.597%
💩2380.542%
⚡1990.453%
🤣1920.437%
🤔1390.317%
🥴1160.264%
👀1010.23%
😨1000.228%
48 further kinds1,1362.59%

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 43,914 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 29 September 2026 to 11 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: 38 of 716 posts held from the last 30 days (5.31%) 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).

11 Nov 2026, 08:47 UTC≈1,200 views10 reactionsread 11 November 2026

⚡️ У Миргороді просіла напруга Зараз напруга в мережі — близько 170 В 😬 Перевірте свої стабілізатори та техніку, особливо чутливу до перепадів напруги. Миргород ЩДК? | Підписатись

😢4❤2⚡1👏1🤬1😁1

11 Nov 2026, 08:34 UTC≈2,100 views21 reactionsread 11 November 2026

🟡 Миргородський район — повітряна тривога, жовтий рівень

🙏10🤬9🤯2

11 Nov 2026, 08:24 UTC≈3,160 views29 reactionsread 11 November 2026

Поки що ✅ Миргород ЩДК? | Підписатись

🙏24👍4🤝1

11 Nov 2026, 08:21 UTC≈3,320 views42 reactionsread 11 November 2026

❗️Полтава під ворожою атакою. Загроза триває. Миргород ЩДК? | Підписатись

🙏25🤬13❤1😁1😢1😨1

11 Nov 2026, 08:19 UTC≈3,670 views32 reactionsread 11 November 2026

Гучно в області. Миргород ЩДК? | Підписатись

🙏29❤1🤬1😨1

11 Nov 2026, 08:13 UTC≈4,100 views43 reactionsread 11 November 2026

"Бандеролі" в напрямку Полтави. - ПС Миргород ЩДК? | Підписатись

🙏35❤4🤬4

11 Nov 2026, 08:10 UTC≈4,280 views49 reactionsread 11 November 2026

Гучно в області. Миргород ЩДК? | Підписатись

🙏46❤2🤬1

11 Nov 2026, 08:09 UTC≈4,380 views30 reactionsread 11 November 2026

🔴 Миргородський район — повітряна тривога, червоний рівень

🙏20🤬9❤1

11 Nov 2026, 08:01 UTC≈4,440 views38 reactionsread 11 November 2026

Група реактивних БпЛА з Харківщини - на Полтавщину, курсом на Полтаву. - ПС Миргород ЩДК? | Підписатись

🙏24🤬8❤4👌1👎1

11 Nov 2026, 07:41 UTC≈5,030 views23 reactionsread 11 November 2026

🟢 Миргородський район — відбій повітряної тривоги

🙏18❤5

11 Nov 2026, 07:27 UTC≈5,520 views30 reactionsread 11 November 2026
Photo

Обнова. Для черг 5.2 — збільшили відключення. Для черг 1.2, 2.2, 3.1, 3.2, 4.1, 4.2, 5.1 — зменшили відключення. Миргород ЩДК? | Підписатись

❤22👎5⚡1👍1🖕1

11 Nov 2026, 07:15 UTC≈5,380 views34 reactionsread 11 November 2026

🔴 Миргородський район — повітряна тривога, червоний рівень

🙏25🤬7❤1👎1

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

@mirgorodlive edited 2 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
10 November 2026
Most recent edit
10 November 2026

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

11 Oct 2026, 14:25 UTCAnonymous Poll573 voters

💡 Чи буде дотримано енергетичного перемир’я?

  1. Так3%
  2. Ні74%
  3. Час покаже26%

The shares total 103%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 29 September 2026 to 11 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

Named by

Channels on the register whose posts name this channel's handle.

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.

Mirgorodtown
@myrhorodtown · 20,461
#1
ПОЛТАВА НОВИНИ | СИРЕНА
@region_poltava_syrena · 192,320
#2
Миргород online📢
@mirgorod_online · 9,944
#3
Труха⚡️Полтава
@truexapoltava · 313,409
#4
Миргород Тутешні | Світло
@mirgorodsvitlo · 4,386
#5
Миргород | News Hub
@myghorodnewshub · 1,942
#6
Карта повітряних тривог 🇺🇦
@alarmua · 941,278
#7
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 729,798
#8
Полтава | Де Ракета ?🚀
@deraketapoltava · 14,253
#9
ППО Полтавщина: Нічні мисливці
@ppo_Poltava · 34,323
#10
УСЕ ПРО ВСЕ ВІДРАЗУ: КИЇВЩИНА , ПОЛТАВЩИНА
@useprovse1 · 31,730
#11
Око України - Захід.
@eyeukrainew · 26,118 (as read 15 September 2026)
#12
Вибухи та бавовна
@vybuhy_bavovna · 82,144
#13
Тривога України | Радар
@kiev_nebo · 540,698
#14
ППО Полтавська область
@radarppopoltava · 5,224
#15
Полтавська ОВА | Новини
@poltavskaoda · 2,941
#16
🔊Чому тривога?🚨| Повітряна тривога | Ракетна небезпека | єРадар |
@tryvoga_chomu · 272,338
#17
Типова Полтавщина🇺🇦
@typical_poltava · 17,108
#18
ukrainesradar
@ukrainesradar · 1
#19
ПІВНІЧ
@pivnic · 2,968
#20
Ми - Полтава
@my_poltava_news · 10,135
#21
Poltava intelligence
@Poltava_intelligence · 3,873
#22
Бабуся Світуся
@babusya_svitusya · 54,491
#23
Хуйова Полтава
@huyova_poltava · 11,957
#24
💥ОБЕРЕЖНО ВИБУХИ l НОВИНИ l РАДАР | СВІТЛО
@oberezhnovibuhi · 27,937
#25
VPLT
@v_plt · 26,149
#26
🇺🇦Радар News | Моніторинг ✙
@ua_radar_news · 1,331
#27
ШОСТА ЧЕРГА, 1 ПІДГРУПА💡 ПОЛТАВСЬКА ОБЛАСТЬ
@mo3ambik_gpv_6 · 20,116
#28
#SK# говорить🇺🇦
@SK_DM_SK · 191,986
#29
Миргородська міська рада/міський голова Сергій Соломаха
@myrgorod_rada · 4,385
#30
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 939,064
#31
Лачен пише
@lachentyt · 1,579,508
#32
🇺🇦 Віталій Дяківнич | Полтавська ОВА
@poltavskaOVA · 68,585
#33
Труха⚡️Україна
@truexanewsua · 3,168,131
#34
Тотальна Зрада
@totallzrada · 266,865
#35
🚨 Радар ракет 📡
@ua_radar_raket · 35,413
#36
Гончаренко Центр Миргород
@GoncharenkoCentreMyrhorod · 1,271
#37
ППО радар | Напрямок ракет | Напрямок шахедів |
@mon1tor_ua · 264,047
#38
monitor
@war_monitor · 958,987
#39
Куди летить? | Тривога
@radar_raketaa · 492,325
#40
PVP.POLTAVA
@poltava_pvp · 110,194
#41
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 410,896
#42
НеТруха⚡️ Кременчук| Новини війни.
@kremikua · 52,277
#43
Андрій Смолій
@smolii_ukraine · 523,719
#44
ЧЕТВЕРТА ЧЕРГА, 1 ПІДГРУПА💡 ПОЛТАВСЬКА ОБЛАСТЬ
@mo3ambik_gpv_4 · 15,468
#45
Суспільне Полтава
@suspilnepoltava · 56,037
#46
ОПЕРАТИВНИЙ ІНФОРМ
@operinform · 135,911
#47
Фонтан за мільйон Полтава
@fontan1000000 · 23,627
#48
ППО Радар | Куди летить? | Напрямок шахедів та БпЛА
@radar_raket_Ukraine · 675 (as read 15 September 2026)
#49
ДРУГА ЧЕРГА, 1 ПІДГРУПА💡 ПОЛТАВСЬКА ОБЛАСТЬ
@mo3ambik_gpv_2 · 17,503
#50
✈️Стратегічна авіація
@StrategicaviationT · 132,792
#51
Лубни, Пирятин,Хорол, Гребінка,Оржиця, Миргород
@lubnya12 · 4,170
#52
ВОНА хаб_Миргород
@weso_myrhorod · 221
#53
Полтава культурна
@kulturnapoltava · 1,065
#54
ШИШАЧЧИНА
@shyshaky · 2,744
#55
Ветеран Доповідає
@veteran_dopoviday · 114,352
#56
Харківський Boroda
@Kharkiv_Boroda · 380
#57
🇺🇦НАШЕ ППО 🚀Де Ракета|Де Шахед📡
@Nashee_PPO · 33,321
#58
АСОЦІАЦІЯ ФУТБОЛУ ПОЛТАВЩИНИ
@afp_football · 1,021
#59
ПОЛТАВА | ПОЛТАВСЬКИЙ ГІДРОМЕТЦЕНТР
@pgdpoltava · 1,421
#60
Сіверські Націоналісти𓃟
@pivnichmmedia · 14,227
#61
Що в повітрі? | Моніторинг
@monitoringwarua · 12,112
#62
𝙥𝙪𝙨𝙨𝙮 𝙝𝙤𝙧𝙤𝙨𝙘𝙤𝙥𝙚
@rihrsk · 72
#63
vityapump
@vityapump · 6,092
#64
Tracking
@the_first_online · 8,077
#65
mumarr music 🍒🐯
@mumarrr_muzic · 386 (as read 15 September 2026)
#66
Flekman.live
@flekmanlive · 306
#67
цілуй.
@tsilyou · 5,649
#68
Ghost of music 🎵
@Ghostofmusicl · 1,178
#69
Где повестки Полтава?
@agendaPoltava · 224,529
#70

Read from Telegram’s recommendation API, most recently 15 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.

Mirgorodtown
@myrhorodtown · 20,461
Telegram ranks this channel #1 of 76 here — alongside 75 others — read 2 October 2026
ППО Полтавщина: Нічні мисливці
@ppo_Poltava · 34,323
Telegram ranks this channel #6 of 71 here — alongside 70 others — read 4 September 2026
ПОЛТАВА НОВИНИ | СИРЕНА
@region_poltava_syrena · 192,320
Telegram ranks this channel #24 of 85 here — alongside 84 others — read 11 August 2026
🚨 Радар ракет 📡
@ua_radar_raket · 35,413
Telegram ranks this channel #64 of 83 here — alongside 82 others — read 1 September 2026
Новини України | Новости Украины
@novostyukraine · 80,498
Telegram ranks this channel #86 of 86 here — alongside 85 others — read 26 August 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“Миргород ЩДК?” (@mirgorodlive), 25,971 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/mirgorodlive.

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.