Telegram RegisterThe public register of Telegram
Telegram profile photo for DeepFakeBot Announces

Channel

DeepFakeBot Announces

@DeepFakeBotAnnounces

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

51,172subscribers

+1,118 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 ID-1001943122207
TypeChannel
Username@DeepFakeBotAnnounces
Description🇺🇸Announces channel for @FaceChangeAIBot 🇷🇺Статус бота, обновления, анонсы.
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held32
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/DeepFakeBotAnnounces

Topic

Hacking & security — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 32% 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 why it has no browse page of its own yet.

Growth

50,05451,17250,6137 August 2026 — 50,054 subscribers7 August 2026 — 50,054 subscribers8 August 2026 — 50,105 subscribers9 August 2026 — 50,165 subscribers10 August 2026 — 50,206 subscribers11 August 2026 — 50,266 subscribers12 August 2026 — 50,344 subscribers13 August 2026 — 50,401 subscribers14 August 2026 — 50,467 subscribers16 August 2026 — 50,530 subscribers17 August 2026 — 50,590 subscribers18 August 2026 — 50,634 subscribers19 August 2026 — 50,680 subscribers20 August 2026 — 50,759 subscribers22 August 2026 — 50,798 subscribers23 August 2026 — 50,860 subscribers25 August 2026 — 50,848 subscribers26 August 2026 — 50,564 subscribers27 August 2026 — 50,266 subscribers28 August 2026 — 50,213 subscribers29 August 2026 — 50,239 subscribers30 August 2026 — 50,278 subscribers31 August 2026 — 50,352 subscribers1 September 2026 — 50,373 subscribers2 September 2026 — 50,435 subscribers3 September 2026 — 50,483 subscribers4 September 2026 — 50,612 subscribers7 September 2026 — 50,697 subscribers10 September 2026 — 50,866 subscribers12 September 2026 — 50,967 subscribers14 September 2026 — 51,075 subscribers15 September 2026 — 51,172 subscribers7 August 202615 September 2026
32 measurements spanning 39 days, net +1,118. 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 49,886–51,340 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 32
Measured (UTC)SubscribersChange
15 Sept 2026, 19:3751,172+97
14 Sept 2026, 02:5651,075+108
12 Sept 2026, 09:2150,967+101
10 Sept 2026, 07:5750,866+169
7 Sept 2026, 02:3650,697+85
4 Sept 2026, 12:3850,612+129
3 Sept 2026, 00:3550,483+48
2 Sept 2026, 01:5350,435+62
1 Sept 2026, 02:0750,373+21
31 Aug 2026, 03:5750,352+74
30 Aug 2026, 05:3850,278+39
29 Aug 2026, 06:3350,239+26
28 Aug 2026, 04:2450,213-53
27 Aug 2026, 05:1650,266-298
26 Aug 2026, 05:5850,564-284
25 Aug 2026, 03:4550,848-12
23 Aug 2026, 21:0750,860+62
22 Aug 2026, 02:2650,798+39
20 Aug 2026, 19:4450,759+79
19 Aug 2026, 16:3350,680first reading

Engagement

23 posts held, back to 24 March 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 82 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
25.1%
avg views ÷ 51,172 subscribers
Avg views / post
12,800
3 posts measured
Reaction rate
0.07%
reactions ÷ views · ER floor
Posts in window
3
of 23 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 26 August 2026
Posts held23 (24 March 202626 August 2026)
Views total38,500
Reactions total27
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Sept 2026, 14:44 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.

Reaction mix

241 reactions across 22 posts, in 8 distinct kinds. The most used accounts for 76.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
18476.3%
👍2610.8%
135.39%
👌93.73%
👀41.66%
🎉31.24%
🤔10.415%
🤝10.415%

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

Measured over the 23 most recent posts we hold, published 24 March 2026 to 26 August 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.

Recent posts

26 Aug 2026, 23:21 UTC≈12,700 views16 reactionsread 16 September 2026

✅Hello everyone! 🔄 Bots @FaceChangeAIBot / @DeepFakeRro_Bot are launched and working normally. Please send your suggestions to the support service 👉👉👉@DeepFakeSupport_Bot. 👀 ➖➖➖➖➖➖➖➖➖➖➖👀 ➡️ @DeepFakeBotAnnounces⏺

11👀4🤔1

26 Aug 2026, 07:35 UTC≈13,100 views8 reactionsread 16 September 2026

➡️📺@FaceChangeAIBot / @DeepFakeRro_Bot 🔽🔽🔽🔽 🇺🇸 Technical work is underway on the provider's communication channel. The bot may not respond to requests. Expect it to be fixed soon. ➖➖➖➖➖➖➖➖➖➖➖ 🇪🇸En el canal de comunicación del proveedor se realizan trabajos técnicos. Es posible que el bot no responda a las solicitudes. Espere que esto se solucione pronto. ➖➖➖➖➖➖➖➖➖➖➖ 🇷🇺 На канале связи провайдера ведутся технически

4👍4

25 Aug 2026, 17:09 UTC≈12,700 views3 reactionsread 16 September 2026

