Telegram RegisterThe public register of Telegram
Telegram profile photo for Mirgorodtown

Channel

Mirgorodtown

@myrhorodtown

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 · Telegram's recommendations · Cite this entry

20,421subscribers

+842 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-1001675559903
TypeChannel
Username@myrhorodtown
DescriptionНайбільш цікаві новини міста! Чат для обговорень: https://t.me/+qj_ng-kVZIxhNmEy Шпалери для ваших смартфонів також тут😍
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 live14 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/myrhorodtown

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 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 2 other registered channels. 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
@novini_ukrtg/8747527 Aug 2026, 13:40 UTC@myrhorodtown/20143 · this entry27 Aug 2026, 14:33 UTC0.9854 minutes
@novini_ukrtg/918044 Nov 2026, 09:51 UTC@myrhorodtown/20994 · this entry4 Nov 2026, 10:50 UTC0.9758 minutes
@novini_ukrtg/9240015 Nov 2026, 17:23 UTC@myrhorodtown/21207 · this entry15 Nov 2026, 17:48 UTC0.9725 minutes
@novini_ukrtg/8649210 Aug 2026, 13:50 UTC@myrhorodtown/19951 · this entry10 Aug 2026, 14:52 UTC0.9562 minutes
@novini_ukrtg/8727624 Aug 2026, 13:52 UTC@myrhorodtown/20114 · this entry24 Aug 2026, 15:27 UTC0.951.6 hours
@novini_ukrtg/8715222 Aug 2026, 05:52 UTC@myrhorodtown/20083 · this entry22 Aug 2026, 06:27 UTC0.9535 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
@novini_ukrtg8 (8/8 hand-verifiable sample passed)0.9546 minutes@novini_ukrtg (8–0)
@poltavskaOVA6 (6/6 hand-verifiable sample passed)0.9972 seconds@poltavskaOVA (6–0)

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. 13 of the 13 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 166 comparable posts for this entry, running 5 August 2026 to 16 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_copy, last confirmed 17 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

19,35820,50219,93020,4217 August 202614 November 2026
64 measurements spanning 99 days, net +842. 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 19,186–20,674 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
14 Nov 2026, 12:4820,421-40
11 Nov 2026, 12:5720,461+6
9 Nov 2026, 17:5820,455+1
8 Nov 2026, 13:0720,454-12
6 Nov 2026, 09:2620,466-2
5 Nov 2026, 10:4520,468-6
4 Nov 2026, 08:4520,474+4
3 Nov 2026, 11:0620,470-3
2 Nov 2026, 07:3620,473+16
1 Nov 2026, 07:2920,457-7
31 Oct 2026, 10:4820,464-19
30 Oct 2026, 13:5520,483-19
28 Oct 2026, 18:3120,502+86
27 Oct 2026, 14:4620,416+52
26 Oct 2026, 16:5920,364+133
25 Oct 2026, 18:3720,231+7
24 Oct 2026, 20:0620,224+53
23 Oct 2026, 20:2620,171+34
22 Oct 2026, 23:0620,137+62
21 Oct 2026, 17:3020,075first reading

Engagement

531 posts held, back to 5 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 86 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
19.4%
avg views ÷ 20,421 subscribers
Avg views / post
3,950
254 posts measured
Reaction rate
0.52%
reactions ÷ views · ER floor
Posts in window
254
of 531 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 17 November 2026
Posts held531 (5 August 2026 – 17 November 2026)
Views total1,004,210
Reactions total5,219
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 16:23 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
≈8,320
Videos
≈1,600
Links
≈1,510

Lifetime counters from Telegram’s own channel header, read 17 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
14m 57s
Average length
45s

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

