📢 NOTICE New FaceFusuionBot is https://t.me/facefusion005_bot
❤11👍7

Channel
@shizuka_ai_news
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Handles named that no longer answer · Cite this entry
52,204subscribers
+4,302 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002030006181 |
|---|---|
| Type | Channel |
| Username | @shizuka_ai_news |
| Created | Between 1 November 2023 and 21 January 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 28 October 2026 |
| Measurements held | 54 |
| Confirmed unchanged | 1 time, most recently 28 October 2026 |
| On Telegram | t.me/shizuka_ai_news |
Technology — 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 89% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 14:48 | 52,204 | +31 |
| 27 Oct 2026, 15:10 | 52,173 | +19 |
| 26 Oct 2026, 13:27 | 52,154 | +9 |
| 25 Oct 2026, 16:07 | 52,145 | +81 |
| 24 Oct 2026, 17:09 | 52,064 | +52 |
| 23 Oct 2026, 15:46 | 52,012 | +33 |
| 22 Oct 2026, 18:07 | 51,979 | +31 |
| 21 Oct 2026, 16:31 | 51,948 | +50 |
| 20 Oct 2026, 10:31 | 51,898 | +36 |
| 19 Oct 2026, 12:56 | 51,862 | +29 |
| 18 Oct 2026, 15:06 | 51,833 | +45 |
| 17 Oct 2026, 11:36 | 51,788 | +83 |
| 16 Oct 2026, 13:20 | 51,705 | +36 |
| 15 Oct 2026, 16:38 | 51,669 | +9 |
| 14 Oct 2026, 15:17 | 51,660 | +77 |
| 13 Oct 2026, 08:09 | 51,583 | +282 |
| 9 Oct 2026, 01:56 | 51,301 | +234 |
| 4 Oct 2026, 16:02 | 51,067 | +580 |
| 26 Sept 2026, 12:15 | 50,487 | +270 |
| 19 Sept 2026, 11:15 | 50,217 | first reading |
21 posts held, back to 21 January 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 165 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 5 October 2026 |
|---|---|
| Posts held | 21 (21 January 2024 – 5 October 2026) |
| Views total | 4,320 |
| Reactions total | 18 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Oct 2026, 11:06 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
4,066 reactions across 16 posts, in 13 distinct kinds. The most used accounts for 68.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2,801 | 68.9% | |
| 👍 | 806 | 19.8% | |
| 👏 | 176 | 4.33% | |
| 🔥 | 74 | 1.82% | |
| 🖕 | 68 | 1.67% | |
| 👎 | 44 | 1.08% | |
| 😁 | 42 | 1.03% | |
| 👾 | 26 | 0.639% | |
| 😭 | 13 | 0.32% | |
| 🫡 | 8 | 0.197% | |
| 🤷♂ | 4 | 0.098% | |
| 🍓 | 3 | 0.074% | |
| 🥰 | 1 | 0.025% |
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 16 of the 21 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 4,066 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 21 January 2024 to 5 October 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.
📢 NOTICE New FaceFusuionBot is https://t.me/facefusion005_bot
❤11👍7
⚠️ Service Restoration Notice! Hey everyone, the Telegram Bot API went down for about an hour, which affected our bot's ability to reply with your processed photos and videos. The good news is everything is back to normal now! The bot is fully up and running. You can now restart your previously failed tasks. Thanks for hanging in there with us! 🙌
❤286👍82👏59😭13😁5
⚠️ NOTICE In the past 30 minutes, the Telegram API was down, causing our bot to respond slowly and fail to reply FaceSwap results. No credits were consumed for failed reply tasks. The Telegram API is now fully operational, and our bot has been restored. Thanks for your understanding.
❤410👍57
📢 Announcement Due to a configuration error during last week’s bot upgrade, some payment channels were temporarily limited to 50 credits only. We sincerely apologize for the inconvenience this may have caused. The bot has now been fully upgraded, and the issue has been fixed. All top-up options and payment channels are now fully restored. Thank you for your understanding and continued support. If you have any ques…
❤146👍42
🚨 Service Incident Notice Our GPU servers experienced an unexpected failure about 30 minutes ago, causing roughly one hour of downtime. All FaceSwap tasks submitted during the outage returned “❌ Face swap fail!”. The server has been fully restored and is operating normally now. Thank you for your understanding.
👍71❤59👎5
📢 Latest Update — Face Selector Added for Video 1. OneFace (previous default) - Swaps the first detected face in each frame (left to right). - Ideal for single-face video. 2. Reference - Use the face detected in first frame as the reference and swaps that person throughout the video. - If no face is found in the first frame, the task fails (no credits consumed).
❤98🔥7
📢 Service Recovery Notice Cloudflare network services have now fully recovered. All affected features are back to normal, including all bot functionalities and the top-up system.✅ Thank you for your patience and understanding. If you experience any further issues, please feel free to 📥 contact us.
👍54❤27😁8🥰1
⚠️ NOTICE Our bot experienced slowed responses and a pending of tasks over the past 2 hours, due to partial unavailability of Cloudflare services it relies on. We have now switched to backup services: The faceswap function of bot has been fully restored. ✅ Payment pages is still unavailable. ❌ We will keep you updated on the status of the bots, Thank you for your patience!
❤52🫡8
📢 Latest Update! ⚡ AI servers upgraded — video face-swap is now 2x faster 🚀 No credits deducted if video freeze is detected
❤135👏33
✅ Bot is back online. ⚠️ @face_fusion_bot has too many pending messages and may not reply. 👉 Please use @facefusion001_bot or @facefusion002_bot if no response.
❤98👍19👎9👏4🔥2😁2
⚠️ NOTICE Our Telegram bot is temporarily unavailable due to Telegram server issues. We’ll bring it back online as soon as Telegram restores their service. Thanks for your patience! 🙏
❤66👍9
Have you encountered any issues with videos freezing after face swapping
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
🖕68❤51👍18👏5🤷♂4
Showing the 12 most recent of 21 posts we hold for @shizuka_ai_news. 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.
@shizuka_ai_news edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Have you encountered any issues with videos freezing after face swapping
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 21 most recent posts we hold, published 21 January 2024 to 5 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
@shizuka_ai_news named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“Shizuka.AI” (@shizuka_ai_news), 52,204 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/shizuka_ai_news.
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.