Telegram RegisterThe public register of Telegram
Telegram profile photo for CPG Trade | سیگنال کریپتو

Channel

CPG Trade | سیگنال کریپتو

@CryptoPrGulf

On this record: Topic · Observations · Growth · Engagement · What this channel posts · View velocity · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Cite this entry

1,191,253subscribers

+751,013 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among the largest entries.

Register entry

Telegram ID-1002330884060
TypeChannel
Username@CryptoPrGulf
Descriptionخلیج همیشه فارس💪🏻 مسئولیت سیگنال ها بر عهده خود کاربر هست تبلیغات نداریم❌‌ 💎 VIP Signals 💰Win rate:+97 Contact: @Noqtezan VIP BOT : @CPGAGENT Tutorial : @CPG_Trade
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 November 2026
Measurements held66
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/CryptoPrGulf

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 8 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. 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
@Radcryptosignal/4072622 Oct 2026, 10:01 UTC@CryptoPrGulf/9137 · this entry22 Oct 2026, 10:14 UTC0.9913 minutes
@Radcryptosignal/4006224 Sept 2026, 21:26 UTC@CryptoPrGulf/7880 · this entry24 Sept 2026, 21:55 UTC0.9828 minutes
@Radcryptosignal/4060917 Oct 2026, 11:33 UTC@CryptoPrGulf/8812 · this entry17 Oct 2026, 11:46 UTC0.9813 minutes
@Radcryptosignal/4069920 Oct 2026, 21:29 UTC@CryptoPrGulf/9063 · this entry20 Oct 2026, 21:37 UTC0.988 minutes
@Radcryptosignal/3921815 Aug 2026, 15:54 UTC@CryptoPrGulf/6385 · this entry15 Aug 2026, 16:24 UTC0.9730 minutes
@Radcryptosignal/402221 Oct 2026, 16:47 UTC@CryptoPrGulf/8124 · this entry1 Oct 2026, 17:07 UTC0.9720 minutes
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
@Radcryptosignal16 (8/8 hand-verifiable sample passed)0.9813 minutes@Radcryptosignal (16–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. 16 of the 16 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 636 comparable posts for this entry, running 7 August 2026 to 17 November 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).

Views and reactions moved apart

On 721 of the 1,055 posts we watched over 30 days, the view counter climbed while the reaction counter stayed where it was — by more than this channel’s own reactions-per-view rate can account for. That rate, measured on this entry, is 0.0630 reactions per view.