12,836 reactions across 531 posts, in 38 distinct kinds. The most used accounts for 25.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3,23925.2%
🤬2,51819.6%
🙏1,61312.6%
😭1,54912.1%
😢1,2269.55%
🤡5023.91%
🔥4513.51%
👍4323.37%
😡1621.26%
😁1521.18%
👎1260.982%
🤮1260.982%
🖕1240.966%
💔1070.834%
🤯790.615%
🤔580.452%
😱550.428%
👀410.319%
👏400.312%
😨370.288%
18 further kinds1991.55%

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 531 of the 531 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 12,836 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 531 most recent posts we hold, published 5 August 2026 to 17 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
1.32%
7 of 531 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
4,120
over 7 measured posts
Median views · rest
4,190
over 524 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. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Measured over the 531 most recent posts we hold, published 5 August 2026 to 17 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: 37 of 254 posts held from the last 30 days (14.6%) 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).

17 Nov 2026, 12:40 UTC≈2,400 views27 reactionsread 17 November 2026
Photo

❗️Оновлено графіки відключень на сьогодні. О 14:37 «Полтаваобленерго» оновили графіки погодинних відключень.

🤬17🖕5❤4😭1

17 Nov 2026, 11:56 UTC≈2,580 views10 reactionsread 17 November 2026

ВІДБІЙ ПОВІТРЯНОЇ ТРИВОГИ – МИРГОРОДСЬКИЙ РАЙОН!

❤9🙏1

17 Nov 2026, 10:35 UTC≈2,920 views16 reactionsread 17 November 2026

МИРГОРОДСЬКИЙ РАЙОН – ПОВІТРЯНА ТРИВОГА!

🤬15❤1

17 Nov 2026, 08:41 UTC≈3,440 views21 reactionsread 17 November 2026
Photo

❗️Оновлено графіки відключень на сьогодні. О 10:20 «Полтаваобленерго» оновили графіки погодинних відключень.

😡13🤬5❤3

17 Nov 2026, 07:04 UTC≈3,950 views62 reactionsread 17 November 2026
Photo

❗️Фото і відео розбитого Кримського мосту: автомобільна ділянка повністю обвалилася у воду, — монітори.

🔥42👏12❤7👌1

17 Nov 2026, 05:56 UTC≈3,850 views16 reactionsread 17 November 2026

ВІДБІЙ ПОВІТРЯНОЇ ТРИВОГИ – ПОЛТАВСЬКА ОБЛАСТЬ!

❤14🙏2

16 Nov 2026, 21:28 UTC≈4,950 views40 reactionsread 17 November 2026

Ракета на Лубни!

🙏22🤬16❤1🎉1

16 Nov 2026, 21:14 UTC≈4,940 views17 reactionsread 17 November 2026

ПОЛТАВСЬКА ОБЛАСТЬ – ПОВІТРЯНА ТРИВОГА!

🤬15❤2

16 Nov 2026, 20:42 UTC≈4,870 views14 reactionsread 17 November 2026
Photo

❗️Опубліковано графіки відключень на завтра, 17 листопада

❤12🖕2

16 Nov 2026, 19:04 UTC≈4,610 views12 reactionsread 17 November 2026

ВІДБІЙ ПОВІТРЯНОЇ ТРИВОГИ – ПОЛТАВСЬКА ОБЛАСТЬ!

❤11🙏1

16 Nov 2026, 18:45 UTC≈4,780 views34 reactionsread 17 November 2026
Photo

❗️На Різдво та Новий рік українцям не передбачені додаткові вихідні, — СЮГ Однак компанії можуть самі вирішувати, чи давати працівникам відпочинок.

🤡22😢6❤4🔥2

16 Nov 2026, 18:38 UTC≈4,500 views12 reactionsread 17 November 2026

ПОЛТАВСЬКА ОБЛАСТЬ – ПОВІТРЯНА ТРИВОГА!

🤬11❤1

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

@myrhorodtown 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
10 August 2026
Most recent edit
10 November 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.

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.

