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 4 other registered channels. They sit inside a group of 6 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 (6 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. 12 of the 42 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 20 comparable posts for this entry, running 2 August 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 6, the earliest publisher we hold is @TCGFORYOU. That is a statement about our reading window, not a claim of authorship.
Views per post sit far below this size band
2.9 average views per post against 5,122 subscribers — an engagement rate of 0.056%. Across the 8,378 registered channels in the same cohort — 3,163–9,997 subscribers, posting mainly in English — the middle half sit between 3.48% and 19.1%, with a median of 8.83%.
What this was computed from
Window
30 days (17 July 2026 – 16 August 2026)
Posts measured
27 of 27 published in the window (27 exact, 0 rounded by Telegram)
Views totalled
77
Mature posts only
0.058% over 25 posts read at least 24h after publication
When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the keys clone_copy · clone_source · err_low, last confirmed 16 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 5 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.
4 measurements spanning 7 days, net -4. 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,121–5,127 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Aug 2026, 08:26
5,122
-2
11 Aug 2026, 04:56
5,124
-2
7 Aug 2026, 18:01
5,126
no change
7 Aug 2026, 17:53
5,126
first reading
Engagement
27 posts held, back to 2 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 7 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
0.056%
avg views ÷ 5,122 subscribers
Avg views / post
2.9
27 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
27
of 27 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 11 August 2026
Posts held
27 (2 August 2026 – 11 August 2026)
Views total
77
Reactions total
—
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
12 Aug 2026, 04:44 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.
#GOLD showed a triangle pattern breakout and a sideways market breakout. Price provided an entry opportunity and moved into profit. Price can still move higher, and a re-entry could be possible.
#BTC goes sideways and dropped hard and strongly yesterday at the NY Open. Price is still unclear and there is not much to do here. LTF turns bearish; now we can expect a short-term drop in the market.
The FOMC decides today, and the bond market has already made up its mind. The 2-year Treasury yield, the cleanest read on where policy goes next, has been sitting above the Federal Funds Rate since April, and the gap is the widest it has been since November 2022. That is not the pricing of a market waiting for a cut; it leans toward the next move being a hike.
A cut today would surprise most of that positioning, and…
Strategy increased its USD Reserve by $650M and repurchased $109M of $STRC. This increased USD Duration by 143 days to 2.7 yrs and tightened STRC's BTC Credit by 10 bps. As of 8/9/26, we hold ₿840,447 in our BTC Reserve and $4.65B in our USD Reserve.
#US30 UPDATE:
#US30 is moving as per the plan and has reached a new all-time high, up around 3%. Hold your positions if you have taken longs and are expecting a new ATH.
#BTC WEEKLY TF UPDATE:
#BTC is still moving sideways, bounded within the Weekly Key area. This means we need to wait an additional week to see a breakout of the zone.
#BITCOIN DAILY TF UPDATE:
#BITCOIN has slowly retraced the entire week, moving up and up, still following the range with nothing happening. Nothing can be anticipated here; we need to wait for the price to move in either direction or for clarity.
Last week Bitcoin outran the equity indices, absorbing an oil shock that left stocks flat and finishing ahead of both. That relative strength has faded. Bitcoin spent this week sliding while US and European stocks sat still, and the break came on Monday: from that session onward it has not been level with stocks again. Oil gave last week's spike back and ended the week the weakest of the four.
One week of relative w…
#SNX gave a break of the consolidation and formed the small range there too. Its a sign for short-selling but market is trying to sustaining at the bottom of the range. If it break the small range too (Blue Box) then get into the short positions too.
#BTC again experienced a short-term rejection from the resistance area, and a move lower may be imminent. However, anticipating this too early would be premature; wait for the candlestick confirmation on the Daily TF.
Smart money is buying this bear market. Retail is selling into it.
BTC whale balances climbed to ~3.06M coins through 2026, accumulating as price broke below $60K.
ETH shows a clear split: large cohorts (10k+) at record highs, while smaller wallets keep distributing.
BTC and XRP are trading near realized price, ETH is already below it, the zone that's historically marked cycle lows.
#BANANA is forming a bull flag pattern following the break of the downtrend channel pattern. Now, place stops in the break of the pattern and take the long and short positions depending on the closing side.
Showing the 12 most recent of 27 posts we hold for @Gigantic_Rebirth_GCR. 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 14 August 2026 — this
entry's latest reading, not the date you are reading this.
“Gigantic Rebirth (GCR)” (@Gigantic_Rebirth_GCR), 5,122 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Gigantic_Rebirth_GCR.
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.
