Telegram RegisterThe public register of Telegram
Telegram profile photo for Raoul Pal RV

Channel

Raoul Pal RV

@RaoulGMI

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry

13subscribers

+6 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003769687434
TypeChannel
Username@RaoulGMI
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live4 November 2026
Measurements held8
Confirmed unchanged2 times, most recently 4 November 2026
On Telegramt.me/RaoulGMI

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 2 October 2026 and assigned it the closest of 31 fixed categories, at 54% 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 (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@krcapitals/573610 Aug 2026, 17:28 UTC@RaoulGMI/2502 · this entry11 Aug 2026, 10:04 UTC1.0017 hours
@krcapitals/573710 Aug 2026, 17:28 UTC@RaoulGMI/2503 · this entry11 Aug 2026, 10:04 UTC1.0017 hours
@krcapitals/574110 Aug 2026, 18:04 UTC@RaoulGMI/2506 · this entry11 Aug 2026, 10:04 UTC1.0016 hours
@krcapitals/574310 Aug 2026, 19:36 UTC@RaoulGMI/2508 · this entry11 Aug 2026, 10:04 UTC1.0014 hours
@krcapitals/573910 Aug 2026, 17:31 UTC@RaoulGMI/2504 · this entry11 Aug 2026, 10:04 UTC0.9617 hours
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
@krcapitals5 (5/5 hand-verifiable sample passed)0.9916 hours@krcapitals (5–0)

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. 5 of the 5 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 11 August 2026 to 11 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).

Of the group of 2 channels, the one whose matching posts we hold earliest is @krcapitals. That is a statement about our reading window, not a claim of authorship.

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

6139.56 August 2026 — 7 subscribers7 August 2026 — 6 subscribers12 August 2026 — 6 subscribers18 September 2026 — 8 subscribers3 October 2026 — 12 subscribers13 October 2026 — 11 subscribers20 October 2026 — 10 subscribers28 October 2026 — 13 subscribers6 August 202628 October 2026
8 measurements spanning 83 days, net +6. 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 5–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Oct 2026, 01:0813+3
20 Oct 2026, 09:1810-1
13 Oct 2026, 23:1711-1
3 Oct 2026, 21:0012+4
18 Sept 2026, 14:228+2
12 Aug 2026, 19:476no change
7 Aug 2026, 03:066-1
6 Aug 2026, 06:037first reading

Engagement

15 posts held, back to 11 August 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 15 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

11 Aug 2026, 10:04 UTC1 viewsread 12 August 2026
Photo

https://tronscan.org/#/transaction/387e3cd81edb2157a59c72c9b4e1ea688ff3236efee3d51e30dee6f23bd9c2a3 Payment Proof Of August 10 2026 Payment Successful Sent via USDT

11 Aug 2026, 10:04 UTC1 viewsread 12 August 2026
Photo

https://tronscan.org/#/transaction/ae34bf8fbf7dcf48a4d5af9bfcd1e1b6cbf9257111a8c5e81dfe554abd09ec68 Payment Proof Of August 10 2026 Payment Successful Sent via USDT

11 Aug 2026, 10:04 UTC1 viewsread 12 August 2026

FOREX GDP DAILY PERFORMANCE MONDAY 10/08/2026 Gold Buy➡️ 65 Pips Vip|Public Gold Buy➡️ Invalidated Vip|Public Gold Sell➡️ 85 Pips Vip|Public Gold Buy➡️ 240 Pips Vip|Public GbpUsd Buy➡️ 40 Pips Vip Gold Buy➡️ 74 Pips Vip Gold Buy➡️ 115 Pips Vip Gold Buy➡️ 100 Pips Vip|Public Gold Sell➡️ 85 Pips Vip|Public TOTAL WINNING : 804 PIPS ✅ TOTAL LOSS : 0 PIPS ❌ TOTAL SETUP : 8/9

11 Aug 2026, 10:04 UTC1 viewsread 12 August 2026

ANNOUNCEMENT – PUMP & BOOST PROGRAM UPDATE 🔥 Massive Payouts are LIVE! Congratulations to everyone who participated in our recent pump & boost initiative — your timing and engagement have paid off! 🔥 Payouts are currently being processed 🔥 Participants are receiving their rewards 🔥Everything is running smoothly and on schedule This is just the beginning — stay alert for future opportunities. Your next win might b…

11 Aug 2026, 10:04 UTC1 viewsread 12 August 2026
Photo

PATIENCE PAID!!! Running into profit now! Making way to our TP1 Let's secure some of our profit and hold some to our TP.

11 Aug 2026, 10:04 UTC1 viewsread 12 August 2026
Photo

TP 1 LOCKED AND SECURED 40 pips TP just secured after our TP1 triggered. Took some times, but always worth it! Securef position, Hold to TP2 ok

11 Aug 2026, 10:04 UTC1 viewsread 12 August 2026
Photo

Last Setup With Me! GOLD RUNNING 85+ PIPS Let's collect partial PROFITS and set the rest at BREAKEVEN for a zero-risk trade The knowledge we gain from each experience is what prepares us toward SUCCESS!🪙

11 Aug 2026, 10:03 UTC1 viewsread 12 August 2026
Photo

Round 5, BOOM BOOM, More Profits Secured! GOLD RUNNING 74+ PIPS Let's collect partial PROFITS and set the rest at BREAKEVEN for a zero-risk trade

11 Aug 2026, 10:03 UTC1 viewsread 12 August 2026

❤️‍🔥 What’s Holding You Back? Money is being made daily inside the VIP – while you’re still watching from the sidelines 👀 ✅ Real signals ✅ Real profits ✅ Real traders leveling up every week So ask yourself... What’s stopping you from being next? Because the only difference between you and them is… ➡️ TAKING ACTION 📩 DM me when you’re ready to stop watching and start earning.

Showing the 12 most recent of 15 posts we hold for @RaoulGMI. 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 6 registered channels — 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.

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

“Raoul Pal RV” (@RaoulGMI), 13 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/RaoulGMI.

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.