Telegram RegisterThe public register of Telegram
Telegram profile photo for Фотушка — фотосессии с ИИ в 1 клик

Bot

Фотушка — фотосессии с ИИ в 1 клик

@fotushka_bot

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

16,618monthly users

-5,494 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 ID7877266877
TypeBot
Username@fotushka_bot
First recorded16 August 2026
Last confirmed live26 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/fotushka_bot

Growth

16,61822,32619,4727 August 2026 — 22,112 monthly users9 August 2026 — 22,026 monthly users10 August 2026 — 22,326 monthly users11 August 2026 — 19,736 monthly users12 August 2026 — 18,949 monthly users14 August 2026 — 19,133 monthly users16 August 2026 — 19,218 monthly users16 August 2026 — 19,218 monthly users17 August 2026 — 19,229 monthly users19 August 2026 — 17,238 monthly users20 August 2026 — 16,823 monthly users21 August 2026 — 16,790 monthly users22 August 2026 — 16,898 monthly users24 August 2026 — 16,995 monthly users25 August 2026 — 16,772 monthly users26 August 2026 — 16,618 monthly users7 August 202626 August 2026
16 measurements spanning 19 days, net -5,494. 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 15,762–23,182 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
26 Aug 2026, 07:5416,618-154
25 Aug 2026, 05:3616,772-223
24 Aug 2026, 07:4616,995+97
22 Aug 2026, 16:5716,898+108
21 Aug 2026, 08:5816,790-33
20 Aug 2026, 06:5716,823-415
19 Aug 2026, 09:3517,238-1,991
17 Aug 2026, 12:4719,229+11
16 Aug 2026, 20:3319,218no change
16 Aug 2026, 03:4719,218+85
14 Aug 2026, 16:1819,133+184
12 Aug 2026, 04:5318,949-787
11 Aug 2026, 08:0319,736-2,590
10 Aug 2026, 10:5122,326+300
9 Aug 2026, 08:5122,026-86
7 Aug 2026, 17:4722,112first 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.

Mentions

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

“Фотушка — фотосессии с ИИ в 1 клик” (@fotushka_bot), 16,618 monthly users as measured 26 August 2026. Telegram Register, tgregister.com/channel/fotushka_bot.

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.