Channel
@kameleoapp
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,043subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001368912410 |
|---|---|
| Type | Channel |
| Username | @kameleoapp |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/kameleoapp |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Oct 2026, 20:56 | 1,043 | +4 |
| 29 Sept 2026, 20:38 | 1,039 | +3 |
| 11 Sept 2026, 22:20 | 1,036 | -1 |
| 2 Sept 2026, 06:34 | 1,037 | -3 |
| 29 Aug 2026, 23:54 | 1,040 | -3 |
| 21 Aug 2026, 06:03 | 1,043 | -1 |
| 14 Aug 2026, 22:35 | 1,044 | -3 |
| 8 Aug 2026, 00:19 | 1,047 | no change |
| 7 Aug 2026, 21:36 | 1,047 | first reading |
20 posts held, back to 3 October 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Kameleo 5.1 is out 🔍 Fingerprint Inspector is now generally available as a one-click launch option. Five more fixes and improvements on top. 🆕 Added • Allow creating a profile using the API without specifying a fingerprint; if omitted, the Engine automatically selects one using its recommended defaults. • Add Fingerprint Inspector as a launch option in the profile context menu in the UI to enable real-time fingerpr…
🚀 Chroma 151 is here Kameleo Engine automatically downloads and switches to the latest kernels, keeping you on the newest patched version without you lifting a finger. More info on the multikernel feature 👉 https://developer.kameleo.io/concepts/kernels/ To support our work on releasing fresh kernels, please ⭐️ us on GitHub: https://github.com/kameleo-io/kameleo
Kameleo 5.0 is out. 🚀 This is the biggest release in a while. Accountless mode, token-based auth replacing email/password, pw-bridge for Junglefox now in the SDK, and smarter fingerprint defaults out of the box. Read the full write-up here: https://kameleo.io/blog/kameleo-5-0-less-setup-more-scraping 🆕 Added Engine: Accountless mode is now supported; profile launch is available without an account GUI: OIDC-based …
Kameleo 5.0 is coming June 15 We're 6 days out. A few breaking changes are shipping with this release — worth knowing before you update. 🔐 Authentication is being overhauled Sign-in moves to the browser. On first launch after updating, you'll click through a sign-in prompt. If you're already logged in via the browser, it's nearly automatic. For server and automated environments: you'll be able to generate a PAT (…
Kameleo 4.5.0 is out. 🐳 Two big additions to the Docker image, a browser selector cleanup, and seven fixes. As some of you requested, the docker image is now tagged 4.5.0, 4.5, and 4. Pin to whichever granularity fits your setup. 🆕 Added - VNC Viewer in Docker: use any browser to inspect the profiles running in the Linux docker image. Details: https://developer.kameleo.io/integrations/docker/#vnc-viewer-only-in-lin…
🔵 Chrome 148 hit stable 2 days ago. Kameleo already supports it. This is part of our SLA: we track the Chrome stable channel and ship support fast, because falling behind isn't just a lagging feature, it's a fingerprint. Evergreen browsers auto-update. Real users are already on 148. If your profiles aren't, that version gap is visible to anti-bot systems. Stay current, stay invisible.
Kameleo now has an official Linux Docker image 🐧 Two browser engines (Chrome-based + Firefox-based), live fingerprint profiles from real device traffic, persistent profiles across restarts. Runs headless on any VPS or AWS ECS — no GPU needed, no Windows VM, no Windows license costs. Docs → https://developer.kameleo.io/integrations/docker/ The longer story (why it took this long, what broke) → https://kameleo.io/bl…
🔧 Kameleo 4.4.1 is out! Small patch after 4.4.0: one Docker improvement and a handful of GUI fixes that were quietly annoying people. Changed ✅ Docker entrypoint: if a GPU is available on the host, the containerized browser can now leverage it for hardware-accelerated rendering. The entrypoint automatically detects GPU availability and configures the browser accordingly. Fixed ✅ GUI: Profile updates are now reflec…
🚀 Chroma 147 is here Kameleo.CLI automatically downloads and switches to the latest kernels, keeping you on the newest patched version without you lifting a finger. More info on the multikernel feature 👉 https://developer.kameleo.io/concepts/kernels/ To honor our rapid work on releasing fresh kernels, please ⭐️ us on GitHub: https://github.com/kameleo-io/kameleo
🚀Kameleo 4.4 is here🚀 This is what happened lately beyond fresh kernel updates and making our infra even more robust ADDED ✅ Multiple language values in profile language settings: accepts comma-separated locales (e.g. de-AT,en-US). Not yet available on the user interface, only via Kameleo's API and official SDKs ✅ Handle bigger deviceMemory values (16, 32) introduced in Chrome 147 ✅ Unified public repositories unde…
🚀 Chroma 146 is here Yesterday (March 10), Chromium 146 Stable was officially released. Today, March 11, we are already shipping our patched Chroma 146 kernel. Browsers evolve constantly. And with them, anti-bot technologies evolve as well. If you build scrapers or browser automation workflows, you simply cannot afford to stay behind. Detection systems adapt fast, and keeping up with the newest browser stack is cri…
🚀 Chroma 145 is here - same day as Chrome 145 Today, Chrome officially released its Stable version: Chrome 145. And today, we are already deploying our patched Chroma 145. Over the last 2 weeks since the stable cut, we’ve been analyzing the source code and preparing the patch, so the moment Chrome went live, we were ready. Result? ✅ Your browser automation stays undetected ✅ Zero action needed on your side Multike…
Showing the 12 most recent of 20 posts we hold for @kameleoapp. 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.
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“KAMELEO.IO - Anti-Detect Browser Platform” (@kameleoapp), 1,043 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/kameleoapp.
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.