Telegram RegisterThe public register of Telegram
Telegram profile photo for Чатик Покровки для нормальных

Supergroup

Чатик Покровки для нормальных

@pokrovka_chat

Has discussion group

On this record: Growth · Engagement · Citations · Cite this entry

7,610members

-131 since we began measuring on 6 August 2026

105 online right now

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

Register entry

Telegram ID-1001230671952
TypeSupergroup
Username@pokrovka_chat
Created27 August 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded25 August 2026
Last confirmed live6 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/pokrovka_chat

Growth

7,6107,8497,729.56 August 2026 — 7,741 members7 August 2026 — 7,742 members10 August 2026 — 7,762 members13 August 2026 — 7,826 members16 August 2026 — 7,849 members20 August 2026 — 7,828 members24 August 2026 — 7,745 members25 August 2026 — 7,745 members27 August 2026 — 7,715 members29 August 2026 — 7,683 members2 September 2026 — 7,649 members6 September 2026 — 7,610 members6 August 20266 September 2026
12 measurements spanning 31 days, net -131. 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 7,574–7,885 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
6 Sept 2026, 03:417,610-39
2 Sept 2026, 05:527,649-34
29 Aug 2026, 22:557,683-32
27 Aug 2026, 06:087,715-30
25 Aug 2026, 21:587,745no change
24 Aug 2026, 00:367,745-83
20 Aug 2026, 00:417,828-21
16 Aug 2026, 18:267,849+23
13 Aug 2026, 12:347,826+64
10 Aug 2026, 09:327,762+20
7 Aug 2026, 04:477,742+1
6 Aug 2026, 10:307,741first reading

Engagement

No public post preview. We read this entry on 25 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.

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

“Чатик Покровки для нормальных” (@pokrovka_chat), 7,610 members as measured 6 September 2026. Telegram Register, tgregister.com/channel/pokrovka_chat.

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.