HANA🟢 +10.12% 0.03934 --> 0.04333 22m 13s Mark: 0.04348 24h Vol: 15 271 617 USDT 404 147
Channel
ByBit P/D 10% 30m
@bybit_10p_30m
On this record: Growth · Engagement · Posts · Citations · Cite this entry
226subscribers
-2 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 | -1002676674375 |
|---|---|
| Type | Channel |
| Username | @bybit_10p_30m |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/bybit_10p_30m |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 16:53 | 226 | -2 |
| 8 Aug 2026, 10:18 | 228 | no change |
| 7 Aug 2026, 17:07 | 228 | first reading |
Engagement
20 posts held, back to 16 March 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 1 pageof 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 16 March 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
BEAT🟢 +10.09% 0.4889 --> 0.53823 27m 5s Mark: 0.53981 24h Vol: 16 963 736 USDT 404 147
BLUAI🔴 -10.16% 0.00665 --> 0.00598 21m 55s Mark: 0.006 24h Vol: 671 213 USDT 404 147
BB🔴 -10.23% 0.03237 --> 0.02906 19m 3s Mark: 0.02909 24h Vol: 1 835 125 USDT 404 147
ESPORTS🔴 -10.15% 0.34047 --> 0.30591 7m 38s Mark: 0.30467 24h Vol: 657 352 USDT 404 147
ME🟢 +10.0% 0.12275 --> 0.13503 15m 48s Mark: 0.13717 24h Vol: 5 836 861 USDT 404 147
BB🟢 +10.21% 0.02919 --> 0.03217 7m 9s Mark: 0.03209 24h Vol: 590 224 USDT 404 147
BLAST🟢 +10.01% 0.0006 --> 0.00066 21m 2s Mark: 0.00066 24h Vol: 6 832 227 USDT 404 147
DOOD🟢 +10.06% 0.00332 --> 0.00365 29m 30s Mark: 0.00365 24h Vol: 2 939 125 USDT 404 147
BLAST🟢 +10.02% 0.00056 --> 0.00062 21m 14s Mark: 0.00062 24h Vol: 4 062 523 USDT 404 147
ARIA🟢 +10.04% 0.15312 --> 0.16849 23m 40s Mark: 0.16702 24h Vol: 6 386 160 USDT 404 147
ARIA🟢 +10.01% 0.13562 --> 0.14919 7m 16s Mark: 0.14921 24h Vol: 5 180 282 USDT 404 147
Showing the 12 most recent of 20 posts we hold for @bybit_10p_30m. 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
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“ByBit P/D 10% 30m” (@bybit_10p_30m), 226 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/bybit_10p_30m.
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.