The most accurate and profitable trading community in the world, since 2017
JOIN VIP:
Support: @DmitriFRI_Adm
🔥FRI BINGX BONUS🔥
($5k INSTANT & NO KYC):
https://bit.ly/FED5000
Created
Between 1 March 2025 and 31 July 2025— 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 10 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 1 other registered channel. They sit inside a group of 4 channels that share the same post bodies 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.
Matching posts — open both and compare (5 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. 1 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 17 comparable posts for this entry, running 28 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 @FedRussianInsiders. 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 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.
7 measurements spanning 4 days, net -371. 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 19,435–19,918 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 05:57
19,491
-2
11 Aug 2026, 02:47
19,493
-126
10 Aug 2026, 01:21
19,619
-177
9 Aug 2026, 04:21
19,796
-64
8 Aug 2026, 06:01
19,860
-2
7 Aug 2026, 18:30
19,862
no change
7 Aug 2026, 18:26
19,862
first reading
Engagement
31 posts held, back to 28 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 15 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
0.225%
avg views ÷ 19,491 subscribers
Avg views / post
43.8
31 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
31
of 31 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
Window
Rolling 30 days · latest post in window 12 August 2026
Posts held
31 (28 July 2026 – 12 August 2026)
Views total
1,358
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 23:43 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,660
Videos
≈2
Links
≈182
Lifetime counters from Telegram’s own channel header, read 12 August 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.
$BTC ANALYSIS
--------------------
$BTC/USDT is trading at $63,841 inside a rising wedge that has held since the $57,750 July lows, currently pressing back toward the lower trendline near $63,400. Structure has been climbing steadily but the wedge is tightening and the risk of a sharp move is building.
Break $65,000 and $67,000 opens up with the upper trendline as the ceiling to clear. Lose $63,400 and the wedge cra…
$TRX ANALYSIS
--------------------
$TRX/USDT is trading at $0.3350 after breaking clean out of the ascending trendline from the June $0.3106 base, tagging fresh highs at $0.3380. Two months of grinding higher lows just paid off with a sharp breakout candle.
Hold above $0.3300 and $0.3400 opens up with $0.35 next. Lose $0.3280 and price falls back into the range with $0.3240 as the retest level. Fresh breakout, momen…
$LINK ANALYSIS
--------------------
$LINK/USDT is trading at $8.405 right at the apex of a seven month descending triangle, with the year long trendline from $14.20 and the rising support from $7.10 converging into one final decision point. Months of compression are about to resolve.
Break the trendline near $8.50 and $9.00 opens up with $9.80 next. Lose $8.00 and the triangle breaks down, exposing $7.40 and $7.10. …
$UNI ANALYSIS
--------------------
$UNI/USDT is trading at $3.935 right at the collision point of two major trendlines, the year long descending resistance from $12 and the rising channel from the June $2.32 base. Price just tagged $4.60 and pulled back, this crossroads decides the next major direction.
Break $4.60 with conviction and the year long downtrend finally breaks, opening $5.40 and beyond. Lose $3.70 and p…
🛎GEM ANNOUNCEMENT🛎
Market conditions are perfect and in a few minutes we will share a gem we’ve found that will completely change the game.
Exchanges: Binance Futures
$SOL ANALYSIS
--------------------
$SOL/USDT is trading at $76.48 and pushing hard into the apex of a three month symmetrical triangle, with the descending resistance from $87 and the rising trendline from $60.40 squeezing tight. Buyers just broke to fresh local highs, the coil is finally testing patience on both sides.
Break $80 and $82 opens up with $87 as the descending trendline target. Lose $74 and the trendlin…
$ETH ANALYSIS
--------------------
$ETH/USDT is trading at $1,919 inside a clean rising channel from the $1,513 June low. Structure remains fully bullish, buyers keep defending every dip and momentum stays firmly with the trend.
Break $1,960 and fresh highs open up fast. Lose $1,845 and price rolls back to $1,805 with the channel base as the deeper cushion. Trend intact, dips still belong to the buyers.
👉Join our VI…
$FET ANALYSIS
--------------------
$FET/USDT is trading at $0.1377 inside a descending channel that has held since May, with the upper trendline near $0.1450 capping the recent bounce. Price flushed to $0.1320 and reclaimed a bit, sellers still control the range.
Break $0.1450 and $0.1520 opens up with $0.1580 next. Lose $0.1360 and $0.1320 gets retested with $0.13 as the deeper floor. Channel intact, fade the highs…
$LINK ANALYSIS
--------------------
$LINK/USDT is trading at $8.302 and grinding higher along the ascending trendline from the $7.00 June base. Rejected from $8.85 but every dip keeps getting bought at the line, structure stays bullish.
Break $8.40 and $8.60 opens up with $8.85 as the ceiling to reclaim. Lose $8.00 and the trendline gets tested with $7.80 waiting below. Trend intact, buyers still defending.
👉Join ou…
Showing the 12 most recent of 31 posts we hold for @FedRussianInsidersTG. 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.
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 12 August 2026 — this
entry's latest reading, not the date you are reading this.
“Fed. Russian Insiders OFFICIAL®️” (@FedRussianInsidersTG), 19,491 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/FedRussianInsidersTG.
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.