Telegram RegisterThe public register of Telegram
Telegram profile photo for Fly-幣圈頭號玩家

Channel

Fly-幣圈頭號玩家

@Bitget00BTC

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,243subscribers

+51 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002404948215
TypeChannel
Username@Bitget00BTC
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/Bitget00BTC

Topic

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 66% 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.

Growth

2,1832,2482,215.57 August 2026 — 2,192 subscribers7 August 2026 — 2,192 subscribers8 August 2026 — 2,191 subscribers11 August 2026 — 2,183 subscribers15 August 2026 — 2,193 subscribers18 August 2026 — 2,188 subscribers21 August 2026 — 2,192 subscribers24 August 2026 — 2,196 subscribers27 August 2026 — 2,210 subscribers30 August 2026 — 2,220 subscribers2 September 2026 — 2,216 subscribers7 September 2026 — 2,219 subscribers11 September 2026 — 2,232 subscribers15 September 2026 — 2,237 subscribers4 October 2026 — 2,248 subscribers11 October 2026 — 2,243 subscribers2,2437 August 202611 October 2026
16 measurements spanning 65 days, net +51. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,173–2,258 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 02:162,243-5
4 Oct 2026, 19:372,248+11
15 Sept 2026, 03:372,237+5
11 Sept 2026, 13:202,232+13
7 Sept 2026, 03:552,219+3
2 Sept 2026, 07:532,216-4
30 Aug 2026, 09:352,220+10
27 Aug 2026, 19:232,210+14
24 Aug 2026, 20:012,196+4
21 Aug 2026, 02:232,192+4
18 Aug 2026, 10:142,188-5
15 Aug 2026, 00:452,193+10
11 Aug 2026, 08:322,183-8
8 Aug 2026, 00:542,191-1
7 Aug 2026, 14:332,192no change
7 Aug 2026, 13:432,192first reading

Engagement

20 posts held, back to 6 August 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.

Reaction mix

101 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 50.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍5150.5%
❤3736.6%
😍65.94%
🎉32.97%
🔥32.97%
👏10.99%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 17 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 101 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 August 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 09:03 UTC84 views2 reactionsread 7 August 2026
Photo

晚間非農和失業率,五⭐️消息面待公布‼️‼️ 兄弟們自行做好倉位管理,別被這一波帶走了

❤2

7 Aug 2026, 08:57 UTC83 views3 reactionsread 7 August 2026

➡️BEAT 看一下📈 右側走階梯式上行,可以嘗試

❤3

7 Aug 2026, 07:10 UTC89 views9 reactionsread 7 August 2026
Photo

週末放縱日 驚喜來臨 🤣 平時看盤太累?平時總是跟不上單? 這個周末就給大家一次放縱的機會~ 🤣周末免費入群👍限時開放 🤣 不畫大餅,一切以實盤收益説話 這個週末,入群門檻直接清零❌ 📍免費席位有限,人滿就關 入群:@zhuli_wahahaha

😍4❤3👍2

7 Aug 2026, 03:27 UTC110 views7 reactionsread 7 August 2026
Photo

➡️CYS 兄弟們,12分鐘暴跌😀😀😀 右側不是Fly的舒適區,是Fly的統治區 會員群位置比初級頻道多😀😀😀收益 後續獲利點位請私訊小助理獲取

❤4👍3

7 Aug 2026, 03:06 UTC102 views3 reactionsread 7 August 2026
Photo

➡️CYS 😀😀😀暴跌!! 多空雙殺來咯 位置比我好的兄弟已經240%左右 減倉40%

👍2❤1

7 Aug 2026, 02:43 UTC105 views7 reactionsread 7 August 2026

看看 KMNO 上韓所的幣,漲勢良好,😀倉位可衝📈

👍3❤2😍2

7 Aug 2026, 01:47 UTC121 views5 reactionsread 7 August 2026
Photo

➡️CYS 多單剩餘倉位出掉 現在下方支撐已經破位,我們找機會多空雙吃

❤3👍2

6 Aug 2026, 18:23 UTC128 views8 reactionsread 7 August 2026
Photo

➡️CYS 😀😀😀 拉飛了兄弟們 也是又帶兄弟們吃肉了 下一獲利:0.98

❤4👍4

Showing the 12 most recent of 20 posts we hold for @Bitget00BTC. 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

Named by 1 registered channel — 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.

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 11 October 2026 — this entry's latest reading, not the date you are reading this.

“Fly-幣圈頭號玩家” (@Bitget00BTC), 2,243 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/Bitget00BTC.

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.