Telegram RegisterThe public register of Telegram
Telegram profile photo for Wicktator Chart Analysis

Channel

Wicktator Chart Analysis

@Wicktator

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

9,700subscribers

-637 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001453629607
TypeChannel
Username@Wicktator
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 November 2026
Measurements held48
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/Wicktator

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 100% 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 1 other registered channel. 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
@Wicktator/3671 · this entry17 May 2026, 18:06 UTC@Crypto_Wick/47117 May 2026, 18:06 UTC1.00under a minute
@Crypto_Wick/47225 May 2026, 10:33 UTC@Wicktator/3672 · this entry25 May 2026, 10:33 UTC1.00under a minute
@Wicktator/3678 · this entry28 May 2026, 13:47 UTC@Crypto_Wick/47828 May 2026, 13:47 UTC1.00under a minute
@Wicktator/3680 · this entry29 May 2026, 15:35 UTC@Crypto_Wick/48029 May 2026, 15:35 UTC1.00under a minute
@Crypto_Wick/4852 Jun 2026, 17:17 UTC@Wicktator/3685 · this entry2 Jun 2026, 17:17 UTC1.00under a minute
@Wicktator/3686 · this entry8 Jun 2026, 22:08 UTC@Crypto_Wick/4868 Jun 2026, 22:08 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
@Crypto_Wick13 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (9–4)

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 4 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 32 comparable posts for this entry, running 9 May 2026 to 19 October 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 @Wicktator — 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 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 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

9,70010,33710,018.56 August 2026 — 10,337 subscribers6 August 2026 — 10,337 subscribers7 August 2026 — 10,336 subscribers8 August 2026 — 10,329 subscribers9 August 2026 — 10,326 subscribers10 August 2026 — 10,321 subscribers11 August 2026 — 10,317 subscribers12 August 2026 — 10,309 subscribers13 August 2026 — 10,302 subscribers14 August 2026 — 10,293 subscribers16 August 2026 — 10,290 subscribers17 August 2026 — 10,284 subscribers18 August 2026 — 10,281 subscribers19 August 2026 — 10,270 subscribers20 August 2026 — 10,261 subscribers21 August 2026 — 10,246 subscribers23 August 2026 — 10,240 subscribers24 August 2026 — 10,233 subscribers25 August 2026 — 10,225 subscribers26 August 2026 — 10,219 subscribers28 August 2026 — 10,212 subscribers29 August 2026 — 10,206 subscribers30 August 2026 — 10,200 subscribers31 August 2026 — 10,204 subscribers1 September 2026 — 10,200 subscribers2 September 2026 — 10,197 subscribers3 September 2026 — 10,177 subscribers5 September 2026 — 10,174 subscribers9 September 2026 — 10,167 subscribers11 September 2026 — 10,155 subscribers13 September 2026 — 10,145 subscribers15 September 2026 — 10,144 subscribers16 September 2026 — 10,129 subscribers19 September 2026 — 10,105 subscribers25 September 2026 — 10,082 subscribers4 October 2026 — 10,039 subscribers8 October 2026 — 10,017 subscribers14 October 2026 — 9,994 subscribers17 October 2026 — 9,972 subscribers20 October 2026 — 9,935 subscribers23 October 2026 — 9,905 subscribers25 October 2026 — 9,854 subscribers29 October 2026 — 9,803 subscribers1 November 2026 — 9,791 subscribers4 November 2026 — 9,772 subscribers7 November 2026 — 9,758 subscribers11 November 2026 — 9,741 subscribers16 November 2026 — 9,700 subscribers6 August 202616 November 2026
48 measurements spanning 101 days, net -637. 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 9,604–10,433 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 48
Measured (UTC)SubscribersChange
16 Nov 2026, 03:179,700-41
11 Nov 2026, 01:469,741-17
7 Nov 2026, 09:509,758-14
4 Nov 2026, 17:569,772-19
1 Nov 2026, 15:389,791-12
29 Oct 2026, 05:409,803-51
25 Oct 2026, 20:279,854-51
23 Oct 2026, 02:269,905-30
20 Oct 2026, 02:559,935-37
17 Oct 2026, 05:199,972-22
14 Oct 2026, 06:449,994-23
8 Oct 2026, 18:3910,017-22
4 Oct 2026, 05:4210,039-43
25 Sept 2026, 13:3710,082-23
19 Sept 2026, 04:2110,105-24
16 Sept 2026, 21:1910,129-15
15 Sept 2026, 02:1510,144-1
13 Sept 2026, 14:2010,145-10
11 Sept 2026, 17:0010,155-12
9 Sept 2026, 01:2010,167first reading

Engagement

42 posts held, back to 9 May 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 32 pages 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 42 posts for this entry, the most recent from 19 October 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

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.

Recent posts

19 Oct 2026, 14:39 UTC≈1,310 viewsread 7 November 2026

PUMP - Now that’s a name with expectations! Strong rally complete. Expecting a pullback into $0.0023–$0.0028 before the next big push higher. Targets: $0.011 → $0.020. Let the pullback finish, wait for the reversal, then look for the pump. Click Here For Full Chart

