Telegram RegisterThe public register of Telegram

Channel

The Bull Vs The Bear

@TheBullvsTheBear

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

2,934subscribers

-4 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-1001206619130
TypeChannel
Username@TheBullvsTheBear
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/TheBullvsTheBear

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 98% 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. 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
@TheBullvsTheBear/12289 · this entry13 May 2026, 05:56 UTC@BusinessTradingSignals/732713 May 2026, 05:57 UTC1.00under a minute
@BusinessTradingSignals/733120 May 2026, 14:26 UTC@TheBullvsTheBear/12293 · this entry20 May 2026, 14:26 UTC1.00under a minute
@BusinessTradingSignals/733226 May 2026, 09:15 UTC@TheBullvsTheBear/12294 · this entry26 May 2026, 09:15 UTC1.00under a minute
@BusinessTradingSignals/733528 May 2026, 03:35 UTC@TheBullvsTheBear/12297 · this entry28 May 2026, 03:35 UTC1.00under a minute
@BusinessTradingSignals/73389 Jun 2026, 05:30 UTC@TheBullvsTheBear/12300 · this entry9 Jun 2026, 05:30 UTC1.00under a minute
@BusinessTradingSignals/73399 Jun 2026, 06:26 UTC@TheBullvsTheBear/12301 · this entry9 Jun 2026, 06:26 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@BusinessTradingSignals9 (8/8 hand-verifiable sample passed)1.00under a minute@BusinessTradingSignals (81)

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 8 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 9 comparable posts for this entry, running 13 May 2026 to 27 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).

Across the whole group of 2, the earliest publisher we hold is @TheBullvsTheBear — which is this entry. 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 1 other registered channel, 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

2,9342,9382,9367 August 2026 — 2,938 subscribers7 August 2026 — 2,938 subscribers10 August 2026 — 2,934 subscribers7 August 202610 August 2026
3 measurements spanning 4 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 2,933–2,939 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 18:052,934-4
7 Aug 2026, 21:232,938no change
7 Aug 2026, 04:162,938first reading

Engagement

19 posts held, back to 9 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 27 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
150.0%
👍150.0%

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

Measured over the 19 most recent posts we hold, published 9 May 2026 to 27 June 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.

Recent posts

27 Jun 2026, 07:05 UTC612 views1 reactionsread 7 August 2026
Photo

That breakout on #DXY is troubling #BTC right now That correlation is still pretty much working out.

1

27 Jun 2026, 07:03 UTC558 viewsread 7 August 2026

Everyone has a strategy in a bull market. Very few have one that survives a bear. That's usually where you find out what you actually know versus what you got lucky on.

17 Jun 2026, 11:19 UTC629 views1 reactionsread 7 August 2026

HAPPY FOMC DAY 🫡 🇺🇸 THE FED WILL OFFICIALLY ANNOUNCE ITS INTEREST RATE DECISION TODAY AT 2 PM ET! IF RATE < 3.50% → MARKET PUMPS IF RATE = 3.75% → MARKET STAYS FLAT IF RATE > 4.00% → MARKET DUMPS ALL EYES ON THE RELEASE TODAY 2:30P

👍1

13 Jun 2026, 11:29 UTC654 viewsread 7 August 2026
Photo

#BTC isn't done yet 👀 Still respecting the long term trendline.

9 Jun 2026, 06:26 UTC675 viewsread 7 August 2026
Photo

#BTC 2-day RSI has reached oversold territory again. After the recent flush, a few days of consolidation wouldn't be surprising before the next move.

9 Jun 2026, 05:30 UTC633 viewsread 7 August 2026
Photo

#BTC Bottom zone The Quarterly chart may provide clues about where #BTC could find its cycle low. Historically, it has often revisited these quarterly FVGs before forming a major bottom. Current zone: $56.8K - $44.6K

28 May 2026, 03:35 UTC633 viewsread 7 August 2026
Photo

Bitcoin falls under $74,000 #ETH falls under $2,000 Over $250,000,000 liquidated from the crypto market in the past 15 minutes.

26 May 2026, 09:15 UTC571 viewsread 7 August 2026
Photo

The bottom for #BTC has been in place since February 2026. Did you know that #BTC has bounced off a 12-year trendline? That's massive! What we’re seeing here is accumulation before the price rises. Altcoins will outperform🔥

Showing the 12 most recent of 19 posts we hold for @TheBullvsTheBear. 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 — 348,343 of 1,151,006entries 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.

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.

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

“The Bull Vs The Bear” (@TheBullvsTheBear), 2,934 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/TheBullvsTheBear.

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.