Channel
@CMEGaps
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2,904subscribers
-81 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002391399744 |
|---|---|
| Type | Channel |
| Username | @CMEGaps |
| Created | Between 1 September 2024 and 19 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/CMEGaps |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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 |
|---|---|---|
| 18 Sept 2026, 06:00 | 2,904 | -8 |
| 14 Sept 2026, 03:57 | 2,912 | -10 |
| 10 Sept 2026, 05:55 | 2,922 | -10 |
| 5 Sept 2026, 01:57 | 2,932 | -5 |
| 1 Sept 2026, 08:37 | 2,937 | -8 |
| 29 Aug 2026, 17:35 | 2,945 | -2 |
| 26 Aug 2026, 09:03 | 2,947 | -7 |
| 23 Aug 2026, 13:45 | 2,954 | -8 |
| 19 Aug 2026, 23:36 | 2,962 | -7 |
| 16 Aug 2026, 16:28 | 2,969 | -9 |
| 13 Aug 2026, 09:03 | 2,978 | -3 |
| 10 Aug 2026, 04:20 | 2,981 | -4 |
| 7 Aug 2026, 02:24 | 2,985 | no change |
| 6 Aug 2026, 23:01 | 2,985 | first reading |
20 posts held, back to 19 March 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 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 20 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
🚨Important information!!! Many people missed last ALTSEASON or even are in a Loss. That is why this guy has prepared a channel so you don't miss the next altseason! Join fast 🔥 ⬇️ https://t.me/+aigndCE8iM5mMzJk
🚨 ATTENTION!! 🚨 +1000% pump coin will be posted in BINANCE WHALE'S LEAK🚀🚀 Link open only for LIMITED TIME🕓 (30min left) JOIN FAST 👀👇 https://t.me/+riOYHjm4XpsyMzM0
NO.1 TELEGRAM CRYPTO CHANNEL JOIN NOW 👉 https://t.me/+eugMNTmszr1iNjQ0
✅ The gap at 110,500 has been filled - just as we warned 📉
The gap was formed at 110,500 ↘️
Done, everything went as planned – the gap is filled - 116800 ✅ #BTC
New CME gap will be formed at ~116800$. The gap will be filled sooner or later with a 90% probability 🔜 #BTC
Here you go 🕺 The #BTC gap at 117200 has been filled ✓
New CME gap will be formed at ~117200$. We hope that it will not be filled in the coming days 🙃 FYI: ±90% of CME gaps are filled sooner or later (it may be in a week, or maybe in a month). Keep this in mind. #BTC
Gap at 104300 — done ✅ #BTC
New CME gap was formed at ~104300$. The gap will be filled sooner or later with a 90% probability 🔜 #BTC
Here you go 🕺 The #BTC gap at 97,000 has been filled ✓
Showing the 12 most recent of 20 posts we hold for @CMEGaps. 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.
Named by 6 registered channels — 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“CME Gaps” (@CMEGaps), 2,904 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/CMEGaps.
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.