Telegram RegisterThe public register of Telegram
Telegram profile photo for Scanon.ai Telegram Group

Channel

Scanon.ai Telegram Group

@scanonai

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

14subscribers

-1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002403565251
TypeChannel
Username@scanonai
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live2 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/scanonai

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 2 November 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Growth

141514.56 August 2026 — 15 subscribers11 August 2026 — 15 subscribers2 November 2026 — 14 subscribers6 August 20262 November 2026
3 measurements spanning 88 days, net -1. 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 14–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Nov 2026, 13:0614-1
11 Aug 2026, 23:0115no change
6 Aug 2026, 16:1615first reading

Engagement

20 posts held, back to 28 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 10s
Average length
50s

Measured directly from 5 videos 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.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤150.0%
👍150.0%

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

Measured over the 20 most recent posts we hold, published 28 September 2025 to 10 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

10 Aug 2026, 16:30 UTC3 viewsread 11 August 2026

v1.1.0 ships August 17th — founding pricing is open Our 2nd biggest release yet, so we're marking it with founding pricing for the rest of the month. Pro: $6/month, locked for life. Half price, permanently, for as long as you stay subscribed. Check it out: https://www.scanon.ai/pricing Running a business? Two months free on an annual plan, with your rate locked in for good. Reply here and we'll set it up. —— Wh…

2 Aug 2026, 16:56 UTC7 viewsread 11 August 2026
Photo

❗️Document redaction is live❗️ this is a big one. you can now scan documents for emails, names, organizations, and other sensitive numbers and codes, and have them automatically flagged and redacted. this has been one of the most requested things since launch, and it genuinely opens up a new category of use cases. contracts, forms, exports, anything with sensitive text in it, scanon can handle it now. it's also li…

23 Jul 2026, 18:12 UTC10 viewsread 11 August 2026
Photo

the scanon api is live probably the biggest thing we've shipped in a while, so here's the full rundown. there's a dedicated api page on the site now where you can create a business profile, plus a dashboard to track your usage as you go. this has been in the works for a bit and it genuinely changes what scanon can be used for. it's not just a tool you use yourself anymore, it's something you can actually build into…

12 Jul 2026, 16:11 UTC12 views1 reactionsread 11 August 2026
Photo

This week — Scanon.ai GPU upgrade, a reward system coming soon, and a bigger announcement 2 weeks out. Concurrent GPU processing is live. Video processes faster now, especially on larger files. Builds on the AWS migration from recent updates. Return user credits: coming soon. Process something 3 days in a row and earn a free photo credit. 5 days in a row earns a free video credit. Not live yet, but close — built t…

❤1

26 Jun 2026, 15:56 UTC15 viewsread 11 August 2026
Photo

Three updates — Scanon.ai Here's what shipped this week. Cryptographic encryption for blurring. We've added cryptographic encryption to the blur process, moving it much closer to fully irreversible and untraceable. Being transparent: this is still rolling out fully, but a working version is live now. Reversible blurring has been a known weak point across this category, and we're working to genuinely close that gap.…

19 Jun 2026, 15:48 UTC15 viewsread 11 August 2026
Photo

Six updates and our first partnership — Scanon.ai A lot shipped this cycle. Here's everything. License plates + screen detection are live. Fully working across images and video. Screens — laptops, phones, TVs — are now detected and blurred too. Video quality now preserves the original. No more quality loss on processed output. What you upload is what you get back, fully anonymized. Processing is faster. Pipeline …

12 Jun 2026, 16:36 UTC11 viewsread 11 August 2026

The new Scanon UI is live. We shipped a meaningful update today and wanted this group to hear it directly. New interface. Rebuilt from the ground up — not a cosmetic refresh. The workflow from upload to output is smoother, the detection view is cleaner, and the whole experience is faster to move through. If you've used Scanon before, you'll feel the difference immediately. Improved enterprise support. Better infra…

26 May 2026, 21:08 UTC12 viewsread 11 August 2026

Scanon v1.1 — coming soon This is the largest update since launch. Here's what's included. Rebuilt UI. Redesigned from the ground up — faster workflow, less friction between upload and output, cleaner detection visibility. Broader media support. More file formats and media types supported natively. Less need for workarounds. Full list on release. Improved video processing. Faster pipeline, higher output quality, …

20 Apr 2026, 17:00 UTC22 viewsread 11 August 2026
Photo

📣 Two updates — Scanon.ai Two things shipping this week. Wanted to make sure this group heard it first. —— 💳 Paid tiers are now live Pro — $12/month Higher processing limits, priority handling, full platform access. Team — $49/month Everything in Pro, built for teams working with media at volume. Free credits are still available. No email. No storage. That doesn't change. If you've been using Scanon regularly,…

8 Apr 2026, 19:50 UTC25 viewsread 11 August 2026
Video

🔵 Selective blurring is now live — scanon.ai You can now choose exactly which detections to redact in your photos. Faces, plates, tattoos — one tap per element. Full granular control. This has been one of the most-requested features since beta. We shipped it. 🎬 Video support is in active development. Coming soon. Zero storage. No email required. Always. 👉 www.scanon.ai

2 Apr 2026, 22:01 UTC24 views1 reactionsread 11 August 2026
Video

🎬 VIDEO SCANNING IS LIVE big update today — video support is now live on Scanon.ai. upload a video and we'll detect personal data in it: faces, license plates, visible addresses, documents in frame, and more. same detection engine as images, now applied to video. ━━━━━━━━━━━━━━━━ ⏱ Current limit: 30 seconds 📺 Current quality: 720p 🔧 Extended limits, higher resolution, and more improvements: coming soon ━━━━━━━━━━━…

👍1

31 Dec 2025, 05:46 UTC36 viewsread 11 August 2026
Video

🚨 Scanon.ai Update We’re officially moving forward with video face blurring. Now that our image face blurring pipeline is solid and established—with full metadata stripping and a universal image reformatter in place—we’re extending the same privacy-first protections to video. Everything is built to keep users safe, anonymous, and fully taken care of. 🎥 Video support is coming soon. Stay unseen.

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

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

“Scanon.ai Telegram Group” (@scanonai), 14 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/scanonai.

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.