Telegram RegisterThe public register of Telegram

Channel

HACKED

@CoinHuntUk

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Polls · Cite this entry

1,383subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001810968529
TypeChannel
Username@CoinHuntUk
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/CoinHuntUk

Topic

Other / unclassifiable — 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 95% 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 2 other registered channels. 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
@CoinVoteUk/627014 Feb 2025, 11:57 UTC@CoinHuntUk/7495 · this entry14 Feb 2025, 11:58 UTC1.00under a minute
@CoinVoteUk/627315 Feb 2025, 01:57 UTC@CoinHuntUk/7498 · this entry15 Feb 2025, 04:32 UTC1.002.6 hours
@CoinVoteUk/627415 Feb 2025, 05:24 UTC@CoinHuntUk/7499 · this entry15 Feb 2025, 05:24 UTC1.00under a minute
@CoinVoteUk/627515 Feb 2025, 08:15 UTC@CoinHuntUk/7500 · this entry15 Feb 2025, 08:15 UTC1.00under a minute
@CoinVoteUk/627615 Feb 2025, 09:15 UTC@CoinHuntUk/7501 · this entry15 Feb 2025, 09:15 UTC1.00under a minute
@CoinHuntUk/7503 · this entry15 Feb 2025, 10:45 UTC@CoinVoteUk/627815 Feb 2025, 10:45 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@CoinVoteUk12 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (84)
@CoinMooner_US12 (8/8 hand-verifiable sample passed)1.00under a minuteeven

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 10 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 12 comparable posts for this entry, running 14 February 2025 to 15 February 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 3, the earliest publisher we hold is @CoinVoteUk. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · 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 2 other registered channels, 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

1,3831,3871,3857 August 2026 — 1,387 subscribers7 August 2026 — 1,387 subscribers7 August 2026 — 1,386 subscribers10 August 2026 — 1,383 subscribers7 August 202610 August 2026
4 measurements spanning 3 days, net -4. 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 1,382–1,388 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 18:141,383-3
7 Aug 2026, 11:471,386-1
7 Aug 2026, 09:471,387no change
7 Aug 2026, 09:361,387first reading

Engagement

20 posts held, back to 14 February 2025the 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 20 posts for this entry, the most recent from 16 February 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

436 reactions across 16 posts, in 9 distinct kinds. The most used accounts for 19.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8519.5%
💯7717.7%
🕊7016.1%
🐳6915.8%
💋6915.8%
👌6314.4%
👍10.229%
👏10.229%
🔥10.229%

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 16 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 436reactions 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 14 February 2025 to 16 February 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

15 Feb 2025, 11:52 UTC≈3,220 views21 reactionsread 7 August 2026
Photo

🚨🚨🚨 PUMP ANNOUNCEMENT 🚨🚨🚨 Here are the details: 📅 DATE: 16Feb / Tomorrow ⏰ TIME: 16:15 PM (GMT) 📈 Exchange 1: RAYDIUM (Solana Network) 🪙 PAIRS: SOL (Solana Network) on Raydium 💰 Expected Growth: 1000%+ Exactly at GMT, we will publish the names, contracts, and all essential details about the TOKENS we will be pumping on both exchanges. ❗️The Pumps will take place simultaneously on Raydium Exchanges. 1️⃣ The faste

💯74👌3💋3🕊3🐳1

15 Feb 2025, 11:39 UTC≈3,140 views29 reactionsread 7 August 2026
Photo

POSTPONED FOR TOMMOROW

8🐳6💋5🕊4👌3💯2👏1

15 Feb 2025, 11:12 UTC≈3,110 views25 reactionsread 7 August 2026

⏰ 3 MINUTES REMAINING! ⏰ 🔥 Important: Raydium (Solana Network): Ensure Phantom or Solflare Wallet is connected and ready. Quick Recap: Raydium (Solana): Have SOL ready to buy. ⏳ Act fast once the token is announced—time is almost up!

🕊7🐳54💯4👌3💋2

15 Feb 2025, 11:10 UTC≈3,080 views30 reactionsread 7 August 2026

