Telegram RegisterThe public register of Telegram
Telegram profile photo for CaptainToxicAnalytics

Channel

CaptainToxicAnalytics

@CaptainToxicAnalytics

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

28subscribers

+2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003793875689
TypeChannel
Username@CaptainToxicAnalytics
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/CaptainToxicAnalytics

Growth

2628277 August 2026 — 26 subscribers11 August 2026 — 26 subscribers16 August 2026 — 28 subscribers7 August 202616 August 2026
3 measurements spanning 9 days, net +2. 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 26–28 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 19:1828+2
11 Aug 2026, 08:4526no change
7 Aug 2026, 19:3326first reading

Engagement

16 posts held, back to 10 August 2026the 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 · 30 days
14.7%
avg views ÷ 28 subscribers
Avg views / post
4.1
16 posts measured
Reaction rate
33.3%
reactions ÷ views · ER floor
Posts in window
16
of 16 held

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 2 of 16 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held16 (10 August 202610 August 2026)
Views total66
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 08:45 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.

What this channel posts

Video runtime
6m 10s
Average length
46s

Measured directly from 8 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

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🖕266.7%
👍133.3%

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

Measured over the 16 most recent posts we hold, published 10 August 2026 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, 20:37 UTC4 viewsread 11 August 2026
Forwarded from @irishmaninrussiaVideo

Ukrainian military infrastructure was reportedly struck in a major wave of attacks, with a thermal power plant and substations hit and gas infrastructure destroyed across the Sumy region Follow me Irish Man In Russia and Bowes Chay on X, Chay Bowes

10 Aug 2026, 20:31 UTC5 viewsread 11 August 2026
Forwarded from @DDGeopoliticsVideo

🇺🇦 European Values Mobilization in Dnepropetrovsk... now at gunpoint. 🔴 @DDGeopolitics | Socials | Donate | Advertising

10 Aug 2026, 20:08 UTC4 viewsread 11 August 2026
Forwarded from @DDGeopoliticsVideo

🇺🇦 Video of the Ukrainian MiG-29 falling from the sky in Odessa region earlier today. 🔴 @DDGeopolitics | Socials | Donate | Advertising

10 Aug 2026, 20:07 UTC4 viewsread 11 August 2026
Forwarded from @DDGeopoliticsVideo

🇱🇾 EXPLOSIONS REPORTED AT LIBYA’S ZAWIYA REFINERY Videos from western Libya show explosions and fire at a fuel tank inside the Zawiya refinery, roughly 40 km west of Tripoli. The cause of the latest explosions is not yet clear. The refinery is strategically important, it has a processing capacity of around 120,000 barrels per day and is linked to the massive Sharara oil field, one of Libya’s principal production ce

10 Aug 2026, 18:43 UTC4 viewsread 11 August 2026
Forwarded from @infodefENGLANDPhoto

"Time to negotiate": Musk denies Kiev Starlink access The world's richest man, billionaire Elon Musk, is in no hurry to provide Ukraine with full access to Starlink satellites. ▪️ According to The Atlantic, Elon Musk has refused to expand Kiev's use of the Starlink satellite system for targeting strikes on Russian territory. ▪️ Sources close to former Ukrainian Defense Minister Mykhailo Fedorov said no positive de

10 Aug 2026, 18:27 UTC4 viewsread 11 August 2026
Forwarded from @intelslavaVideo

🇷🇺🇷🇺🇲🇱🏳️⚡️ — Footage shows a Russian Africa Corps Lancet loitering munition striking a vehicle belonging to Jama'at Nusrat al-Islam wal-Muslimin (JNIM) in Mali. @IntelSlava

10 Aug 2026, 18:14 UTC4 viewsread 11 August 2026

📝A Look at Kaliningrad📝 It is important to distinguish actual threats from imaginary ones Potential threats to the Russian enclave on the Baltic are discussed frequently, but they are examined in a peculiar manner. The scenario where NATO infantry divisions cross borders and their fleets line up around Baltiysk is often debated. In reality, there are currently no real signs of planning for an imminent ground invasi

10 Aug 2026, 18:11 UTC3 viewsread 11 August 2026
Forwarded from @two_majorsPhoto

Zakharova: The press conference between Vucic and Zelensky in Belgrade on August 8th was tainted by a question from Michael Martens, a correspondent for the German newspaper FAZ. His question was: "Can you tell us, Europeans, what exactly we can do to help you kill more Russians? Of course, more Russian soldiers." To leave no doubt about the intent behind the provocation, he clarified on his social media account: "

10 Aug 2026, 18:11 UTC3 viewsread 11 August 2026
Forwarded from @two_majorsPhoto

⚡️Two Majors #Summary as of the morning of August 10, 2026 ▪️During the night, enemy drone attacks were repelled in Sevastopol and Crimea; 13 drones, heading towards Moscow, were shot down. Enemy channels reported an attack on oil refineries in Tatarstan in the early morning. In Makeevka (DPR), the "Galaktika" shopping center was on fire. During the day, the number of drones shot down from 8:00 AM to 8:00 PM reached

10 Aug 2026, 17:56 UTC6 viewsread 11 August 2026

🇰🇷🇺🇦 South Korea will not supply lethal weapons to Ukraine, Yonhap reports, citing a senior Foreign Ministry official. The official's statement came in response to Zelensky's remarks published the day before, in which he claimed North Korea was planning to send additional troops to Russia. "The government has offered Ukraine support in various sectors, including energy, infrastructure, healthcare, and education, an

10 Aug 2026, 17:54 UTC5 viewsread 11 August 2026
Forwarded from @DDGeopoliticsPhoto

🇺🇦 Ukrainian Air Force confirmed the loss of a MiG-29 over Odessa region. 🔴 @DDGeopolitics

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

Forward network

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.

Mentions

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

“CaptainToxicAnalytics” (@CaptainToxicAnalytics), 28 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/CaptainToxicAnalytics.

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.