Миргород ЩДК?
@mirgorodlive · 26,131
#1
ПОЛТАВА НОВИНИ | СИРЕНА
@region_poltava_syrena · 191,973
#2
#SK# говорить🇺🇦
@SK_DM_SK · 191,904
#3
Миргород online📢
@mirgorod_online · 9,918
#4
🚨 Радар ракет 📡
@ua_radar_raket · 35,313
#5
Труха⚡️Полтава
@truexapoltava · 313,968
#6
Лачен пише
@lachentyt · 1,576,100
#7
🇺🇦 Віталій Дяківнич | Полтавська ОВА
@poltavskaOVA · 68,477
#8
Повітряні Сили ЗС України / Air Force of the Armed Forces of Ukraine
@kpszsu · 938,170
#9
Труха⚡️Україна
@truexanewsua · 3,165,345
#10
Тотальна Зрада
@totallzrada · 265,783
#11
Карта повітряних тривог 🇺🇦
@alarmua · 940,548
#12
Карта повітряних тривог ‼️ Вибухи ‼️ Ракети ‼️
@povitryanatrivogaaa · 728,432
#13
Миргородська міська рада/міський голова Сергій Соломаха
@myrgorod_rada · 4,390
#14
Миргород | News Hub
@myghorodnewshub · 1,943
#15
ППО радар | Напрямок ракет | Напрямок шахедів |
@mon1tor_ua · 264,080
#16
Реальний Київ | Украина
@kievreal1 · 1,550,018
#17
PVP.POLTAVA
@poltava_pvp · 109,735
#18
Суспільне Полтава
@suspilnepoltava · 55,916
#19
TLk News
@tlknewsua · 640,966
#20
УСЕ ПРО ВСЕ ВІДРАЗУ: КИЇВЩИНА , ПОЛТАВЩИНА
@useprovse1 · 31,656
#21
ТСН новини / ТСН.ua
@tch_channel · 729,418
#22
Куди летить? | Тривога
@radar_raketaa · 490,712
#23
Хуйовий Харків 🇺🇦 Хуевый Харьков
@huyovy_kharkiv · 463,751
#24
ППО Радар | Куди летить? | Напрямок шахедів та БпЛА
@radar_raket_Ukraine · 676 (as read 2 October 2026)
#25
Всевидящее ОКО (миллион подписчиков)
@oko_ua · 1,751
#26
Реальна Війна | Україна | Новини
@voynareal · 1,541,547
#27
Труха⚡️Київ
@truexakyiv · 972,266
#28
Україна Online: Новини | Політика
@UaOnlii · 1,536,697
#29
Киевский Движ
@k_dvizh · 470,936
#30
Полтава | Де Ракета ?🚀
@deraketapoltava · 14,180
#31
Полтавська ОВА | Новини
@poltavskaoda · 2,943
#32
🟢 Київ Новини | Live 24/7
@kyiv_novyny_24 · 237,542
#33
Типова Полтавщина🇺🇦
@typical_poltava · 16,956
#34
ОПЕРАТИВНИЙ ІНФОРМ
@operinform · 135,311
#35
НеТруха⚡️ Кременчук| Новини війни.
@kremikua · 52,311
#36
Повітряна Розвідка❗Тривога
@povitryana_rozvidka · 9,950
#37
Телеграмна служба новин - Україна
@tgsn_ua · 1,103,159
#38
🔊⚠️єРадар | Повітряна тривога | Ракетна небезпека
@eRadarrua · 411,004
#39
eyeukrainew
@eyeukrainew · 8
#40
Ukraine NOW
@UkraineNow · 404,377
#41
Ми - Полтава
@my_poltava_news · 10,111
#42
Тривога України | Радар
@kiev_nebo · 539,280
#43
monitoring
@monitorwarr · 85,150
#44
Фонтан за мільйон Полтава
@fontan1000000 · 23,720
#45
🔊Чому тривога?🚨| Повітряна тривога | Ракетна небезпека | єРадар |
@tryvoga_chomu · 271,642
#46
Вибухи та бавовна
@vybuhy_bavovna · 81,983
#47
AviMonitor
@avimonitor · 2,922
#48
ППО Полтавська область
@radarppopoltava · 5,262
#49
Де Ракета ?🚀 | Моніторинг
@deraketaua · 154,826
#50
Зміст. Полтава
@pl_zmist · 8,087
#51
Труха⚡️Кременчук
@kremenchugtruexa · 118,774
#52
Ветеран Доповідає
@veteran_dopoviday · 113,730
#53
🚀 РАКЕТА UA | Тривога України
@war_raketaua · 85,686
#54
МОЗАМБІК.МЕДІА: Лубни, Пирятин, Хорол, Гребінка, Оржиця
@mo3ambik · 36,615
#55
Полтавська окрема бригада територіальної оборони
@Poltava_116_brygada_TrO · 773
#56
Бабуся Світуся
@babusya_svitusya · 54,308
#57
Хуйова Полтава
@huyova_poltava · 12,021
#58
Ігор Терехов
@ihor_terekhov · 161,661
#59
ППО Полтавщина: Нічні мисливці
@ppo_Poltava · 34,333
#60
monitor
@war_monitor · 956,914
#61
INSIDER UA | Україна | Новини
@insiderukr · 2,141,667
#62
STERNENKO
@ssternenko · 879,121
#63
ЧЕТВЕРТА ЧЕРГА, 1 ПІДГРУПА💡 ПОЛТАВСЬКА ОБЛАСТЬ
@mo3ambik_gpv_4 · 15,463
#64
✙ Київ Оперативний | Kyiv Operative ✙
@kyivoperat · 337,929
#65
Гончаренко Центр Миргород
@GoncharenkoCentreMyrhorod · 1,286
#66
Що в повітрі? | Моніторинг
@monitoringwarua · 12,202
#67
ДРУГА ЧЕРГА, 1 ПІДГРУПА💡 ПОЛТАВСЬКА ОБЛАСТЬ
@mo3ambik_gpv_2 · 17,536
#68
ШОСТА ЧЕРГА, 1 ПІДГРУПА💡 ПОЛТАВСЬКА ОБЛАСТЬ
@mo3ambik_gpv_6 · 20,185
#69
Сіверські Націоналісти𓃟
@pivnichmmedia · 14,166
#70
Strategic Control
@strategicontrol · 27,117
#71
✈️Стратегічна авіація
@StrategicaviationT · 132,886
#72
Tracking
@the_first_online · 8,054
#73
(Графіки)Світло Четверта черга💡 Полтавська область.
@svitlo4s · 1,248
#74
ARTHUR
@pysarenkoarthur · 32,832
#75
(Графіки)Світло Шоста черга 💡Полтавська область.
@svitlo6s · 1,565
#76

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

