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 2 other registered channels. This entry also sits inside a group of 3 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.
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 0 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 6 comparable posts for this entry, running 2 June 2026 to 2 June 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 3 channels, the one whose matching posts we hold earliest is @Kouroshtajianpv — 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 3 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
Growth history is still building. We hold no measurements for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
Engagement
17 posts held, back to 2 June 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 17 posts for this entry, the most recent from 2 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 149
- Videos
- 4
- Links
- 29
Lifetime counters from Telegram’s own channel header, read 17 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
2 Jun 2026, 14:46 UTC5 viewsread 17 August 2026 كيفية البدء
👇👇
http://t.me/TRADER_INVESTT
2 Jun 2026, 14:46 UTC4 viewsread 17 August 2026 تم الإيداع
2 Jun 2026, 14:46 UTC4 viewsread 17 August 2026 Photo
Photo, posted without a caption
2 Jun 2026, 14:46 UTC4 viewsread 17 August 2026 نعم، المبلغ موجود بالفعل في محفظتي. يمكنك إرسال تفاصيل الدفع بعملة USDT إليّ.
2 Jun 2026, 14:46 UTC4 viewsread 17 August 2026 لقد كنت أنتظر الحصول على راتبي حتى أتمكن من استثمار 1000 دولار معك
2 Jun 2026, 14:46 UTC4 viewsread 17 August 2026 لقد انضممت إلى قناتكم منذ شهرين، ولاحظت أنها المنصة الأكثر ربحية التي رأيتها على الإطلاق.
2 Jun 2026, 14:46 UTC4 viewsread 17 August 2026 كل عام وأنتم بخير بمناسبة الشهر الجديد
2 Jun 2026, 14:46 UTC4 viewsread 17 August 2026 Photo
ربحت اليوم 1734 دولارًا. لا أعرف كيف أشكرك.
2 Jun 2026, 14:46 UTC4 viewsread 17 August 2026 بصراحة، أنت الأفضل. هذه أفضل بداية لي في هذا الشهر الجديد.
2 Jun 2026, 14:45 UTC3 viewsread 17 August 2026 Photo
⭐️ قد تلاحظون أننا نبيع من الأعلى إلى الأسفل 🌟
لدينا روبوتات ذكاء اصطناعي 🤖 وأنظمة متطورة عالية التقنية تقوم بالبيع المباشر بعد إعطائها أمرًا بتفريغ العملات عند بلوغها أعلى سعر ممكن.
لا يمكن لأحد البيع قبل الأنظمة والروبوتات.
هذا هو سر النجاح 💎
نشتري ونجمع عند أدنى سعر، ثم نضخ السيولة لخلق ذروة، ونبيع فورًا عند تلك الذروة. 🚀
😀 لذا، عندما يسأل البعض: لماذا لا تطلقون القنبلة قبل وقوعها وتتركون الجميع يدخلون بأنفسهم؟ …
2 Jun 2026, 14:45 UTC3 viewsread 17 August 2026 Photo
وهدف الربح 1 هو 180 نقطة ✅
لنغلق الصفقة الآن ونحدد نقطة التعادل إذا كنت ترغب في الاحتفاظ بها الآن ‼️
يا لها من بداية رائعة ليومنا 🔥
2 Jun 2026, 14:45 UTC3 viewsread 17 August 2026 Photo
١٣٠ نقطة، هيا بنا! ✅
لنغلق الصفقة الآن ونحدد نقطة التعادل إذا كنت ترغب في الاحتفاظ بها الآن! ‼️
نحن متخصصون في المضاربة السريعة! 🔥🔥🔥
Showing the 12 most recent of 17 posts we hold for @Kouroshtajianpv. 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.
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. This entry holds no subscriber measurement yet, so the line below cites the entry itself.
“👑Kourosh Tajian I Crypto” (@Kouroshtajianpv). Telegram Register, tgregister.com/channel/Kouroshtajianpv.
No subscriber measurement is held for this entry yet, so there is no history to download — a download that asserted zero readings would be a false statement, not an empty one.