Telegram RegisterThe public register of Telegram
Telegram profile photo for Губернский МКР

Channel

Губернский МКР

@gubernsky_mkrn

Has discussion group

On this record: Growth · Engagement · Citations · Telegram's recommendations · Cite this entry

12,592subscribers

+33 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-1001435145805
TypeChannel
Username@gubernsky_mkrn
Created21 September 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded20 August 2026
Last confirmed live5 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/gubernsky_mkrn

Growth

12,55312,61812,585.57 August 2026 — 12,559 subscribers7 August 2026 — 12,562 subscribers8 August 2026 — 12,561 subscribers9 August 2026 — 12,562 subscribers10 August 2026 — 12,563 subscribers11 August 2026 — 12,570 subscribers12 August 2026 — 12,565 subscribers13 August 2026 — 12,568 subscribers14 August 2026 — 12,578 subscribers16 August 2026 — 12,571 subscribers17 August 2026 — 12,582 subscribers18 August 2026 — 12,579 subscribers19 August 2026 — 12,575 subscribers20 August 2026 — 12,553 subscribers20 August 2026 — 12,553 subscribers21 August 2026 — 12,566 subscribers23 August 2026 — 12,583 subscribers24 August 2026 — 12,618 subscribers25 August 2026 — 12,616 subscribers28 August 2026 — 12,615 subscribers28 August 2026 — 12,612 subscribers29 August 2026 — 12,609 subscribers30 August 2026 — 12,607 subscribers1 September 2026 — 12,601 subscribers2 September 2026 — 12,594 subscribers3 September 2026 — 12,587 subscribers5 September 2026 — 12,592 subscribers12,5927 August 20265 September 2026
27 measurements spanning 29 days, net +33. 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 12,543–12,628 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
5 Sept 2026, 09:3912,592+5
3 Sept 2026, 14:1812,587-7
2 Sept 2026, 04:1712,594-7
1 Sept 2026, 01:4612,601-6
30 Aug 2026, 22:1512,607-2
29 Aug 2026, 22:5512,609-3
28 Aug 2026, 21:3412,612-3
28 Aug 2026, 01:0812,615-1
25 Aug 2026, 18:1812,616-2
24 Aug 2026, 21:0812,618+35
23 Aug 2026, 07:3812,583+17
21 Aug 2026, 19:5612,566+13
20 Aug 2026, 18:1212,553no change
20 Aug 2026, 17:0312,553-22
19 Aug 2026, 14:5412,575-4
18 Aug 2026, 15:5312,579-3
17 Aug 2026, 15:1412,582+11
16 Aug 2026, 06:2612,571-7
14 Aug 2026, 19:3412,578+10
13 Aug 2026, 11:1312,568first reading

Engagement

No public post preview. We read this entry on 20 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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.

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.

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.

Парк Галицкого Краснодар
@park_galitskogo · 50,040
Telegram ranks this channel #15 of 96 here — alongside 95 others — read 25 August 2026
Куда Пойти В Краснодаре
@event_of_krasnodar · 39,434
Telegram ranks this channel #33 of 94 here — alongside 93 others — read 30 August 2026
Краснодар Новости Bigbro_krd
@bigbro_krd · 32,944
Telegram ranks this channel #73 of 92 here — alongside 91 others — read 4 September 2026
Новости Краснодара и Края (Майкоп / Адыгея)
@krasnodar_chp23 · 77,141
Telegram ranks this channel #76 of 79 here — alongside 78 others — read 19 August 2026
ЧП Краснодара и края 🔞
@chpkrasnodara · 289,815
Telegram ranks this channel #78 of 89 here — alongside 88 others — read 10 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 5 September 2026 — this entry's latest reading, not the date you are reading this.

“Губернский МКР” (@gubernsky_mkrn), 12,592 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/gubernsky_mkrn.

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.