Telegram RegisterThe public register of Telegram

Channel

XclusiveETH (Official)

@XclusiveETH

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

781subscribers

+0 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-1002078636524
TypeChannel
Username@XclusiveETH
Created5 April 2024measured — dated from the channel’s first post
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/XclusiveETH

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 93% 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
@MegaWhalesCalls/3719316 Dec 2025, 23:09 UTC@XclusiveETH/9819 · this entry16 Dec 2025, 23:09 UTC1.00under a minute
@MegaWhalesCalls/3720224 Dec 2025, 11:27 UTC@XclusiveETH/9821 · this entry24 Dec 2025, 11:27 UTC1.00under a minute
@MegaWhalesCalls/3720424 Dec 2025, 14:54 UTC@XclusiveETH/9823 · this entry24 Dec 2025, 14:54 UTC1.00under a minute
@MegaWhalesCalls/3720527 Dec 2025, 18:27 UTC@XclusiveETH/9824 · this entry27 Dec 2025, 18:28 UTC1.00under a minute
@MegaWhalesCalls/372083 Feb 2026, 00:48 UTC@XclusiveETH/9826 · this entry3 Feb 2026, 00:48 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@MegaWhalesCalls5 (5/5 hand-verifiable sample passed)1.00under a minute@MegaWhalesCalls (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 5 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 7 comparable posts for this entry, running 12 December 2025 to 3 February 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 @MegaWhalesCalls. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 8 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

7817 Aug 2026, 13:02 — 781 subscribers8 Aug 2026, 01:47 — 781 subscribers7 Aug 2026, 13:028 Aug 2026, 01:47
2 measurements taken within a single day. 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 780–782 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 01:47781no change
7 Aug 2026, 13:02781first reading

Engagement

14 posts held, back to 5 April 2024the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 14 posts for this entry, the most recent from 3 February 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
3
Videos
1
Links
6

Lifetime counters from Telegram’s own channel header, read 8 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.

Video runtime
7s
Average length
7s

Measured directly from 1 video 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

33 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 87.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2987.9%
🔥26.06%
🫡26.06%

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

Measured over the 14 most recent posts we hold, published 5 April 2024 to 3 February 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

3 Feb 2026, 00:48 UTC694 views5 reactionsread 8 August 2026
Video

Yumi-Chan - $YUMI Momo’s Little Brother X: https://x.com/yumichansol Telegram: https://t.me/yumichansolana Website: https://yumi-chan.fun CA: n9Cuja8786cRLRCamKFAD23h3S5m7fJ7ufCdkGhpump

5

27 Dec 2025, 18:28 UTC811 views3 reactionsread 8 August 2026

WOLF | Wolfenstein (🔗ETH) 0x53a03E9EdF4Fa647268F19cF2eC509A7A1C52359 Pool Info: 🦄 DEX: UniSwap V2 📊 Mcap: $43,270 💧 Liq: $7,888 | 18.2288% 💸 TxFees: B $1.00 | S $2.50

3

24 Dec 2025, 14:54 UTC711 views5 reactionsread 8 August 2026

Hey everyone, if you’re searching for a good Bot to buy coins – this is the one I personally use, and in my opinion it’s the best among the rest. Fast, easy, and works on any chain 🚀👉 https://t.me/Sigma_buyBot?start=ref=5213146685

3🫡2

24 Dec 2025, 11:27 UTC578 viewsread 8 August 2026

SANTA | Santa's Little Helper (🔗ETH) 0xd0b612189c9b48fc966E8009681015b6b234d5D0 Pool Info: 🦄 DEX: UniSwap V2 📊 Mcap: $9,282 💧 Liq: $4,446 | 47.898% 💸 TxFees: B $0.50 | S $5.00

17 Dec 2025, 07:00 UTC571 views2 reactionsread 8 August 2026
Photo

NOOB | $NOOB Before the Alpha, Before the Wins, there was a $NOOB Previous: XMoney Vivek ETHZilla DankDoge CA: 0x744648B69006F3535f1Da1507AF80B7e41F0b491 CHART: https://dexscreener.com/ethereum/0x58a1025758db326081eeafb5f25f1aeaf54c056a X:https://x.com/NoobStillHere TG: https://t.me/NOOBonETH WEB: https://nooboneth.vip

2

16 Dec 2025, 23:09 UTC498 viewsread 8 August 2026
Photo

Aped $YEP Good CTO team pushing MC: 50k Duckie is a Saurolophus which is a dinosaur. Duckie is the key figure in The Land Before Time 🦖 "Yep Yep Yep" https://www.youtube.com/watch?v=knVGwaevQxI CA: 0x9f2D32834A556Af4c8cc65c84837130eFFdc6eef Telegram: https://t.me/YepYepCTO X: https://x.com/YepYepYepETH

12 Dec 2025, 18:51 UTC502 views4 reactionsread 8 August 2026
Photo

Good CTO Team behind MC: 17k $DOGE is a chaotic meme token on Ethereum — a satirical fusion of Elon Musk, Vivek Ramaswamy, Donald Trump, Sonic energy, classic Inu vibes, and pure “69” meme culture. A playful mix of crypto, culture, and chaos. Telegram: https://t.me/DOGEMEME69CTO Website: https://DOGEELON69.com Twitter: https://x.com/doge69elon Chart: https://dexscreener.com/ethereum/0x930e7bf4af5b1f60bdb3e9df44

4

Showing the 12 most recent of 14 posts we hold for @XclusiveETH. 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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“XclusiveETH (Official)” (@XclusiveETH), 781 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/XclusiveETH.

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.