Telegram RegisterThe public register of Telegram
Telegram profile photo for ПРОБУЖДЕНИЕ СИЛЫ

Bot

ПРОБУЖДЕНИЕ СИЛЫ

@potokizobot

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

42,884monthly users

+7,036 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 ID8294321299
TypeBot
Username@potokizobot
First recorded12 August 2026
Last confirmed live17 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/potokizobot

Growth

35,84842,88439,3667 August 2026 — 35,848 monthly users9 August 2026 — 37,915 monthly users10 August 2026 — 39,717 monthly users11 August 2026 — 40,833 monthly users12 August 2026 — 40,833 monthly users13 August 2026 — 42,423 monthly users14 August 2026 — 42,744 monthly users16 August 2026 — 42,708 monthly users17 August 2026 — 42,884 monthly users7 August 202617 August 2026
9 measurements spanning 10 days, net +7,036. 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 34,793–43,939 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
17 Aug 2026, 11:5342,884+176
16 Aug 2026, 01:5842,708-36
14 Aug 2026, 09:3742,744+321
13 Aug 2026, 02:4642,423+1,590
12 Aug 2026, 20:2240,833no change
11 Aug 2026, 02:2840,833+1,116
10 Aug 2026, 04:5739,717+1,802
9 Aug 2026, 03:5137,915+2,067
7 Aug 2026, 05:1535,848first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

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

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

“ПРОБУЖДЕНИЕ СИЛЫ” (@potokizobot), 42,884 monthly users as measured 17 August 2026. Telegram Register, tgregister.com/channel/potokizobot.

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.