Each interval, as we read it — views and reactions before and after
PostOverViewsReactionsExpected
/101737 Nov 2026, 12:20 UTC12 minutes4,400 → 5,110at least +700687 → 688at most +2+44.1
/101737 Nov 2026, 12:20 UTC22 minutes5,110 → 6,050at least +930688 → 689at most +2+58.6
/101737 Nov 2026, 12:20 UTC55 minutes6,050 → 7,910at least +1,850689 → 693at most +5+116.5
/101737 Nov 2026, 12:20 UTC55 minutes7,910 → 9,450at least +1,530693 → 693at most +1+96.4
/101737 Nov 2026, 12:20 UTC55 minutes9,450 → 11,100at least +1,550693 → 693at most +1+97.7
/941626 Oct 2026, 13:06 UTC31 minutes5,110 → 6,710at least +1,590713 → 721at most +9+100.2
/941626 Oct 2026, 13:06 UTC35 minutes6,710 → 8,850at least +2,130721 → 722at most +2+134.2
/941626 Oct 2026, 13:06 UTC30 minutes8,850 → 10,500at least +1,550722 → 725at most +4+97.7
/941626 Oct 2026, 13:06 UTC48 minutes11,400 → 13,400at least +1,900726 → 727at most +2+119.7
/965629 Oct 2026, 10:58 UTC30 minutes5,770 → 7,060at least +1,280712 → 714at most +3+80.6
/965629 Oct 2026, 10:58 UTC35 minutes7,060 → 8,300at least +1,230714 → 716at most +3+77.5
/965629 Oct 2026, 10:58 UTC34 minutes8,300 → 9,590at least +1,280716 → 718at most +3+80.6
/965629 Oct 2026, 10:58 UTC60 minutes9,590 → 11,300at least +1,610718 → 719at most +2+101.4
/972829 Oct 2026, 22:49 UTC56 minutes9,050 → 10,600at least +1,450712 → 714at most +3+91.3
/972829 Oct 2026, 22:49 UTC60 minutes13,300 → 16,100at least +2,700722 → 730at most +9+170.1
/972829 Oct 2026, 22:49 UTC43 minutes18,900 → 22,300at least +3,300733 → 733at most +1+207.9
/972829 Oct 2026, 22:49 UTC76 minutes22,300 → 28,500at least +6,100733 → 735at most +3+384.3
/972929 Oct 2026, 22:54 UTC56 minutes9,200 → 10,900at least +1,600760 → 773at most +14+100.8
/972929 Oct 2026, 22:54 UTC60 minutes13,800 → 17,100at least +3,200790 → 810at most +21+201.6
/972929 Oct 2026, 22:54 UTC43 minutes20,300 → 24,300at least +3,900827 → 842at most +16+245.7
/972929 Oct 2026, 22:54 UTC76 minutes24,300 → 31,500at least +7,100842 → 845at most +4+447.3
/99813 Nov 2026, 15:52 UTC31 minutes5,720 → 6,800at least +1,070701 → 702at most +2+67.4
/99813 Nov 2026, 15:52 UTC34 minutes6,800 → 7,850at least +1,040702 → 703at most +2+65.5
/99813 Nov 2026, 15:52 UTC35 minutes7,850 → 9,050at least +1,190703 → 707at most +5+75.0
/99813 Nov 2026, 15:52 UTC55 minutes9,050 → 10,600at least +1,450707 → 708at most +2+91.3
/99823 Nov 2026, 15:59 UTC31 minutes5,740 → 7,310at least +1,560697 → 701at most +5+98.3
/99823 Nov 2026, 15:59 UTC34 minutes7,310 → 8,860at least +1,540701 → 702at most +2+97.0
/99823 Nov 2026, 15:59 UTC35 minutes8,860 → 10,600at least +1,640702 → 703at most +2+103.3
/99823 Nov 2026, 15:59 UTC55 minutes10,600 → 13,300at least +2,600703 → 705at most +3+163.8
/100915 Nov 2026, 09:59 UTC31 minutes4,060 → 5,010at least +940702 → 704at most +3+59.2
/100915 Nov 2026, 09:59 UTC34 minutes5,010 → 6,300at least +1,280704 → 705at most +2+80.6
/100915 Nov 2026, 09:59 UTC30 minutes6,300 → 7,410at least +1,100705 → 708at most +4+69.3
/100915 Nov 2026, 09:59 UTC60 minutes7,410 → 8,770at least +1,350708 → 708at most +1+85.0
/1027910 Nov 2026, 06:38 UTC35 minutes3,140 → 3,920at least +770694 → 699at most +6+48.5
/1027910 Nov 2026, 06:38 UTC55 minutes4,470 → 5,290at least +810699 → 700at most +2+51.0
/1027910 Nov 2026, 06:38 UTC35 minutes5,290 → 6,130at least +830700 → 700at most +1+52.3
/1027910 Nov 2026, 06:38 UTC3.8 hours9,420 → 11,900at least +2,380705 → 705at most +1+149.9
/1031210 Nov 2026, 16:30 UTC31 minutes5,250 → 6,390at least +1,130674 → 676at most +3+71.2
/1031210 Nov 2026, 16:30 UTC34 minutes6,390 → 7,670at least +1,270676 → 677at most +2+80.0
/1031210 Nov 2026, 16:30 UTC35 minutes7,670 → 8,870at least +1,190677 → 680at most +4+75.0
/1031210 Nov 2026, 16:30 UTC55 minutes10,000 → 12,200at least +2,100681 → 686at most +6+132.3

Expected is the view gain multiplied by this channel’s own prior reactions-per-view rate over the same post — not a corpus average, so a channel whose audience never reacts is compared only against itself. Every interval is credited in the direction that makes the observation harder to record, never easier: t.me renders views and reactions to three significant figures above ~1,000, so a raw delta can be a rendering step. Every delta below is at least 4 x the coarser reading's step, the view gain is discounted by a full step and the reaction gain credited with one. Measured by tgregister velocity.py (our own t.me/s/ readings).

What this does and does not say. It says the two counters moved apart, by more than rounding and more than this channel’s own history predicts. It asserts no cause. Views arriving from outside Telegram, an embedded or forwarded copy of the post, and a burst of readers who simply do not react all produce this shape. This detector has recorded very few observations across the whole register, and its precision has not been measured; treat it as an anomaly worth looking at, not as a finding.

Recorded under the keys clone_copy · view_reaction_decoupling, last confirmed 18 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.

Growth

