Telegram RegisterThe public register of Telegram
Telegram profile photo for Russian Insiders VIP Free

Channel

Russian Insiders VIP Free

@russianinsidersbyCF

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Cite this entry

1,508subscribers

-7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001603305985
TypeChannel
Username@russianinsidersbyCF
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/russianinsidersbyCF

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 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 why it has no browse page of its own yet.

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 2 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)
Posted firstThenOverlapGap
@FedRussianInsiders_Vip/894818 Jun 2026, 19:33 UTC@russianinsidersbyCF/6490 · this entry18 Jun 2026, 19:34 UTC1.00under a minute
@FedRussianInsiders_Vip/894925 Jun 2026, 19:02 UTC@russianinsidersbyCF/6491 · this entry25 Jun 2026, 19:03 UTC1.00under a minute
@FedRussianInsiders_Vip/89513 Jul 2026, 20:42 UTC@russianinsidersbyCF/6492 · this entry3 Jul 2026, 20:42 UTC1.00under a minute
@FedRussianInsiders_Vip/895219 Jul 2026, 15:02 UTC@russianinsidersbyCF/6493 · this entry19 Jul 2026, 15:02 UTC1.00under a minute
@FedRussianInsiders_Vip/895320 Jul 2026, 17:57 UTC@russianinsidersbyCF/6494 · this entry20 Jul 2026, 17:57 UTC1.00under a minute
@FedRussianInsiders_Vip/895621 Jul 2026, 18:45 UTC@russianinsidersbyCF/6497 · this entry21 Jul 2026, 18:45 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@FedRussianInsiders_Vip9 (8/8 hand-verifiable sample passed)1.00under a minute@FedRussianInsiders_Vip (90)
@FedRussianInsidersOfficial9 (8/8 hand-verifiable sample passed)1.00under a minute@FedRussianInsidersOfficial (90)

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. 2 of the 18 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 16 comparable posts for this entry, running 12 May 2026 to 6 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 3, the earliest publisher we hold is @FedRussianInsidersOfficial. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 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 2 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.

Growth

1,5081,5151,511.57 August 2026 — 1,515 subscribers7 August 2026 — 1,515 subscribers8 August 2026 — 1,514 subscribers11 August 2026 — 1,515 subscribers14 August 2026 — 1,508 subscribers7 August 202614 August 2026
5 measurements spanning 7 days, net -7. 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 1,507–1,516 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 20:251,508-7
11 Aug 2026, 02:071,515+1
8 Aug 2026, 06:321,514-1
7 Aug 2026, 09:161,515no change
7 Aug 2026, 09:041,515first reading

Engagement

20 posts held, back to 12 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
10.5%
avg views ÷ 1,508 subscribers
Avg views / post
158
14 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
14
of 20 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 6 August 2026
Posts held20 (12 May 20266 August 2026)
Views total2,209
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 18:11 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.

Recent posts

6 Aug 2026, 03:55 UTC78 viewsread 7 August 2026
Photo

$BTC ANALYSIS -------------------- August has a reputation for being BTC's wildcard month. Average return is slightly positive, but the median sits at negative 6.99%, when August turns red, it turns hard. 2022 dropped 13.88%, 2018 fell 9.27%, 2015 got hit for 18.67%. Not a panic signal, just a reason to tighten up. History leans cautious for the back half of the month, keep risk management tight regardless of your b

5 Aug 2026, 15:56 UTC81 viewsread 7 August 2026
Photo

USDT’s 60-day market cap change has fallen -$4B, nearing its sharpest contraction on record, per CryptoQuant.

2 Aug 2026, 21:54 UTC117 viewsread 7 August 2026
Photo

🔥#BTR Update🔥 Target 1: $0.0185✅ Target 2: $0.0190✅ Target 3: $0.0198✅ Target 4: $0.0208✅ Profit: 121.2% on 5x lev🚀 BOOM!! Another high reached and 2 more targets destroyed, that’s how we roll🔥

31 Jul 2026, 15:28 UTC145 viewsread 7 August 2026
Photo

🔥$BTR Update🔥 Target 1: $0.0185✅ Target 2: $0.0190✅ Profit: 71.8% on 5x lev🚀 Reaching a high of $0.0196, $BTR did just what we expected… Stay tuned for more!!🔥

