Channel
@WhiteBITNotification
On this record: Topic · Growth · Engagement · Posts · Cite this entry
4,558subscribers
-132 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001527699059 |
|---|---|
| Type | Channel |
| Username | @WhiteBITNotification |
| Created | Between 1 August 2021 and 31 March 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 10 October 2026 |
| On Telegram | t.me/WhiteBITNotification |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Oct 2026, 17:39 | 4,558 | -20 |
| 4 Oct 2026, 22:37 | 4,578 | -22 |
| 25 Sept 2026, 22:21 | 4,600 | -10 |
| 17 Sept 2026, 06:39 | 4,610 | -8 |
| 12 Sept 2026, 23:20 | 4,618 | -8 |
| 9 Sept 2026, 00:16 | 4,626 | -13 |
| 3 Sept 2026, 18:18 | 4,639 | -2 |
| 31 Aug 2026, 15:12 | 4,641 | -4 |
| 29 Aug 2026, 00:19 | 4,645 | -5 |
| 26 Aug 2026, 10:15 | 4,650 | -12 |
| 23 Aug 2026, 00:58 | 4,662 | -12 |
| 19 Aug 2026, 21:53 | 4,674 | +7 |
| 16 Aug 2026, 22:07 | 4,667 | -3 |
| 13 Aug 2026, 15:37 | 4,670 | -5 |
| 10 Aug 2026, 10:36 | 4,675 | -15 |
| 7 Aug 2026, 04:30 | 4,690 | no change |
| 7 Aug 2026, 04:25 | 4,690 | first reading |
32 posts held, back to 30 July 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 pages 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 32 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Dear users! Deposits and withdrawals of Ravencoin (RVN) are temporarily closed due to a technical update. Sorry for the inconvenience caused. We will inform you as soon as the update is completed. Stay tuned for news!
Dear users! Deposits and withdrawals of the assets based on the Story network are temporarily closed due to a technical update. Sorry for the inconvenience caused. We will inform you as soon as the update is completed. Stay tuned for news!
Dear users! Deposits and withdrawals of Internet Computer (ICP) are temporarily closed due to a technical update. Sorry for the inconvenience caused. We will inform you as soon as the update is completed. Stay tuned for news!
Dear users! We are happy to inform you that the technical update of UAH Card Transfer has been completed. Deposits of UAH via Card Transfer are available again. Thank you for your patience.
Funding rate settlement change The funding rate settlement of the ACE-PERP perpetual futures at WhiteBIT changes from every 1 hour to every 4 hours starting on the 10th of August at 4:00 UTC.
Dear users! We are happy to inform you that the technical update of UAH IBAN Transfer has been completed. Deposits of UAH via IBAN Transfer are available again. Thank you for your patience.
Dear users! Deposits of UAH via Card Transfer are temporarily closed due to a technical update. Sorry for the inconvenience caused. We will inform you as soon as the update is completed. Stay tuned for news!
Dear users! Deposits of UAH via IBAN Transfer are temporarily closed due to a technical update. Sorry for the inconvenience caused. We will inform you as soon as the update is completed. Stay tuned for news!
Funding rate settlement change The funding rate settlement of the DEXE-PERP perpetual futures at WhiteBIT changes from every 1 hours to every 4 hour starting on the 7th of August at 20:00 UTC.
Dear users! We are happy to inform you that the technical update of EUR SEPA Instant Clear Junction has been completed. Withdrawals of EUR via Instant Clear Junction are available again. Thank you for your patience.
Funding rate settlement change The funding rate settlement of the ERA-PERP perpetual futures at WhiteBIT changes from every 1 hour to every 4 hours starting on the 7th of August at 16:00 UTC.
Funding rate settlement change The funding rate settlement of the ACE-PERP perpetual futures at WhiteBIT changes from every 4 hours to every 1 hour starting on the 7th of August at 08:00 UTC.
Showing the 12 most recent of 32 posts we hold for @WhiteBITNotification. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“WhiteBIT Notifications” (@WhiteBITNotification), 4,558 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/WhiteBITNotification.
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.