Telegram RegisterThe public register of Telegram
Telegram profile photo for Wick_Deadly_Calls_007

Channel

Wick_Deadly_Calls_007

@Wick_Deadly_Calls_007

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

27subscribers

+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-1002867115027
TypeChannel
Username@Wick_Deadly_Calls_007
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live10 November 2026
Measurements held2
On Telegramt.me/Wick_Deadly_Calls_007

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 11 November 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 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 3 other registered channels. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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 (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@yumekocallz/575 Feb 2026, 03:11 UTC@Wick_Deadly_Calls_007/85 · this entry5 Feb 2026, 03:11 UTC1.00under a minute
@yumekocallz/7024 Mar 2026, 23:37 UTC@Wick_Deadly_Calls_007/98 · this entry24 Mar 2026, 23:37 UTC1.00under a minute
@ConanXcall/9024 Mar 2026, 23:37 UTC@Wick_Deadly_Calls_007/98 · this entry24 Mar 2026, 23:37 UTC1.00under a minute
@Wick_Deadly_Calls_007/98 · this entry24 Mar 2026, 23:37 UTC@PythonPlays/9424 Mar 2026, 23:37 UTC1.00under a minute
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
@yumekocallz9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (7–2)
@ConanXcall8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–0)
@PythonPlays8 (8/8 hand-verifiable sample passed)1.00under a minute@PythonPlays (6–2)

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 2 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 10 comparable posts for this entry, running 5 February 2026 to 4 July 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 4 channels, the one whose matching posts we hold earliest is @Wick_Deadly_Calls_007 — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · clone_source, last confirmed 11 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 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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

277 August 2026 — 27 subscribers11 August 2026 — 27 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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
11 Aug 2026, 07:4527no change
7 Aug 2026, 17:2627first reading

Engagement

20 posts held, back to 31 January 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 1 page of 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 4 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
54
Videos
4
Links
58

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

Recent posts

4 Jul 2026, 08:01 UTC20 viewsread 11 August 2026

$MANLET just tapped 13M! Everyone faded it early, and now people are FOMOing in. Instead of buying the news, buy before it happens. $ANSUM is next

11 May 2026, 12:18 UTC12 viewsread 11 August 2026
Forwarded from @WavesGemPhoto

$FORGE AI🔷 We are thrilled to unveil Forge AI the next-generation, AI-powered developer toolkit engineered to redefine smart contract development on the blockchain. Forge AI is an all-in-one development suite built to empower builders at every stage. It enables developers to: -Develop Smarter with our AI Co-Pilot, accelerating smart contract creation. -Audit with Confidence using the Guardian AI Auditor for automa…

11 May 2026, 12:17 UTC2 viewsread 11 August 2026
Forwarded from @MajorLaunchRadarPhoto

📳 Major Launch Radar Powered by @MajorTrending 🟣 SOL ⊕ 6h 29m - PS | Black ⊕ 8h 29m - PS | Nexora ⊕ 11h 29m - FL | whitewolf ⊕ 20h 29m - PS | USDU ⊕ 32h 29m - PS | GreyAlienSol ⊕ 33h 29m - FL | aurumgamma 🔵 ETH ⊕ 10h 59m - PS | AI1Net ⊕ 31h 29m - PS | Americanshib. ⊕ 37h 59m - PS | Pepe 🟡 BSC ⊕ 1h 59m - PS | aigodscoin ⊕ 10h 59m - PS | officialvegas ⊕ 33h 29m - PS | JijiCoin ⊕ 33h 29m - WL | FLAP. …

24 Mar 2026, 23:37 UTC2 viewsread 11 August 2026

🚀 Most Bullish Alex Info from Kimchi Spaces Ep #3 🚀 Alex (MyDoge / DogeOS co-founder) dropping HEAVY support for $KIMCHI + real Elon/CB Doge proximity: 1. Alex is HOLDING $KIMCHI & calling upside "I got kimchi coins. [...] Kimchi is, like, 400k market cap. That's half 1,000,000. [...] Kimchi on Anoncoin. Half 1,000,000 market cap." → Public bag + quick 25%+ MC pump potential. 2. Alex offering DIRECT intro to House…

24 Mar 2026, 23:36 UTC2 viewsread 11 August 2026
Forwarded from @spawnscallsPhoto

UPDATE RIP🪙 The team is working hard and has done 3x from the spot I shared yesterday✅ CHART: https://dexscreener.com/solana/hpethuncrnhkvaywkiudiqzvxbnjdgqxfmxqbkrnj7s6 Tg: https://t.me/chucknorrisxtrends

24 Mar 2026, 23:36 UTC2 viewsread 11 August 2026
Forwarded from @gubbinscallsPhoto

A different coin with the same name passed it

24 Mar 2026, 23:35 UTC2 viewsread 11 August 2026
Forwarded from @naughtyapescall

EVamkzzXKUmxKoxJ6R4E21JhFQq2HyyGs6rbqvHkpump

19 Mar 2026, 14:33 UTC4 viewsread 11 August 2026
Forwarded from @calledbyblakeePhoto

Holy shit what a cook!! This team never dissapoints 53k —> 3M ath making it an absolutely diabolical 55x if you were early!! Lock TF in! Notis on, so you don’t miss my next mooner

19 Mar 2026, 14:33 UTC14 viewsread 11 August 2026
Forwarded from @spawnscallsPhoto

🚨 New Alpha Loading A new project from a team with multiple successful launches is about to hit the market. Built to move fast and send hard. 👀 Launch: Saturday — 15:00 UTC Stay close. Smart money is watching. https://t.me/earlymemerunner

19 Mar 2026, 14:33 UTC14 viewsread 11 August 2026
Forwarded from @spidersjournalPhoto

Elon just retweeted another chibi post he will definitely push this feature hard DbC9CvSLwUt9v3Bf9Eo8F6WERgtfq2xKuiTcJx8Cpump

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

“Wick_Deadly_Calls_007” (@Wick_Deadly_Calls_007), 27 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Wick_Deadly_Calls_007.

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.