➡️📺@FaceChangeAIBot / @DeepFakeRro_Bot 🔽🔽🔽🔽 🇺🇸 Dear Users, Yesterday, our network provider experienced temporary technical issues, which caused some deepfake generation tasks to freeze. If your task has been stuck in the queue for several hours, please send us the task ID and the link to the bot you used. We will reset the task so you can restart it. We apologize for any inconvenience this may have caused and apprec

3

1 Jul 2026, 17:29 UTC≈35,900 views31 reactionsread 16 September 2026

✅Hello everyone! 🔄 Bots @FaceChangeAIBot / @DeepFakeRro_Bot are launched and working normally. Please send your suggestions to the support service 👉👉👉@DeepFakeSupport_Bot. 👀 ➖➖➖➖➖➖➖➖➖➖➖👀 ➡️ @DeepFakeBotAnnounces⏺

23👍53

29 Jun 2026, 21:09 UTC≈35,300 views17 reactionsread 16 September 2026

➡️📺@FaceChangeAIBot / @DeepFakeRro_Bot 🔽🔽🔽🔽 🇺🇸 Technical work is underway on the provider's communication channel. The bot may not respond to requests. Expect it to be fixed soon. ➖➖➖➖➖➖➖➖➖➖➖ 🇪🇸En el canal de comunicación del proveedor se realizan trabajos técnicos. Es posible que el bot no responda a las solicitudes. Espere que esto se solucione pronto. ➖➖➖➖➖➖➖➖➖➖➖ 🇷🇺 На канале связи провайдера ведутся технически

17

29 Jun 2026, 09:28 UTC≈29,400 views1 reactionsread 16 September 2026

✅Hello everyone! 🔄 Bots @FaceChangeAIBot / @DeepFakeRro_Bot are launched and working normally. Please send your suggestions to the support service 👉👉👉@DeepFakeSupport_Bot. 👀 ➖➖➖➖➖➖➖➖➖➖➖👀 ➡️ @DeepFakeBotAnnounces⏺

1

29 Jun 2026, 06:38 UTC≈28,500 views5 reactionsread 16 September 2026

➡️📺@FaceChangeAIBot / @DeepFakeRro_Bot 🔽🔽🔽🔽 🇺🇸 Technical work is underway on the provider's communication channel. The bot may not respond to requests. Expect it to be fixed soon. ➖➖➖➖➖➖➖➖➖➖➖ 🇪🇸En el canal de comunicación del proveedor se realizan trabajos técnicos. Es posible que el bot no responda a las solicitudes. Espere que esto se solucione pronto. ➖➖➖➖➖➖➖➖➖➖➖ 🇷🇺 На канале связи провайдера ведутся технически

5

17 Jun 2026, 07:54 UTC≈20,700 views5 reactionsread 16 September 2026

✅Hello everyone! 🔄 Bots @FaceChangeAIBot / @DeepFakeRro_Bot are launched and working normally. Please send your suggestions to the support service 👉👉👉@DeepFakeSupport_Bot. 👀 ➖➖➖➖➖➖➖➖➖➖➖👀 ➡️ @DeepFakeBotAnnounces⏺

5

17 Jun 2026, 06:58 UTC≈19,100 views5 reactionsread 16 September 2026

🇺🇸 To avoid losing tokens, we recommend stopping current generations and not starting new ones for an hour ➖➖➖➖➖➖➖➖➖➖➖ 🇪🇸 Para evitar perder tokens, recomendamos detener las generaciones actuales y no iniciar nuevas durante una hora. ➖➖➖➖➖➖➖➖➖➖➖ 🇷🇺 Во избежание потери токенов рекомендуем остановить текущие генерации и не запускать новые в течении часа. 👉 @DeepFakeBotAnnounces⏺

5

17 Jun 2026, 06:53 UTC≈15,800 views6 reactionsread 16 September 2026

➡️📺@FaceChangeAIBot / @DeepFakeRro_Bot 🔽🔽🔽🔽 🇺🇸 Technical work is underway on the provider's communication channel. The bot may not respond to requests. Expect it to be fixed soon. ➖➖➖➖➖➖➖➖➖➖➖ 🇪🇸En el canal de comunicación del proveedor se realizan trabajos técnicos. Es posible que el bot no responda a las solicitudes. Espere que esto se solucione pronto. ➖➖➖➖➖➖➖➖➖➖➖ 🇷🇺 На канале связи провайдера ведутся технически

6

27 May 2026, 17:07 UTC≈28,200 views20 reactionsread 16 September 2026

✅Hello everyone! 🔄 Bots @FaceChangeAIBot / @DeepFakeRro_Bot are launched and working normally. Please send your suggestions to the support service 👉👉👉@DeepFakeSupport_Bot. 👀 ➖➖➖➖➖➖➖➖➖➖➖👀 ➡️ @DeepFakeBotAnnounces⏺

16👌4

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

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“DeepFakeBot Announces” (@DeepFakeBotAnnounces), 51,172 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/DeepFakeBotAnnounces.

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.