Channel
@Btcbiaodifenxiang
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
610subscribers
-72 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001670985851 |
|---|---|
| Type | Channel |
| Username | @Btcbiaodifenxiang |
| Created | 27 July 2023 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/Btcbiaodifenxiang |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 13 Sept 2026, 17:55 | 610 | +2 |
| 6 Sept 2026, 20:22 | 608 | -7 |
| 28 Aug 2026, 21:58 | 615 | -57 |
| 21 Aug 2026, 13:54 | 672 | -4 |
| 14 Aug 2026, 19:44 | 676 | -6 |
| 8 Aug 2026, 02:31 | 682 | no change |
| 7 Aug 2026, 12:35 | 682 | first reading |
2 posts held, back to 27 July 2023 — 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 2 posts for this entry, the most recent from 27 July 2023. An engagement rate over an empty window would be a number about nothing.
本频道不定时分享币圈消息及标的，想一对一指导了解更多信息可私聊群主 交易所注册链接： 币安：https://accounts.binance.info/register?ref=205942410 欧易：https://cnouyi.reisen/join/7550538 抹茶：https://www.mexc.com/register?inviteCode=1Lzi3 Bitget: https://www.bgportable.com/zh-CN/referral/register?from=referral&clacCode=BGCN1QDR Gate: https://www.gate.ac/signup/XwIQXV1W?ref_type=103
Channel created
Showing the 2 most recent of 2 posts we hold for @Btcbiaodifenxiang. 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.
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 2 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“币圈比特币策略免费分享社区” (@Btcbiaodifenxiang), 610 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/Btcbiaodifenxiang.
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.