440,2401,191,253815,746.57 August 202615 November 2026
66 measurements spanning 100 days, net +751,013. 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 327,588–1,303,905 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
15 Nov 2026, 19:201,191,253+21,065
12 Nov 2026, 09:191,170,188+16,248
10 Nov 2026, 07:181,153,940-1,462
8 Nov 2026, 22:401,155,402-573
7 Nov 2026, 12:371,155,975+8,739
6 Nov 2026, 11:211,147,236+7,724
5 Nov 2026, 09:041,139,512+399
4 Nov 2026, 11:191,139,113-526
3 Nov 2026, 12:401,139,639+652
2 Nov 2026, 10:461,138,987+4,340
1 Nov 2026, 07:301,134,647+7,094
31 Oct 2026, 07:061,127,553+26,643
30 Oct 2026, 05:411,100,910+8,992
29 Oct 2026, 08:551,091,918+15,008
28 Oct 2026, 04:571,076,910+11,880
27 Oct 2026, 05:391,065,030+14,924
26 Oct 2026, 03:051,050,106+22,841
25 Oct 2026, 01:201,027,265+20,052
23 Oct 2026, 22:301,007,213+37,786
22 Oct 2026, 20:01969,427first reading

Engagement

2,868 posts held, back to 7 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 224 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.04%
avg views ÷ 1,191,253 subscribers
Avg views / post
12,400
1,264 posts measured
Reaction rate
5.88%
reactions ÷ views · ER floor
Posts in window
1,264
of 2,868 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 November 2026
Posts held2,868 (7 August 2026 – 18 November 2026)
Views total15,669,330
Reactions total920,760
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 12:50 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
≈2,500
Videos
≈12
Links
≈37

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

View velocity

How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.

Computed from 1,085 of this channel’s own posts over the last 30 days (30 of the 24-hour readings behind this are interpolated, not measured directly): across 938 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 1.7 hours of being posted; a typical post has already reached 40.9% of its 24-hour view count within the first hour, and 80.6% within the first six; the median 24-hour reach across those posts is 11,000 views — 0.923% of this channel’s own subscriber count (90th percentile 19,960).

8 most recently posted, with a view-velocity reading
PostReadingsLatest readingCurve24h reachHalf of last-observed views by
/1066318 Nov 2026, 11:55 UTC224 minutes – 55 minutes old3,410 views ~619 reactionsno checkpoint reading yetnot yet at 24h24 minutesupper bound — already past half at first reading · provisional — final view count still climbing
/1066218 Nov 2026, 07:34 UTC97 minutes – 5.3 hours old11,500 views ~717 reactions60 minutes: 3,161 interp. → 3.0 hours: 7,291 interp.still climbing at last readingnot yet at 24h2.3 hoursprovisional — final view count still climbing
/1066118 Nov 2026, 07:33 UTC99 minutes – 5.3 hours old10,800 views ~690 reactions60 minutes: 3,089 interp. → 3.0 hours: 7,100 interp.still climbing at last readingnot yet at 24h2.2 hoursprovisional — final view count still climbing
/1066018 Nov 2026, 07:30 UTC912 minutes – 5.3 hours old10,200 views ~690 reactions60 minutes: 3,060 interp. → 3.0 hours: 6,705 interp.still climbing at last readingnot yet at 24h2.1 hoursprovisional — final view count still climbing
/1065918 Nov 2026, 07:29 UTC913 minutes – 5.4 hours old9,590 views ~692 reactions60 minutes: 2,955 interp. → 3.0 hours: 6,287 interp.still climbing at last readingnot yet at 24h2.1 hoursprovisional — final view count still climbing
/1065818 Nov 2026, 07:25 UTC102 minutes – 5.4 hours old9,150 views ~694 reactions60 minutes: 2,925 interp. → 3.0 hours: 5,986 interp.still climbing at last readingnot yet at 24h2.1 hoursprovisional — final view count still climbing
/1065718 Nov 2026, 07:25 UTC102 minutes – 5.4 hours old7,760 views ~683 reactions60 minutes: 2,730 interp. → 3.0 hours: 5,392 interp.still climbing at last readingnot yet at 24h1.9 hoursprovisional — final view count still climbing
/1065618 Nov 2026, 07:19 UTC109 minutes – 5.5 hours old8,230 views ~698 reactions60 minutes: 3,025 interp. → 3.0 hours: 5,715 interp.still climbing at last readingnot yet at 24h1.8 hoursprovisional — final view count still climbing

Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.

Reaction mix

723,824 reactions across 1,000 posts, in 4 distinct kinds. The most used accounts for 25.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤187,33825.9%
🫡183,70125.4%
👍178,37824.6%
🔥174,40724.1%

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 1,000 of the 1,000 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 723,824 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 26 October 2026 to 18 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.

