Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
Observations
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Content that also appears on other registered channels
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
Matching posts — open both and compare (1 of the pairs behind the counts below)
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 1 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 18 comparable posts for this entry, running 13 March 2024 to 18 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Across the whole group of 2, the earliest publisher we hold is @alexdev_en. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
Also posting the same content
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
6 measurements spanning 12 days, net -13. 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 2,645–2,663 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
18 Aug 2026, 21:54
2,647
-3
12 Aug 2026, 19:13
2,650
-6
9 Aug 2026, 21:52
2,656
-5
7 Aug 2026, 06:23
2,661
+1
6 Aug 2026, 21:00
2,660
no change
6 Aug 2026, 20:49
2,660
first reading
Engagement
20 posts held, back to 13 March 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 2 pagesof 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 18 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
112 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 42.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
47
42.0%
❤
36
32.1%
🔥
26
23.2%
👏
2
1.79%
🆒
1
0.893%
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 18 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 112reactions 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 13 March 2024 to 18 July 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.
Instagram Issues
Instagram seems to be undergoing some type of maintenance, where it is impossible to open a profile page in incognito mode or without authentication
We are working on finding alternative solutions, but are sure that instagram will resolve this issue soon
ℹ️ Feature Request ℹ️
We are working on new features and implementations for EngageBot.PRO
We want to invest some time, thanks to the help of a new team member, to make the existing features better, and produce new ones
❔ For Example:
Now the "users" table loads incredibly faster and asyncronously, saving time and performances on any kind of device
👉 What would you like us to add/improve?
We're talking about ANY P…
❗️ EngageBot.PRO Updates ❗️
We've just rolled out a new update packed with new features, improvements, and fixes to make the bot even better!
Here is what's new:
🔗 Links & Social Media
Link Unshortening: The bot now automatically unshorts Instagram and TikTok links.
New TikTok Links: Added support for the newest TikTok URL formats.
In-Place Replacement: Instant and direct replacement for URLs directly inside t…
⚠ CloudFlare Down ⚠
Cloudflare, leading provider for DNS and Networking, is down globally (and most platforms like ChatGPT, Canva, X.. are down with it)
Some of our services depend on cloudflare for interactions (server-to-server connections and web platform), so our bots are currently "unreachable" as well
We will try to keep you updated as much as possible
You can keep track of our situation on our Status Page:…
⚠️ Server Provider Issues
Our server provider is reporting issues with some of our servers, probably related to networking access
We are in contact trying to resolve the issue as soon as possible
Some services might be unresponsive during this maintenance
⭐️ Happy Holidays ⭐️
We would like to take a moment to wish you all a sincere Happy Holidays 🎁
We hope that this year has been a happy and fulfilling one for you, and that the next one can shine with even more strength ❄️
We are thrilled and honored to have had you on board our projects over the years, and we hope that we can continue to work to improve and solidify your trust in the coming year as well
We also t…
🎯 NEW: Variables List
We just released our comprehensive Variables List, that allows you to have a complete overview of all the possible customizations you can insert in your EngageBot.PRO messages
Together with this variables list, we also created new variables and optimized the existing ones!
You can insert them in ANY message sent by the bot, limited to the situation
📥 Try it now!
🎵 TikTok BETA is OUT 🎵
🌟 EngageBot.PRO officially released the TikTok BETA Program!
Bring your engagement to TikTok with the new Beta of EngageBot.PRO!
Like, Comment, Follow and Views to create your own TikTok Engagement Groups.
❔ Not a customer? Start now to create your TikTok Engagement Groups!
🔗 Read More
😛 TikTok Engagement Groups are coming! 😛
We are happy to announce that TikTok API is entering its phase Alpha 2.0!
We now have officially something stable to work with, and are proceeding with the development of its features for EngageBot.PRO
We will also be featuring the TikTok Engagement API in our Social API plan, so stay tuned!
❓ Interested? Join EngageBot.PRO today to have it INCLUDED FOR FREE as soon as it …
🤖 Twitter (X) Beta V2 Available
We need YOUR HELP to make EngageBot.PRO better! ⭐️
Our Twitter Integration finally reached Beta Stage 2, and we are ready to release it for Production Use!
➿➿➿➿➿➿➿➿➿➿➿➿➿
❓ What does it mean?
Beta 2 stage means that the system has been fully tested by both our staff and selected customers, and it's fully working without any reported issues!
🔭 Why not production then?
We want to m…
❤3
Showing the 12 most recent of 20 posts we hold for @EngageBotPRO. 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.
Polls
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
We are working on the TikTok API, but costs are higher than Instagram
For every request made to TikTok, ~100 engagebot requests would be consumed This means that, with the Professional plan, ~300 tiktoks could be checked daily How do you feel?
I would still be interested in using it73%
I prefer waiting for a cheaper option27%
Shares as published. 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 20 most recent posts we hold, published 13 March 2024 to 18 July 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.
Citation-graph rank
Citation-graph rank — 52,002 of 1,550,164entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 18 August 2026 — this
entry's latest reading, not the date you are reading this.
“📸 EngageBot.PRO” (@EngageBotPRO), 2,647 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/EngageBotPRO.
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.