18 Oct 2026, 13:49 UTC≈1,500 viewsread 7 November 2026

BITCOIN - $70K before $130K? Expecting a pullback towards $68K–$71K before the next major move higher. That’s the area to watch for bullish confirmation. The bigger picture points towards a potential $150K–$200K move, with pullbacks along the way. Full Analysis: The pullback setup The next leg higher The bigger picture Open the breakdowns above for the full explanation of the setup, the key levels to watch and th…

15 Oct 2026, 18:20 UTC≈1,660 viewsread 7 November 2026

USDCHF - Trendline broken. 1000pip Trade Active ✅ The rejection from resistance has now been followed by a breakdown. The short setup is underway, with a potential 1,000-pip move lower in focus. Entry, stop loss and targets are marked on the daily setup. View the USDCHF Daily Setup

27 Sept 2026, 19:03 UTC≈2,730 viewsread 7 November 2026
Video

GBPUSD - move complete. +450 pips ✅ From triangle resistance straight down to support. The move mapped out in VIP has now played out in full. Watch the original forecast unfold, candle by candle. Verify the original VIP setup for yourself: https://www.tradingview.com/chart/GBPUSD/YUEVkqhW-VIP-GBPUSD-SHORT/ VIP members get setups like this + daily updates as the market develops. Unlock VIP Access ✅ Alternative VIP…

18 Sept 2026, 17:24 UTC≈3,090 viewsread 7 November 2026
Photo

USDJPY - straight into profit 🚀 Posted earlier today. Sell zone identified. Rejection confirmed. Price moved immediately in our favour. The bigger wave 5 move is still in play, with 153.00 / 151.00 as our targets. The setup was mapped before the move - now we let the market do the work. If you want more setups like this, support our work across our platforms. The more support we get, the more free setups we’ll co…

18 Sept 2026, 09:24 UTC≈2,490 viewsread 7 November 2026

USDJPY - 700 pip setup 🚀 We’ve been tracking the higher-timeframe structure and price is now moving into the area we’ve been waiting for. The setup is simple: Rejection from the sell zone + trendline break = wave 5 lower. Targets: 153.00 / 151.00 Full chart and breakdown posted here 👇 ✅TradingView 📱 Instagram / CryptoWick Instagram VIP members get setups like this + daily updates as the structure develops. Unloc…

17 Sept 2026, 17:37 UTC≈2,220 viewsread 7 November 2026

We’ve got plenty more setups like this already running in profit. If you want to catch the next big swing, join VIP before the next move gets underway. Daily updates. Clear structure. No missed moves. Unlock VIP Access ✅ Alternative VIP Link ✅ We'll see you in there 🫡

17 Sept 2026, 17:35 UTC≈2,020 viewsread 7 November 2026
Video

GBPUSD - before & after 🫠 We identified the higher-timeframe triangle early and mapped out the move into wave E before it happened. The setup was posted privately for VIP, with daily updates as the structure developed so members didn’t miss a thing. Another move planned before the market delivered. View the original VIP setup here: https://www.tradingview.com/chart/GBPUSD/YUEVkqhW-VIP-GBPUSD-SHORT/

17 Sept 2026, 17:31 UTC≈1,700 viewsread 7 November 2026
Video

NZDUSD - before & after 🎯 This setup was posted privately for VIP before the move played out, and price followed the roadmap cleanly. VIP members get the full setup + daily updates, so they stay up to date as the structure develops and don’t miss any changes along the way. View the original VIP setup here: https://www.tradingview.com/chart/NZDUSD/kKIrULey-VIP-NZDUSD-SHORT/ We plan the trade, you trade the plan.

17 Sept 2026, 05:15 UTC≈1,770 viewsread 7 November 2026
Photo

Just a few of our recent swings 🎯 The market has been great to us. Patience, clear analysis and letting the bigger moves play out. Now we’re at a pivotal point, with more big swing setups lined up. Join VIP for the full breakdowns and see what we’re preparing for next 👇 Unlock VIP Access ✅ Alternative VIP Link ✅ We plan the trade, you trade the plan 🫡

11 Sept 2026, 14:45 UTC≈2,440 viewsread 7 November 2026

Cardano - Final Drop Into The Buy Zone 🔥 We’re expecting a final 5th wave down to complete wave C of the 5-3-5 correction. Simply put: one last move lower to finish the pullback before we look for the next major rally. The highlighted buy zone is where we’ll be watching for a bullish reaction and confirmation. Full breakdown on TradingView 🎯

3 Sept 2026, 04:02 UTC≈3,060 viewsread 7 November 2026
Photo

GOLD - THE PLAN IN MOTION 🔥 Wave 4 is doing exactly what the framework said it would. We mapped it before it started. Now we're in it, positions running 🚀 Plan the trade. Trade the plan.

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

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“Wicktator Chart Analysis” (@Wicktator), 9,700 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/Wicktator.

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.