Telegram Stars

Stars received
75
across the posts below
Posts paid on
18
of 1,000 we hold a reading for · 2%
Most on one post
50
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @CryptoPrGulf. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 26 October 2026 to 18 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 156 of 1,264 posts held from the last 30 days (12.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).

18 Nov 2026, 11:55 UTC≈3,410 views619 reactionsread 18 November 2026
Photo

PIEVERSE فول تارگت 🔄

👍229❤201🫡105🔥84

18 Nov 2026, 07:34 UTC≈11,500 views717 reactionsread 18 November 2026

〰️SIGNAL PERSIAN GULF〰️ #BLESS/USDT (25X〰️〰️〰️〰️〰️) 〰️ENTRY:0.0128 〰️TARGETS: ✏️:0.0132 ✏️:0.0136 ✏️:0.0142 〰️STOP LOSS:0.010700 Crypto Persian Gulf 〰️

❤233👍177🔥166🫡141

Signed Radin

18 Nov 2026, 07:33 UTC≈10,800 views690 reactionsread 18 November 2026

Bless Long 0.0128

❤237👍178🔥163🫡112

Signed Radin

18 Nov 2026, 07:30 UTC≈10,200 views690 reactionsread 18 November 2026

Kgen استاپ و تارگت ها مجدد چک بشه

🫡192❤181🔥177👍140

Signed Radin

18 Nov 2026, 07:29 UTC≈9,590 views692 reactionsread 18 November 2026

هردو سیگنال فرصت ورود داره ⏰

🔥204❤191👍157🫡140

Signed Radin

18 Nov 2026, 07:25 UTC≈9,150 views694 reactionsread 18 November 2026

〰️SIGNAL PERSIAN GULF〰️ #EVAA/USDT (25X〰️〰️〰️〰️〰️) 〰️ENTRY:3.68 〰️TARGETS: ✏️:3.82 ✏️:4.15 ✏️:4.50 〰️STOP LOSS:3.266 Crypto Persian Gulf 〰️

❤207👍172🔥166🫡149

Signed Radin

18 Nov 2026, 07:25 UTC≈7,760 views683 reactionsread 18 November 2026

Evaa Long 3.68

🔥201👍172❤160🫡150

Signed Radin

18 Nov 2026, 07:19 UTC≈8,230 views698 reactionsread 18 November 2026

〰️SIGNAL PERSIAN GULF〰️ #KGEN/USDT (25X〰️〰️〰️〰️〰️) 〰️ENTRY:0.08250 〰️TARGETS: ✏️:0.08373 ✏️:0.08500 ✏️:0.08700 〰️STOP LOSS:0.07400 Crypto Persian Gulf 〰️

🔥206🫡189❤184👍119

Signed Radin

18 Nov 2026, 07:18 UTC≈5,230 views685 reactionsread 18 November 2026

Kgen Long 0.008250

🔥194👍189❤168🫡134

Signed Radin

18 Nov 2026, 07:10 UTC≈5,210 views693 reactionsread 18 November 2026

Zama ظاهرا درحرکته🔼🔼

🔥253👍183🫡138❤119

Signed Radin

18 Nov 2026, 07:01 UTC≈5,300 views743 reactionsread 18 November 2026

روزتون بخیر〰️

❤354🔥180🫡119👍90

Signed Radin

17 Nov 2026, 21:52 UTC≈11,400 views1,994 reactionsread 18 November 2026
Photo

شبتون به همین زیبایی 〰️

🫡599❤511🔥501👍383

Signed Radin

Showing the 12 most recent of 2,868 posts we hold for @CryptoPrGulf. 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

@CryptoPrGulf edited 15 posts 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
9 August 2026
Most recent edit
18 November 2026

Posts recorded as deleted after publishing

We recorded 21 posts on @CryptoPrGulf as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
19 September 2026
Most recent seen missing
15 November 2026
Median time before seen missing
5.2 hours
Seen missing in the last 30 days
18

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.

9 Nov 2026, 13:04 UTCAnonymous Poll438 voters

بنظرتون مقاومتو میشکنه یا نه؟🏴‍☠️

  1. بله56%
  2. خیر48%

The shares total 104%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not 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 1,000 most recent posts we hold (the sample is capped at 1,000), published 26 October 2026 to 18 November 2026. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

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

“CPG Trade | سیگنال کریپتو” (@CryptoPrGulf), 1,191,253 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/CryptoPrGulf.

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.