Telegram RegisterThe public register of Telegram
Telegram profile photo for كلاسيكو نيوز HD

Channel

كلاسيكو نيوز HD

@ClassicoNewsHD

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Cite this entry

51,411subscribers

+27,802 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003203558121
TypeChannel
Username@ClassicoNewsHD
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live15 November 2026
Measurements held63
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/ClassicoNewsHD

Topic

Sports — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.

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 in near-verbatim form on 12 other registered channels. This entry also forms a group of 2 channels linked by matching posts. 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 (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ClassicoNewsHD/25070 · this entry1 Sept 2026, 17:40 UTC@RealMadridNews015/1363661 Sept 2026, 19:02 UTC1.0082 minutes
@RealMadridNews015/1408812 Oct 2026, 20:47 UTC@ClassicoNewsHD/29317 · this entry2 Oct 2026, 20:48 UTC1.00under a minute
@ClassicoNewsHD/30975 · this entry17 Oct 2026, 12:52 UTC@RealMadridNews015/14256217 Oct 2026, 12:53 UTC1.0072 seconds
@ClassicoNewsHD/31658 · this entry18 Oct 2026, 21:56 UTC@RealMadridNews015/14294418 Oct 2026, 21:59 UTC1.002 minutes
@ClassicoNewsHD/31659 · this entry18 Oct 2026, 21:57 UTC@RealMadridNews015/14294518 Oct 2026, 21:59 UTC1.002 minutes
@RealMadridNews015/14446029 Oct 2026, 09:50 UTC@ClassicoNewsHD/34104 · this entry29 Oct 2026, 16:05 UTC1.006.3 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@RealMadridNews01546 (8/8 hand-verifiable sample passed)1.005 minutes@RealMadridNews015 (27–19)
@RealMadridNewsHD27 (8/8 hand-verifiable sample passed)0.972 minutes@RealMadridNewsHD (20–7)
@RealMadridWorldHD26 (8/8 hand-verifiable sample passed)0.997 minutes@RealMadridWorldHD (14–12)
@YSMSPRZ7222 (8/8 hand-verifiable sample passed)1.008 minutesthis entry (17–5)
@barca_New_arab18 (8/8 hand-verifiable sample passed)0.965 minutes@barca_New_arab (14–4)
@Kings_of_Europe17 (8/8 hand-verifiable sample passed)0.9926 minutesthis entry (16–1)
@RealMadridWorld1516 (8/8 hand-verifiable sample passed)0.9919 minutes@RealMadridWorld15 (14–2)
@c77m215 (8/8 hand-verifiable sample passed)1.0010 minutesthis entry (14–1)
@Barca_Studio_News14 (8/8 hand-verifiable sample passed)0.944 minuteseven
@FCBarcelona_Arabic8 (8/8 hand-verifiable sample passed)0.954 minutes@FCBarcelona_Arabic (8–0)
@IRAQBLANCOS8 (8/8 hand-verifiable sample passed)0.978 minutesthis entry (5–3)
@FCBLamine_pooq7 (7/7 hand-verifiable sample passed)1.0014 minutesthis entry (7–0)

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. 145 of the 145 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 1,451 comparable posts for this entry, running 8 August 2026 to 14 November 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @ClassicoNewsHD — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 15 November 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.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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

23,60951,91337,76151,4119 August 202615 November 2026
63 measurements spanning 98 days, net +27,802. 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 19,363–56,159 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 63
Measured (UTC)SubscribersChange
15 Nov 2026, 06:1051,411-502
12 Nov 2026, 01:4851,913+407
10 Nov 2026, 06:5751,506+222
8 Nov 2026, 17:5151,284-94
7 Nov 2026, 13:5651,378+513
6 Nov 2026, 10:4850,865+492
5 Nov 2026, 10:3750,373+1,201
4 Nov 2026, 07:0449,172+2,869
3 Nov 2026, 05:1646,303-14
2 Nov 2026, 02:0946,317-297
1 Nov 2026, 01:1946,614-262
30 Oct 2026, 23:2646,876-374
29 Oct 2026, 23:1947,250-272
28 Oct 2026, 23:4947,522+1,061
27 Oct 2026, 19:1146,461-235
26 Oct 2026, 21:0646,696+183
25 Oct 2026, 23:0746,513+55
24 Oct 2026, 22:3746,458+260
23 Oct 2026, 22:3646,198-267
23 Oct 2026, 00:4646,465first reading

Engagement

3,416 posts held, back to 8 August 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 197 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.52%
avg views ÷ 51,411 subscribers
Avg views / post
1,300
1,104 posts measured
Reaction rate
2.81%
reactions ÷ views · ER floor
Posts in window
1,104
of 3,416 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 1,102 of 1,104 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 15 November 2026
Posts held3,416 (8 August 2026 – 15 November 2026)
Views total1,432,832
Reactions total40,186
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Nov 2026, 05:43 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
8s
Average length
4s

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

36,926 reactions across 994 posts, in 26 distinct kinds. The most used accounts for 68.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤25,09268.0%
🔥2,9247.92%
👎1,9805.36%
❤‍🔥1,5624.23%
😭1,0752.91%
💔7051.91%
🤯5221.41%
🫡4811.30%
🤬3741.01%
💘3721.01%
👏3550.961%
🥰3090.837%
🥱2660.72%
👍2410.653%
😢2330.631%
😱800.217%
🤩600.162%
😘530.144%
😍510.138%
👌420.114%
6 further kinds1490.404%

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 999 of the 1,000 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 36,926 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 October 2026 to 15 November 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.

Telegram Stars

Stars received
10
across the posts below
Posts paid on
6
of 1,000 we hold a reading for · 0.6%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ClassicoNewsHD. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 18 October 2026 to 15 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 292 of 1,104 posts held from the last 30 days (26.4%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

15 Nov 2026, 00:29 UTC≈1,070 views30 reactionsread 15 November 2026

Posted without readable text

❤22👎5💔2👍1

Signed ⋆ 𓏺 𝗢𝗕𝗔𝗜𝗗𝗔

15 Nov 2026, 00:23 UTC913 views15 reactionsread 15 November 2026
Photo

🚨🚨🚨🎙 سلافن بيليتش: ‏نود أن يحصل ليفاكوفيتش على استمرارية في المشاركة مع برشلونة. لكنه حارس مرمى جيد جدًا، لم أكن أعرفه شخصيًا قبل تولّي تدريب المنتخب. لكن خلال الشهرين اللذين عملنا فيهما معًا، لاحظت أنه تطور في بعض الجوانب.

❤15

Signed ⋆ 𓏺 𝖧𝖺𝗆𝖺𝖽

15 Nov 2026, 00:20 UTC837 views13 reactionsread 15 November 2026
Photo

- يُقال إن التدريبات في برشلونة أصعب من المباريات، هل هذا صحيح؟ 🚨🚨🚨🎙 دومينيك ليفاكوفيتش: ‏التدريبات في برشلونة صعبة جدًا بالفعل، فنحن نتحدث عن أفضل اللاعبين في العالم. ‏ سيكون من المثالي أن أحرس المرمى في كل مباراة، لكنني أنتظر فرصتي بصبر.

❤13

Signed ⋆ 𓏺 𝖧𝖺𝗆𝖺𝖽

14 Nov 2026, 23:55 UTC829 views25 reactionsread 15 November 2026
Photo

كوكوريا. 📸

❤23❤‍🔥2

Signed ⋆ 𓏺 𝖧𝖺𝗆𝖺𝖽

14 Nov 2026, 23:53 UTC800 views15 reactionsread 15 November 2026
Photo

- صحيفة ماركا [◾️]: مؤخرًا أصبح لدينا فينيسيوسان.. أحدهما بقميص ريال مدريد، والآخر بقميص منتخب البرازيل.

❤15

Signed ⋆ 𓏺 𝗢𝗕𝗔𝗜𝗗𝗔

14 Nov 2026, 23:52 UTC754 views18 reactionsread 15 November 2026
Photo

🚨🚨🚨🗣️ دومينيك ليفاكوفيتش: ‏سعيد بالفوز بالجائزة التي تعكس تقدير الجماهير. وفخور بالسير على خطى لوكا وبيريا، مؤكدًا أن نجاح المنتخب الوطني يعني له الكثير. وموجهًا الشكر لكل من صوّت ودعم المنتخب في جميع الظروف.

❤18

Signed ⋆ 𓏺 𝖧𝖺𝗆𝖺𝖽

14 Nov 2026, 23:47 UTC779 views14 reactionsread 15 November 2026
Photo

كامافينغا. 📸

❤13❤‍🔥1

Signed ⋆ 𓏺 𝖧𝖺𝗆𝖺𝖽

14 Nov 2026, 23:45 UTC740 views20 reactionsread 15 November 2026
Photo

حصل ليفاكوفيتش على جائزة «القلب الناري»، تقديرًا لروح التضحية والتفاني التي أظهرهما مع المنتخب الكرواتي. ❤️🇭🇷

❤20

Signed ᴋʏʟᴇʀ

14 Nov 2026, 23:17 UTC934 views24 reactionsread 15 November 2026
Photo

‏• كامافينغا في الفريق الفائز خلال تدريبات فرنسا.

❤24

Signed ⋆ 𓏺 𝖧𝖺𝗆𝖺𝖽

14 Nov 2026, 23:08 UTC≈1,000 views24 reactionsread 15 November 2026
Photo

• البرتغال والأرجنتين تسقطان في أول اختبار دون رونالدو وميسي، بالخسارة أمام الدنمارك وأوروغواي.. هل أصبح المنتخبان رهينة لوجود أسطورتيهما؟! 🤯🤯🤯

❤19💔5

Signed ⋆ 𓏺 𝗢𝗕𝗔𝗜𝗗𝗔

14 Nov 2026, 23:06 UTC965 views22 reactionsread 15 November 2026
Photo

كليان مبابي. 📸

❤22

Signed ⋆ 𓏺 𝖧𝖺𝗆𝖺𝖽

14 Nov 2026, 22:57 UTC970 views24 reactionsread 15 November 2026
Photo

🎂 - يكمل اليوم روني بردغجي عامه 21 .

❤19👎5

Signed ᴋʏʟᴇʀ

Showing the 12 most recent of 3,416 posts we hold for @ClassicoNewsHD. 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.

Posts edited after publishing

@ClassicoNewsHD edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
1 October 2026
Most recent edit
4 October 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @ClassicoNewsHD as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
11 October 2026
Most recent seen missing
15 October 2026
Median time before seen missing
13 hours
Seen missing in the last 30 days
0

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

20 Oct 2026, 12:41 UTCAnonymous Poll327 voters

من تُفضل ؟ 🤔

  1. داني اولمو 🔴41%
  2. فيرمن لوبيز 🔴66%

The shares total 107%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 October 2026 to 15 November 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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

Named by 10 registered channels — 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.

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

“كلاسيكو نيوز HD” (@ClassicoNewsHD), 51,411 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/ClassicoNewsHD.

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.