Telegram RegisterThe public register of Telegram

Channel

Bybit Crypto Feed

@bybitcryptofeed

Verified by Telegram

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

32,949subscribers

-203 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001725176319
TypeChannel
Username@bybitcryptofeed
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 live12 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/bybitcryptofeed

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 10 August 2026 and assigned it the closest of 31 fixed categories, at 45% 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 8 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 (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@bybitcryptofeed/4213 · this entry4 Aug 2026, 08:00 UTC@bybit_announcements/93934 Aug 2026, 10:45 UTC1.002.7 hours
@bybitcryptofeed/4215 · this entry4 Aug 2026, 13:00 UTC@bybit_announcements/93974 Aug 2026, 13:00 UTC1.00under a minute
@bybit_announcements/94115 Aug 2026, 13:00 UTC@bybitcryptofeed/4218 · this entry5 Aug 2026, 13:00 UTC1.00under a minute
@bybit_announcements/94256 Aug 2026, 12:30 UTC@bybitcryptofeed/4221 · this entry6 Aug 2026, 12:30 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@bybit_announcements5 (5/5 hand-verifiable sample passed)1.00under a minute@bybit_announcements (32)

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 3 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 19 comparable posts for this entry, running 27 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 8, the earliest publisher we hold is @BybitTradFi. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, 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 7 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

32,94933,15233,050.57 August 2026 — 33,152 subscribers7 August 2026 — 33,152 subscribers8 August 2026 — 33,121 subscribers9 August 2026 — 33,073 subscribers10 August 2026 — 33,055 subscribers11 August 2026 — 33,005 subscribers12 August 2026 — 32,949 subscribers7 August 202612 August 2026
7 measurements spanning 5 days, net -203. 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 32,919–33,182 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 11:1432,949-56
11 Aug 2026, 09:5533,005-50
10 Aug 2026, 07:0333,055-18
9 Aug 2026, 06:4133,073-48
8 Aug 2026, 05:4233,121-31
7 Aug 2026, 07:3033,152no change
7 Aug 2026, 07:2933,152first reading

Engagement

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

ERR · 30 days
2.11%
avg views ÷ 32,949 subscribers
Avg views / post
694
32 posts measured
Reaction rate
0.862%
reactions ÷ views · ER floor
Posts in window
33
of 33 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. It is computed over the 30 of 32 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held33 (27 July 202612 August 2026)
Views total22,207
Reactions total187
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 21:10 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
3,790
Videos
47
Links
1,500

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.

Video runtime
35s
Average length
35s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

187 reactions across 30 posts, in 9 distinct kinds. The most used accounts for 70.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
13270.6%
🔥2111.2%
126.42%
👍94.81%
😁42.14%
31.60%
🎉31.60%
🤔21.07%
👎10.535%

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

Measured over the 33 most recent posts we hold, published 27 July 2026 to 12 August 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

12 Aug 2026, 17:01 UTC107 views2 reactionsread 12 August 2026
Photo

🤖 Best Trade GPT #BTG Dive into the Future of Trading with TradeGPT! Boost your trading skills with our AI bot. Access TradeGPT on our web page, on the Bybit app, or in the TradeGPT topic as explained here. Rules: ✅ Ask TradeGPT the most creative and fun crypto and trading ideas you can think of. ✅ Use /gpt and #BTG when posing your questions in the TRADEGPT chat ✅ If using the webpage or the Bybit app, share scre

2

12 Aug 2026, 11:25 UTC213 views4 reactionsread 12 August 2026
Photo

Looking for a short-term trade around today's CPI release? Need a guide in setting your Take Profit levels? @Bybit_Learn shares forecasted post-CPI moves for 14 major assets, including $BTC and gold.

🔥4

12 Aug 2026, 10:17 UTC222 views4 reactionsread 12 August 2026
Photo

🎮 Discord Community Game Night Get ready to dive into our exciting crossword puzzle challenge! We’ll drop the clues, and you’ll need to check the article to find the answers and crack the puzzle. The clock is ticking, so let’s get started! Today's topic is Bybit TradFi Copy Trading How to Play: ✅ Read the article and use the clues provided to unlock the answers. ✅ We will be dropping each tip one by one in ⁠⁠⁠ht

4

12 Aug 2026, 07:43 UTC186 viewsread 12 August 2026
Photo

US inflation data lands today (August 12). @Bybit_Learn shares forecasted price reactions for $BTC, gold, and more:

11 Aug 2026, 16:08 UTC255 views9 reactionsread 12 August 2026
Photo

📉 Share Your PnL Share your Bybit PnL snapshot and tell us why you should win the $USDT prize! To win trading bonus follow the rules below! 🤑 How To Participate: ✅ Whether it is a profit or loss snapshot, share with the hashtag #MyPnL in ⁠⁠Technical Analysis Topic ✅ Include a reason why you think your #MyPnL is the most interesting one ✅ Ensure the snapshot is relevant to today's market ✅ Only one entry per partic

5🤔2👎1😁1

11 Aug 2026, 16:02 UTC239 views4 reactionsread 12 August 2026
Photo

📊 Community Technical Analysis #CTA (Weekly) Showcase your technical analysis skills! Analyze the chart and submit your insights. Rules: ✅ Perform technical analysis on the BTCUSDT 4H chart with detailed and proper explanation of directions of price movement. ✅ Properly predict the highs & lows of the week compared to reverence price viz. current market price at the time of posting the announcement. ✅ Submit it us

4

11 Aug 2026, 04:36 UTC245 views4 reactionsread 12 August 2026
Photo

📊 Bybit Options Weekly Review: Aug 3–10 NFP shocked at −23K (vs +80K expected) — biggest miss in months. Prior months revised down 103K combined. Markets went full "bad news = good news": 🔸 $XAUT +5.9%, $BTC & $ETH rally 🔸 BTC ETF inflows: $853M | ETH ETF: $245M (3rd largest weeks YTD) 🔸 September rate hike odds dropped from ~55% → 44% This week's focus: Aug 12 CPI — the real test. Three options strategies laid ou

21🔥1

10 Aug 2026, 12:45 UTC326 viewsread 12 August 2026
Photo

US earnings: Investors are still ready to reward/punish AI spending plans. Which one of these three stocks may post a new record high this week?

10 Aug 2026, 09:00 UTC296 views3 reactionsread 12 August 2026
Video

Four features. One screen. Here's how it works. #Bybit #NewFinancialPlatform #ByX

3

8 Aug 2026, 21:58 UTC403 views4 reactionsread 12 August 2026
Photo

🪙 Bybit Coin Analysis Which coin listed on Bybit are you watching the most? Join our Discord community and share your market insights! Tell us which coin you've picked and why - whether it's based on technical analysis, market news, or on-chain data - for a chance to win exciting rewards. How to join ✅ Choose any listed coin on Bybit ✅ Give us a good reason why you think it is the coin to watch out for ✅ Post i

3🔥1

8 Aug 2026, 13:29 UTC420 views8 reactionsread 12 August 2026
Photo

Bybit: Let’s Talk About It 🔊 Today’s market needs your voice. Join the conversation, share your views, and win amazing rewards. How to join: ✅ Share your personal opinion on the topics below (no one-liners) ✅ Reply to at least ONE other user by quoting their message ✅ Use #BybitChat ❌ No AI-generated text ❌ No off-topic replies This week’s topics: 1️⃣ Before opening a Bybit Options trade, how much does time to

4🎉1👍1🔥1😁1

8 Aug 2026, 08:55 UTC452 views8 reactionsread 12 August 2026
Photo

💬 Monthly Feedback Session #MFS This month, we're focusing on Bybit Galaxy and the Galaxy Community Challenge. If you've been using Galaxy (and) participating in the Community Challenge, we want to hear from you. Share one feedback about something you liked, disliked, found confusing, or believe could be improved. Your feedback could be about: 🔹 User Experience 🔹 The Points 🔹 The Community Challenge 🔹 Rewards 🔹

8

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

Posts edited after publishing

@bybitcryptofeed edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 August 2026
Most recent edit
9 August 2026

Citation-graph rank

Citation-graph rank — 190,917 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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Bybit Alpha
@Official_Bybit_Alpha · 231,231
Telegram ranks this channel #3 of 80 here — alongside 79 others — read 11 August 2026
Bybit Announcements
@bybit_announcements · 428,155
Telegram ranks this channel #9 of 85 here — alongside 84 others — read 10 August 2026
Gate News
@GateOfficialNews · 489,807
Telegram ranks this channel #35 of 86 here — alongside 85 others — read 10 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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.

“Bybit Crypto Feed” (@bybitcryptofeed), 32,949 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/bybitcryptofeed.

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.