28 Jul 2026, 15:19 UTC189 viewsread 7 August 2026
Photo

🔥$BULLA Update🔥 Target 10: $0.014✅ NEW HIGH: $0.017✅ Profit: 372% on 5x lev🚀 We knew about $BULLA when we signaled it, our members entered, it dipped a bit, we waited, …bought even more, and it paid off huge. That’s the power of our signals, and with the market now bottoming out, we’re about to see even bigger moves Stay tuned for the next, which will be 2x bigger

27 Jul 2026, 17:39 UTC166 viewsread 7 August 2026
Photo

🔥$BULLA Update🔥 Patience pays off with interests. Target 1: $0.0092✅ Target 2: $0.0094✅ Target 3: $0.0096✅ Target 4: $0.0098✅ Target 5: $0.0101✅ Target 6: $0.0105✅ Target 7: $0.0110✅ Target 8: $0.0117✅ Target 9: $0.0128✅ NEW HIGH: $0.0138✅ Profit: 312% on 5x lev🚀

27 Jul 2026, 12:29 UTC137 viewsread 7 August 2026

🔥 $AAVE Update 🔥 Target 1: 100.00 ✅ Profit: 32% (5x lev.) 🔥 -------------------- Yours truly, Fed. Russian Insiders®

23 Jul 2026, 18:18 UTC213 viewsread 7 August 2026
Photo

📍 SIGNAL ID: #G178 COIN: $AAVE/USDT Direction: ⬆️ LONG Type: Swing -------------------- Position Size: 2-4% Leverage: 3-5x -------------------- ENTRY: 93.50 - 94.00 🔘 Target 1: 100.00 🔘 Target 2: 107.00 🔘 Target 3: 115.00 🔘 Target 4: 125.00 🔘 Target 5: 137.00 🔘 Target 6: 150.00 🚫 STOP LOSS: 85.00 AAVE reclaimed the 90.0–94.0 demand zone with a strong 8H impulse, confirming a bullish structure flip off the long-st

22 Jul 2026, 15:35 UTC190 viewsread 7 August 2026
Photo

🔥$BULLA Update🔥 Target 1: $0.0092✅ Target 2: $0.0094✅ Target 3: $0.0096✅ Target 4: $0.0098✅ Target 5: $0.0101✅ Target 6: $0.0105✅ Target 7: $0.0110✅ Target 8: $0.0117✅ NEW HIGH: $0.0126✅ Profit: 247% on 5x lev🚀 Another high for $BULLA!! Profits taken and on to the next!!🔥

21 Jul 2026, 18:45 UTC179 viewsread 7 August 2026
Photo

🔥#CHILLGUY (Binance Futures)🔥 Same setup as $BANK before it went parabolic. Leverage: 3-5x Entry: Below 0.011 Targets: 0.0112 - 0.0114 - 0.0117 - 0.0121 - 0.0128 - 0.0135 - 0.0146 - 0.0160 - 0.018 - 0.021 - 0.024 - 0.030 - 0.038 - 0.045 - 0.060 - 0.081 - OPEN SL: Below 0.0077

21 Jul 2026, 17:35 UTC161 viewsread 7 August 2026
Photo

🚨LIFETIME UPGRADE SALE🚨 (Only For Current VIP Members) -------------------- Upgrade your current VIP membership to an UNLIMTED LIFETIME Membership!!🔥 🔥LIFETIME UPGRADE SALE: $250🔥 LIFETIME EXCLUSIVE EXTRAS: ✅EARLY ACCESS (Projects/Gems/Features, Lifetime members ONLY) No spots will be saved. First come, first served. See you inside brothers!! -------------------- 👉Step 1) Payment USDT TRC20 TVT7iKrWnkWrrfioTKtdAq

21 Jul 2026, 12:38 UTC161 viewsread 7 August 2026

If you longed just $1,000 worth of $BANK on 5x leverage when we told you to, you’d be sitting on $62,550 right now. That’s the power of our signals… And with the market starting to explode again, we’re about to see even bigger setups very soon🚀

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

Citation-graph rank

Citation-graph rank — 1,136,185 of 1,480,944entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“Russian Insiders VIP Free” (@russianinsidersbyCF), 1,508 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/russianinsidersbyCF.

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.