This channel offers educational content only and should not be considered as financial advice. This channel is operated under the brand of @vipdrprofit.
Created
Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
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 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 word for word on 3 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)
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 18 comparable posts for this entry, running 30 July 2026 to 7 August 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 4, the earliest publisher we hold is @CryptoPlanw. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, 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 3 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.
26 measurements spanning 91 days, net -197. 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 8,514–8,771 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)
Subscribers
Change
6 Nov 2026, 06:48
8,544
-19
3 Nov 2026, 04:49
8,563
-10
31 Oct 2026, 05:17
8,573
-35
28 Oct 2026, 14:10
8,608
-8
25 Oct 2026, 08:26
8,616
-8
22 Oct 2026, 05:59
8,624
-3
19 Oct 2026, 08:17
8,627
-13
16 Oct 2026, 04:18
8,640
-25
12 Oct 2026, 18:18
8,665
+37
6 Oct 2026, 03:01
8,628
-17
28 Sept 2026, 14:54
8,645
+46
18 Sept 2026, 18:21
8,599
-12
14 Sept 2026, 04:15
8,611
-16
10 Sept 2026, 16:01
8,627
-1
5 Sept 2026, 11:37
8,628
-9
1 Sept 2026, 08:16
8,637
-1
29 Aug 2026, 00:14
8,638
-17
25 Aug 2026, 23:55
8,655
-11
23 Aug 2026, 08:47
8,666
-25
19 Aug 2026, 20:33
8,691
first reading
Engagement
131 posts held, back to 30 July 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 38 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
9.16%
avg views ÷ 8,544 subscribers
Avg views / post
783
44 posts measured
Reaction rate
1.68%
reactions ÷ views · ER floor
Posts in window
44
of 131 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 43 of 44 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 November 2026
Posts held
131 (30 July 2026 – 7 November 2026)
Views total
34,442
Reactions total
569
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Nov 2026, 00:13 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
Photos
≈1,020
Videos
≈3
Links
≈1
Lifetime counters from Telegram’s own channel header, read 8 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
1,564 reactions across 129 posts, in 2 distinct kinds. The most used accounts for 84.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
1,326
84.8%
👍
238
15.2%
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 129 of the 131 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 1,564 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 131 most recent posts we hold, published 30 July 2026 to 7 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.
Recent posts
Telegram’s own ‘edited’ marker: 12 of 44 posts held from the last 30 days (27.3%) 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).
$BTC Short Scalp Setup:
Entry: CMP till 76200
TP: 73700
SL: 76639
isclaimer: This content is for educational and informational purposes only and is not financial advice. I am not a licensed financial advisor. Trading and crypto carry a high risk of loss, including total loss of capital. Always do your own research (DYOR) and consult a licensed professional before making financial decisions.
#TraderGauls 🎭
🚨 $REZ | The Next Potential Upbit KRW Listing Play? 👀
The on-chain clues are getting more interesting...
Here's why $REZ is on my radar:
🔹 Potential Upbit KRW Listing: Around 38.1M $REZ was reportedly transferred from a suspected team wallet to an address linked with Upbit promotional activity.
🔹 The Pattern Looks Familiar: Similar transfers were seen before $MPLX, $SLX, $BMT, and $NIL received their KRW listings…
Greetings frens
🚨 I THINK I'VE FOUND THE NEXT POTENTIAL UPBIT KRW LISTING PLAY.
Last time I shared $NMR before the hype and it did 50%
Now I'm seeing interesting on-chain activity that could point toward another potential Upbit KRW listing.
Nothing is guaranteed, but the data is definitely worth paying attention to.
Should I share the full research and thesis in the Gem Calls series? 👀🔥
Let me know through your…
🚨 Market Update Video is Live!
In today's video we'll cover:
📊 $BTC LTF trigger
📈 $ETH LTF trigger with a deeper analysis
📉 Overall altcoin market update
🎯 Key triggers on a few altcoins I'm closely watching
If you're planning to trade this week, don't miss this one. It covers the levels and confirmations I'm waiting for before taking any positions.
Watch it, take notes, and let's stay one step ahead of the marke…
$ETH LTF UPDATE:
Our Fav pattern in play, Right now Strucuture is Brearish so we'll wait for a Structure break for playing this LTF LONG
isclaimer: This content is for educational and informational purposes only and is not financial advice. I am not a licensed financial advisor. Trading and crypto carry a high risk of loss, including total loss of capital. Always do your own research (DYOR) and consult a licensed p…
📊 $BTC Update
After the dump, here's what I'm seeing on the LTF:
✅ Open Interest increasing
✅ Futures CVD increasing
✅ Long/Short ratio increasing
✅ New longs entering near the bottom
✅ A lot of spoofing in the order book
The big question is...
Are these smart money positions or just retail chasing the bottom?
Personally, I think it's mostly retail, and they could get wiped out if the market isn't done shaking o…
📊 $RUNE & $BCH Trade Update
Closing both positions in a small 1.5–2% drawdown after both entries were filled.
The setups were technically solid, but when news starts driving the market, technical analysis often takes a back seat.
Capital preservation always comes first. We'll take the small loss, stay patient, and wait for the next high-probability opportunity.
#TraderGauls 🎭
📊 $BNB Trade Update
Our $BNB trade hit the stop loss. It was a tight stop, resulting in only a -1.5% loss.
The main reason is the sharp sell-off in the US stock market, and as usual, crypto is following the risk-off move.
In this type of market, price can slice through support and resistance levels very quickly, so protecting capital becomes more important than chasing trades.
Losses are part of the game. We keep…
$BNB BUYING SETUP:
Entry Limit: 704-705
TP: 738
SL: 693
Disclaimer: This content is for educational and informational purposes only and is not financial advice. I am not a licensed financial advisor. Trading and crypto carry a high risk of loss, including total loss of capital. Always do your own research (DYOR) and consult a licensed professional before making financial decisions.
#TraderGauls 🎭
📊 $UNI Trade Update
The $UNI trade moved nearly 5% in our favor, which was enough to move the stop loss to breakeven.
Later, price came back and hit our entry, making this a breakeven trade, not a winning trade.
If my approach was to take profits after every 1–2% move and immediately move the stop to entry, then yes, this could have been counted as a winning trade.
But that's not how I trade.
I'm not trying to m…
❤8👍3
Showing the 12 most recent of 131 posts we hold for @TraderGaulsVIP. 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
@TraderGaulsVIP edited 1 post 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
18 August 2026
Most recent edit
18 August 2026
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.
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 6 November 2026 — this
entry's latest reading, not the date you are reading this.
“Trader Gauls 🏟” (@TraderGaulsVIP), 8,544 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/TraderGaulsVIP.
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.