Миргород ЩДК?
@mirgorodlive · 26,131
Telegram ranks this channel #1 of 70 here — alongside 69 others — read 15 September 2026
🚨 Радар ракет 📡
@ua_radar_raket · 35,313
Telegram ranks this channel #5 of 83 here — alongside 82 others — read 1 September 2026
ПОЛТАВА НОВИНИ | СИРЕНА
@region_poltava_syrena · 191,973
Telegram ranks this channel #18 of 85 here — alongside 84 others — read 11 August 2026
МОЗАМБІК.МЕДІА: Лубни, Пирятин, Хорол, Гребінка, Оржиця
@mo3ambik · 36,615
Telegram ranks this channel #29 of 71 here — alongside 70 others — read 4 September 2026
ППО Полтавщина: Нічні мисливці
@ppo_Poltava · 34,333
Telegram ranks this channel #32 of 71 here — alongside 70 others — read 4 September 2026
#SK# говорить🇺🇦
@SK_DM_SK · 191,904
Telegram ranks this channel #48 of 89 here — alongside 88 others — read 14 August 2026
УСЕ ПРО ВСЕ ВІДРАЗУ: КИЇВЩИНА , ПОЛТАВЩИНА
@useprovse1 · 31,656
Telegram ranks this channel #55 of 82 here — alongside 81 others — read 5 September 2026
Труха⚡️Полтава
@truexapoltava · 313,968
Telegram ranks this channel #58 of 82 here — alongside 81 others — read 10 August 2026

This channel appears in 8 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Mirgorodtown” (@myrhorodtown), 20,421 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/myrhorodtown.

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.