Channel
@BWEnews_TR
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
1,959subscribers
-15 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002171818863 |
|---|---|
| Type | Channel |
| Username | @BWEnews_TR |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/BWEnews_TR |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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, 16:15 | 1,959 | +3 |
| 14 Sept 2026, 06:41 | 1,956 | -1 |
| 10 Sept 2026, 15:16 | 1,957 | +3 |
| 2 Sept 2026, 04:04 | 1,954 | -3 |
| 29 Aug 2026, 22:17 | 1,957 | -2 |
| 26 Aug 2026, 19:36 | 1,959 | -5 |
| 24 Aug 2026, 00:53 | 1,964 | -3 |
| 20 Aug 2026, 00:54 | 1,967 | +1 |
| 17 Aug 2026, 10:15 | 1,966 | -5 |
| 13 Aug 2026, 13:28 | 1,971 | -2 |
| 10 Aug 2026, 13:43 | 1,973 | -1 |
| 7 Aug 2026, 15:02 | 1,974 | no change |
| 7 Aug 2026, 13:55 | 1,974 | first reading |
20 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 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.
UPBIT LISTING: [거래] 블록스트리트(BSB) 신규 거래지원 안내 (KRW, BTC, USDT 마켓) UPBIT LİSTESİ: [Alım Satım] Blockstreet (BSB) için yeni işlem desteği duyurusu (KRW, BTC, USDT piyasaları) BSB MarketCap: 39.5M (Otomatik eşleştirme yanlış olabilir) ———————————— 2026-08-07 10:55:19 source: https://upbit.com/service_center/notice?id=1766002002
Bithumb Listing: [마켓 추가] 블록스트리트(BSB) 원화 마켓 추가 Bithumb Listelemesi: [Piyasa Eklemesi] BlockStreet (BSB) KRW piyasasına ekleniyor BSB MarketCap: 39.5M (Otomatik eşleştirme yanlış olabilir) ———————————— 2026-08-07 10:38:57 source: https://feed.bithumb.com/notice/1654365
UPBIT LISTING: [거래] 카미노파이낸스(KMNO) KRW 마켓 디지털 자산 추가 UPBIT LİSTELEMESİ: [İşlem] Kamino Finance (KMNO) KRW piyasasına dijital varlık eklendi KMNO MarketCap: 148.1M (Otomatik eşleştirme yanlış olabilir) ———————————— 2026-08-07 10:09:47 source: https://upbit.com/service_center/notice?id=1908054133
AggrNews: *WINTERMUTE TO TRADE COMMODITIES, CRYPTO ETFS, TOKENIZED STOCKS UPON REGULATORY APPROVAL: BBG AggrNews: *WINTERMUTE, DÜZENLEYİCİ ONAYININ ARDINDAN EMTİA, KRİPTO ETF'LERİ VE TOKENLEŞTİRİLMİŞ HİSSE SENETLERİ İŞLEMİ YAPACAK: Bloomberg ———————————— 2026-08-07 04:00:06
AggrNews: ROBINHOOD US LISTS $CASHCAT AggrNews: ROBINHOOD US, $CASHCAT'I LİSTELİYOR ———————————— 2026-08-06 20:41:54
Binance EN: Binance Futures Will Launch Multiple USDⓈ-Margined TradFi Perpetual Contracts (2026-08-06) Binance TR: Binance Futures, Çoklu USDⓈ-Marginli TradFi Sürekli Sözleşmelerini Başlatacak (06.08.2026) ———————————— 2026-08-06 10:30:12 source: https://cache.bwe-ws.com/bn-1845
UPBIT LISTING: [거래] 캡(CAP) 신규 거래지원 안내 (KRW, BTC, USDT 마켓) UPBIT LİSTELEMESİ: [İşlem] CAP (CAP) Yeni İşlem Desteği Duyurusu (KRW, BTC, USDT Piyasaları) CAP MarketCap: 44.2M (Otomatik eşleştirme yanlış olabilir) ———————————— 2026-08-06 09:55:17 source: https://upbit.com/service_center/notice?id=1518829904
Bithumb Listing: [마켓 추가] 유니베이스(UB) 원화 마켓 추가 Bithumb Listelemesi: [Piyasa Eklemesi] Unibase (UB) KRW Piyasasına Eklendi UB MarketCap: 567M (Otomatik eşleştirme yanlış olabilir) ———————————— 2026-08-06 09:19:06 source: https://feed.bithumb.com/notice/1654358
UPBIT LISTING: [거래] 그래비티토큰(GRVT) 신규 거래지원 안내 (KRW, BTC, USDT 마켓) UPBIT LİSTELEMESİ: [İşlem] Gravity Token (GRVT) için yeni işlem desteği duyurusu (KRW, BTC, USDT piyasaları) GRVT MarketCap: 30.4M (Otomatik eşleştirme yanlış olabilir) ———————————— 2026-08-05 12:42:33 source: https://upbit.com/service_center/notice?id=551269062
Bithumb Listing: [마켓 추가] 스퀴드(QUID) 원화 마켓 추가 Bithumb Listelemesi: [Market Eklemesi] Squid (QUID) KRW marketine eklendi ———————————— 2026-08-04 18:18:05 source: https://feed.bithumb.com/notice/1654330
UPBIT LISTING: [거래] 스퀴드(QUID) 신규 거래지원 안내 (KRW, BTC, USDT 마켓) UPBIT LİSTELEMESİ: QUID (QUID) Yeni İşlem Desteği Duyurusu (KRW, BTC, USDT Piyasaları) ———————————— 2026-08-04 18:00:06 source: https://upbit.com/service_center/notice?id=319415357
Bithumb Listing: [마켓 추가] 메타다오(META2), 글로벌달러(USDG) 원화 마켓 추가 Bithumb Listeleme: [Pazar Eklendi] METADAO (META2), GlobalDollar (USDG) Kore Wonu piyasasına eklendi ———————————— 2026-08-04 13:04:48 source: https://feed.bithumb.com/notice/1654310
Showing the 12 most recent of 20 posts we hold for @BWEnews_TR. 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 2 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.
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.
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.
This channel appears in 15 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“BWEnews türkçe 🇹🇷” (@BWEnews_TR), 1,959 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/BWEnews_TR.
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.