Channel
@DICloakBrowser_Official
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,221subscribers
+9 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002982382963 |
|---|---|
| Type | Channel |
| Username | @DICloakBrowser_Official |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/DICloakBrowser_Official |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 08:27 | 1,221 | +5 |
| 10 Aug 2026, 18:31 | 1,216 | +7 |
| 7 Aug 2026, 10:48 | 1,209 | -3 |
| 7 Aug 2026, 06:31 | 1,212 | first reading |
20 posts held, back to 29 May 2026 — 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 pageof 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. It is computed over the 3 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (29 May 2026 – 7 August 2026) |
| Views total | 1,392 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 06:31 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.
9 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 77.8% | |
| 👏 | 2 | 22.2% |
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 7 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 9reactions 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 29 May 2026 to 7 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.
💳 Manage Profiles and Launch Browser Tasks with DICloak APIs Still creating Profiles, assigning proxies, and opening browsers manually? Local API and HTTP API let your own system handle these steps. 💬 What can you do with them? • HTTP API for Profile management: Create or update Profiles, assign proxies, organize Profile Groups, and manage Members through your own system. • Local API for actions on your device: Ope…
⚡️ Set Up Extensions Once, Use Them Across Profiles Adding the same tools to every Profile takes time. With Extensions, you can set them up once and apply them where they are needed. You can also control what team members can see or change. 👀 What can you do with Extensions? • Add extensions: choose from Marketplace, a Chrome Web Store URL, or a ZIP package • Apply them to Profiles: organize tools into Extension Gr…
🖥 Running Multiple RPAs? Keep Every Task Under Control Multiple RPA tasks are useful, but checking their status one by one takes time. Task History gives you a single place to review every execution record. ✨ What can you do with it? • Choose how many Profiles can run the same RPA task at the same time • Keep long-running tasks running without being interrupted by system sleep • Quickly check what task ran, which P…
💡 No Template for Your Task? Create Your Own RPA The template library is only the starting point. Custom RPA gives you more ways to automate your daily work. 🔍 Who is it for? • You already have an Automa process you want to run in DICloak • No current RPA template covers the task or website you use • Your team follows a fixed process that needs its own automation 🖥 What can you do with Custom RPA? • Build the task…
🤖 Stop Repeating the Same Social Media Tasks Across Profiles The task itself may only take a few minutes. Repeat it across 10 or 20 Profiles, and it can quickly take over your day. Social media RPA templates are built for exactly this kind of repeated work. 👨💻 What can you automate? • X: browse homepage posts, like content, or update a profile • TikTok: watch videos or collect followers and video data • YouTube: s…
❤2
🔄 DICloak V2.9.10: Find Profiles Faster and Manage Extension Protection with Ease A fresh DICloak update is here! Let’s take a look at what’s new. 🔍 Looking for several client or campaign Profiles? Use Profile names (batch) to enter multiple full or partial names at once. All matching Profiles appear in one list, making campaign checks and client handoffs easier. 🛡 Want to exempt super admins from extension protec…
❤1
🍪 Warm Up Empty Profiles with Cookie Bot Empty Profiles can look unnatural when used right away. But Cookie Bot takes care of the first browsing step across multiple Profiles before account signup and daily use. 👀 Why users run Cookie Bot • Build browsing history: visit relevant websites before using a new Profile for Facebook, TikTok, Amazon, or other platforms • Farm Cookies automatically: collect and save the Co…
🔄 DICloak Update: Easier Route Switching and Better Member Access Control This update makes DICloak connection issues easier to resolve and Profile group changes easier to apply. 🤍 Switch Access Routes Inside DICloak • Use another available route when you cannot access DICloak normally • Open the route-switching window from the connection prompt or the upper-right corner • This only changes DICloak’s access route. …
🚀 Do It Once Across Multiple Profiles with Synchronizer Managing several social media accounts often means repeating the same action in every profile. With Synchronizer, you can perform the same actions across selected profiles from one master control window. ⚠️ Where the time usually goes • repeating the same clicks and navigation in every profile • copying captions, comments, or other text account by account • sw…
❤2
🔄 DICloak V2.9.7: Easier Login Checks, Cleaner Member Lists Daily account work often starts before the real task begins: logging in, finding the right members, and checking the right fields. This V2.9.7 update makes these small steps easier. 🌐 Switch Network Routes When Login Connection Fails When certain network-related login issues happen, users can check available routes and switch to a reachable one before chan…
⚡️ Too Many Repetitive Tasks? Batch It. As a project grows, those small tasks quickly turn into a long chain of repetitive clicks: creating similar profiles, applying the same settings, opening daily sessions, and updating everything again when something changes. 💡 With DICloak, you can handle those tasks in batches: ✔️ Set up a new batch: Create or import profiles, apply proxy settings, and keep names, groups, an…
⚙️ How to Keep Logins, Cookies & Proxies Stable Inside Profiles Do you run into issues like profile migration, cookies not carrying over, or proxy changes affecting your setup? Here are 5 FAQs covering issues users commonly run into. Check if any of them match your situation. 1. Can I import browser profiles from other browsers into DICloak? Yes. If your current tool supports profile export, you can migrate them in…
Showing the 12 most recent of 20 posts we hold for @DICloakBrowser_Official. 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.
Citation-graph rank — 1,210,924 of 1,480,944entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“DICloak Browser” (@DICloakBrowser_Official), 1,221 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/DICloakBrowser_Official.
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.