‼️ 5 MINUTES LEFT ‼️ 🔥 Open Raydium NOW! For Newcomers: Raydium (Solana Network): Buy with SOL 🕒 10 minutes to buy after the coin is announced. 💰 20 minutes to sell after the SELL SIGNAL for maximum profit. ⏰ Get ready—time is almost up!

🕊96👌6💯6🐳2💋1

15 Feb 2025, 11:05 UTC≈3,010 views35 reactionsread 7 August 2026

💥 10 MINUTES LEFT 💥 🚀 Get Ready for the Pump! Step-by-Step Guide: 1️⃣ 5 minutes before the announcement: Open Raydium (SOL) and stay tuned here. 2️⃣ Coin revealed here in the channel. 3️⃣ Buy immediately: SOL on Raydium. 4️⃣ You’ll have 10 minutes to act. 5️⃣ Buy early for maximum profits! ⏰ Turn ON notifications to stay updated! 💰 Time’s ticking—act fast!

🐳97🕊7💋5👌4💯3

15 Feb 2025, 11:02 UTC≈2,960 views24 reactionsread 7 August 2026

🔥 15 MINUTES LEFT 🔥 🚨 Suggested Buy: 1 SOL (Raydium) 📈 Platforms: Raydium (SOL/USDC) 💰 Market Cap: $9.8k 🎯 Goal: $100k 🚀 Potential Profits: 1000% (10x) Prepare Now: Raydium: Load SOL in Phantom/Solflare ⏰ Act fast for maximum profits!

6🐳5💋5💯5👌1🔥1🕊1

15 Feb 2025, 10:45 UTC≈2,970 views31 reactionsread 7 August 2026

⏺ 30 MINUTES LEFT ⏺ 💰 Targeting 1000%-2000% Gains! Exchanges: Slippage: 2% (Enable Expert Mode) 🔹 Raydium (SOL): Pair: SOL/USDC Slippage: 1%-3% How to Prepare: Load SOL in Phantom Wallet/Solflare for Raydium. ⏰ Act fast when coins are revealed—early buyers profit most!

👌9💋6🕊6🐳54💯1

15 Feb 2025, 10:15 UTC≈2,920 views13 reactionsread 7 August 2026
Photo

💥 1 HOUR LEFT! 💥 🎯 Get Ready for Today’s Pump! 🚀 Step-by-Step Guide: 1️⃣ 5 minutes before the announcement: Open Raydium (SOL) and stay in this channel. 2️⃣ Target coin will be revealed right here. 3️⃣ After the announcement: Raydium: Use SOL to purchase the token. 4️⃣ You’ll have 10 minutes to act—buy early for maximum profits! ⏰ Turn ON notifications and stay ready! 🔔 📈 Act fast, secure your gains!

💯4👌3🕊31🐳1💋1

15 Feb 2025, 09:15 UTC≈2,920 views24 reactionsread 7 August 2026
Photo

💥 2 HOURS UNTIL THE PUMP! 💥 The countdown has begun! 🚨 Important Details: 1️⃣ Coin Announcement: Target coins will be revealed in just 2 hours. Stay ready! 2️⃣ Raydium (Solana Network): Additional opportunities for Solana traders. 💡 How to Prepare: SOL (Solana): Load up Phantom Wallet or Solflare Wallet. ⏰ Time is ticking—be ready to act fast for maximum profits!

8🐳5🕊4👌3💋2💯2

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

15 Feb 2025, 04:32 UTCAnonymous Poll551 voters

Vote For You Community| Winner Will Get Instant 100000$ USDT Investment With Proof & Free 1 Week Promo. Voter Must Vote & Join Our Channel, Community Must Pin Our Poll, Let's Vote & Win. BEST OF LUCK

  1. SAFEMOON CTO (SOL)10%
  2. yesnoerror1%
  3. Oval office1%
  4. LC | SOL2%
  5. $1 CTO -$1 to $13%
  6. Mumu the Bull | $MUMU1%
  7. KIKI CAT Global Chat77%
  8. Broccoli Inu | $BROC - Community2%
  9. $HONEY Community1%
  10. AzurCryptus on SUI2%

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 14 February 2025 to 16 February 2025. 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.

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

“HACKED” (@CoinHuntUk), 1,383 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/CoinHuntUk.

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.