Telegram RegisterThe public register of Telegram

Channel

20K VIDEOS

@videodevidral

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

16,539subscribers

-31 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002552211879
TypeChannel
Username@videodevidral
Created28 May 2025measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/videodevidral

Topic

Crypto & trading — 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 10 August 2026 and assigned it the closest of 31 fixed categories, at 82% 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@videodevidral/6 · this entry23 Sept 2025, 19:32 UTC@video_videos_virall/3723 Sept 2025, 19:33 UTC1.00under a minute
@videodevidral/7 · this entry23 Sept 2025, 19:32 UTC@video_videos_virall/3823 Sept 2025, 19:33 UTC1.00under a minute
@videodevidral/10 · this entry23 Sept 2025, 19:32 UTC@video_videos_virall/4123 Sept 2025, 19:33 UTC1.00under a minute
@videodevidral/13 · this entry23 Sept 2025, 19:32 UTC@video_videos_virall/4423 Sept 2025, 19:33 UTC1.00under a minute
@videodevidral/15 · this entry23 Sept 2025, 19:32 UTC@video_videos_virall/4623 Sept 2025, 19:33 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@video_videos_virall5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (50)

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 0 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 6 comparable posts for this entry, running 20 September 2025 to 23 September 2025. 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 @videodevidral — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, 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.

Growth

16,53916,57016,554.57 August 2026 — 16,570 subscribers8 August 2026 — 16,567 subscribers9 August 2026 — 16,563 subscribers10 August 2026 — 16,555 subscribers11 August 2026 — 16,548 subscribers12 August 2026 — 16,539 subscribers7 August 202612 August 2026
6 measurements spanning 5 days, net -31. 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 16,534–16,575 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 16:0416,539-9
11 Aug 2026, 14:5216,548-7
10 Aug 2026, 13:4216,555-8
9 Aug 2026, 14:1716,563-4
8 Aug 2026, 11:1116,567-3
7 Aug 2026, 17:4516,570first reading

Engagement

15 posts held, back to 28 May 2025the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 15 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 15 posts for this entry, the most recent from 23 September 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
7
Links
2

Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
888.9%
👍111.1%

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 5 of the 15 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 15 most recent posts we hold, published 28 May 2025 to 23 September 2025, 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

23 Sept 2025, 19:32 UTC≈1,450 viewsread 13 August 2026

JUST IN : 🇭🇰 Hong Kong backs development of investment products like tokenised gold. @chain_spark

23 Sept 2025, 19:32 UTC≈1,820 views4 reactionsread 13 August 2026

🚀 Top Trending Coins (Today) 1. ASTER 2. UDS 3. HYPE 4. PUMP 5. PENGU 6. LINEA 7. BARD 8. AVNT 9. AVAX 10. SOL 11. ONDO 12. NEAR 13. SUI 14. BNB 15. KMNO @chain_spark

3👍1

23 Sept 2025, 19:32 UTC≈1,380 views1 reactionsread 13 August 2026
Photo

JUST IN: 🇺🇸 Golden statue of President Trump holding a Bitcoin placed outside the US Capitol. @chain_spark

1

23 Sept 2025, 19:32 UTC≈1,390 viewsread 13 August 2026
Photo

📊 Crypto Fear and Greed Index 🧭 Index Value : 52 😱 Sentiment : Neutral 💰 BTC Price : $116431 @chain_spark

23 Sept 2025, 19:32 UTC≈1,350 views1 reactionsread 13 August 2026
Photo

NEW : 42% of #Bitcoin's circulating supply could become illiquid by 2032 due to Bitcoin treasury accumulation - Fidelity. @chain_spark

1

23 Sept 2025, 19:32 UTC≈1,800 viewsread 13 August 2026
Photo

🔥 NEW: Coinbase rolls out a new way for users to earn yields on USDC by integrating with Morpho, offering yields up to 10.8% through onchain DeFi lending directly in the app. @chain_spark

23 Sept 2025, 19:32 UTC≈1,310 viewsread 13 August 2026

JUST IN : 🔥 The SEC has approved common listing standards for commodity trust fund shares on the Nasdaq, CBOE, and NYSE. @chain_spark

23 Sept 2025, 19:32 UTC≈1,550 viewsread 13 August 2026
Photo

JUST IN : 🐳 Whale 0x96F4 withdrew 15,200 $ETH ($70.44M) from #Binance in the past 2 hours. @chain_spark

23 Sept 2025, 19:32 UTC≈1,380 viewsread 13 August 2026
Photo

JUST IN: 🚨🚨 Over $108,000,000 liquidated from the crypto market in the past 60 minutes. @chain_spark

23 Sept 2025, 19:32 UTC≈1,420 viewsread 13 August 2026

JUST IN: 🇺🇸 Coinbase CEO Brian Armstrong says he's in DC working to get crypto market structure legislation passed and "making sure we never have another Gary Gensler." @chain_spark

20 Sept 2025, 19:40 UTC≈5,270 views2 reactionsread 13 August 2026

👅👇 https://terasharelink.com/s/1By3XqeiD7ObTD0_Ht7T84A https://terasharelink.com/s/1By3XqeiD7ObTD0_Ht7T84A Mira los videos completos 👆😋 More vídeo 👇 https://t.me/addlist/1N0b7KSf-VBiZTY1

2

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“20K VIDEOS” (@videodevidral), 16,539 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/videodevidral.

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.