Telegram RegisterThe public register of Telegram
Telegram profile photo for BB RSI

Channel

BB RSI

@mcxyzBBRSI

On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry

554subscribers

-12 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001826732982
TypeChannel
Username@mcxyzBBRSI
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/mcxyzBBRSI

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 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.

Growth

5545665607 August 2026 — 566 subscribers7 August 2026 — 566 subscribers15 August 2026 — 565 subscribers21 August 2026 — 563 subscribers28 August 2026 — 562 subscribers6 September 2026 — 555 subscribers15 September 2026 — 554 subscribers7 August 202615 September 2026
7 measurements spanning 39 days, net -12. 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 552–568 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 09:58554-1
6 Sept 2026, 18:18555-7
28 Aug 2026, 07:25562-1
21 Aug 2026, 19:06563-2
15 Aug 2026, 04:16565-1
7 Aug 2026, 01:01566no change
7 Aug 2026, 00:48566first reading

Engagement

20 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

7 Aug 2026, 00:47 UTC1 viewsread 7 August 2026
Photo

CFGUSDT (4h) RSI14 Oversold (20.62) & Heikin-Ashi price below Bollinger Bands 1D Change: -4.697% Current price: $0.1603 Market cap: $61M TradingView | Binance

7 Aug 2026, 00:20 UTC1 viewsread 7 August 2026
Photo

RPLUSDT (4h) RSI14 Oversold (39.17) & Heikin-Ashi price below Bollinger Bands 1D Change: -1.299% Current price: $1.52 Market cap: $34.5M TradingView | Binance ========================== RPLUSDT (8h) RSI14 Oversold (33.65) & Heikin-Ashi price below Bollinger Bands 1D Change: -1.299% Current price: $1.52 Market cap: $34.5M TradingView | Binance

7 Aug 2026, 00:14 UTC1 viewsread 7 August 2026
Photo

GRAMUSDT (4h) RSI14 Oversold (34.17) & Heikin-Ashi price below Bollinger Bands 1D Change: -1.793% Current price: $1.369 Market cap: $3.8B TradingView | Binance ========================== SKYUSDT (8h) RSI14 Oversold (34.66) & Heikin-Ashi price below Bollinger Bands 1D Change: -1.991% Current price: $0.05514 Market cap: $1.3B TradingView | Binance ========================== SKYUSDT (4h) RSI14 Oversold (34.1) &

7 Aug 2026, 00:08 UTC1 viewsread 7 August 2026
Photo

ONDOUSDT (8h) RSI14 Oversold (31.91) & Heikin-Ashi price below Bollinger Bands 1D Change: -4.092% Current price: $0.3586 Market cap: $1.7B TradingView | Binance

6 Aug 2026, 23:54 UTC1 viewsread 7 August 2026
Photo

XLMUSDT (8h) RSI14 Oversold (22.37) & Heikin-Ashi price below Bollinger Bands 1D Change: -2.184% Current price: $0.1612 Market cap: $5.5B TradingView | Binance

6 Aug 2026, 23:53 UTC1 viewsread 7 August 2026
Photo

JTOUSDT (4h) RSI14 Oversold (30.04) & Heikin-Ashi price below Bollinger Bands 1D Change: -7.078% Current price: $0.4818 Market cap: $243.8M TradingView | Binance

6 Aug 2026, 23:41 UTC1 viewsread 7 August 2026
Photo

SOLUSDT (4h) RSI14 Oversold (35.75) & Heikin-Ashi price below Bollinger Bands 1D Change: -2.228% Current price: $72.42 Market cap: $42.1B TradingView | Binance

6 Aug 2026, 23:40 UTC1 viewsread 7 August 2026
Photo

WLDUSDT (4h) RSI14 Oversold (29.55) & Heikin-Ashi price below Bollinger Bands 1D Change: -4.508% Current price: $0.3029 Market cap: $1.1B TradingView | Binance ========================== WLFIUSDT (4h) RSI14 Oversold (24.08) & Heikin-Ashi price below Bollinger Bands 1D Change: -1.495% Current price: $0.0527 Market cap: $1.7B TradingView | Binance

6 Aug 2026, 23:13 UTC1 viewsread 7 August 2026
Photo

XRPUSDT (4h) RSI14 Oversold (26.17) & Heikin-Ashi price below Bollinger Bands 1D Change: -2.402% Current price: $1.0359 Market cap: $64.7B TradingView | Binance

6 Aug 2026, 23:04 UTC1 viewsread 7 August 2026
Photo

INJUSDT (4h) RSI14 Oversold (24.74) & Heikin-Ashi price below Bollinger Bands 1D Change: -5.879% Current price: $4.563 Market cap: $456.1M TradingView | Binance

6 Aug 2026, 22:36 UTC2 viewsread 7 August 2026
Photo

STXUSDT (4h) RSI14 Oversold (22.18) & Heikin-Ashi price below Bollinger Bands 1D Change: -1.877% Current price: $0.1307 Market cap: $242.3M TradingView | Binance

6 Aug 2026, 22:16 UTC2 viewsread 7 August 2026
Photo

BNSOLUSDT (4h) RSI14 Oversold (38.97) & Heikin-Ashi price below Bollinger Bands 1D Change: -1.681% Current price: $81.9 Market cap: $741.2M TradingView | Binance

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

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

“BB RSI” (@mcxyzBBRSI), 554 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/mcxyzBBRSI.

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.