#BTC 夜間掛單多📈 進場:62388-61588附近 止盈:65000-66500-🛫 防守:60500

Channel
寫輪眼致富基地(主動私訊都是騙子)
@Traderfenggecn
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
5,526subscribers
-36 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001581446233 |
|---|---|
| Type | Channel |
| Username | @Traderfenggecn |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/Traderfenggecn |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 04:17 | 5,526 | -1 |
| 14 Sept 2026, 13:57 | 5,527 | +2 |
| 11 Sept 2026, 07:37 | 5,525 | -11 |
| 6 Sept 2026, 18:59 | 5,536 | +1 |
| 2 Sept 2026, 06:43 | 5,535 | -8 |
| 29 Aug 2026, 21:57 | 5,543 | -2 |
| 24 Aug 2026, 03:55 | 5,545 | -4 |
| 20 Aug 2026, 01:11 | 5,549 | +1 |
| 16 Aug 2026, 18:38 | 5,548 | -1 |
| 13 Aug 2026, 13:05 | 5,549 | -11 |
| 10 Aug 2026, 05:00 | 5,560 | -1 |
| 7 Aug 2026, 12:35 | 5,561 | -1 |
| 7 Aug 2026, 09:30 | 5,562 | no change |
| 7 Aug 2026, 09:28 | 5,562 | first reading |
Engagement
23 posts held, back to 22 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 8 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 23 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
34 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 58.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 20 | 58.8% | |
| 🙏 | 8 | 23.5% | |
| 👌 | 3 | 8.82% | |
| 👍 | 3 | 8.82% |
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 13 of the 23 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 34 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 22 July 2026 to 11 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
8.11市場熱點: 1.btc最近與黃金出現分歧了,回到64k重新震蕩,先下來了就不該追方向,上周對應的落點也是63.5k附近 2.eth回踩更標準,又來到了1860的強支撐,上方關注1920-1930不變,趨勢方向暫不明確 3. Bitmine上周增持7391枚以太坊,總持倉量增至約580.5萬枚; 4.Michael Saylor:Strategy美元儲備增加6.5億美元並回購1.09億美元STRC; 5.貝萊德:隨著比特幣與股票的脫鈎趨勢逐漸顯現,市場情緒正在轉變;
❤2
比特幣在64k玩了三天、65k玩了兩天,不過在這個區間內並沒有見到新的吸籌行為,現貨需求不足。明天週一如果還維持這種資金情況就得往下砸一砸了。
非農出來了 ‑2.3萬人,預期8萬,前值2萬 就業出現負增長,大幅低於預期 單從數據來看無疑是利好,市場會重新定價美聯儲更快降息,美元、美債收益率下行。 目前空单浮虧,可以成本附近出來 等待更好的交易機會
空單進場浮盈
👍1
8.5市場熱點: 1.btc一潭死水,受益於美股的反彈,短線也略微走強,收復到64上方震蕩,強勢與否仍然以65k作為分界線; 2.eth開始收斂了,波動甚至還不如大餅,繼續關注1900這塊的阻力; 3.SpaceX首份財報超預期,但解禁壓力下盤後跌超7%; 4.以太坊新提案EIP-8361:質押率超50%後收益直接歸零; 5.彭博社:美伊可能在1至2天內達成一項關於重新開放霍爾木茲海峽的短期协议;
❤1
以太多单繼續掛單 ,老規矩,先到那邊做那邊
❤2👌2
重點關注週五的非農
短線上做個空單📉 進場:1893-1915附近 止盈:1840-1800-🛫 防守:1945
🙏3
以太多單有效,繼續掛單
🙏2👌1
7.30市場熱點: 1.btc沒有做出太大動作,凌晨講話先鷹後鴿,盤面缺少確定性方向,63k破位前還是看短線反彈為主, 2.eth結構同步,1850是關鍵分界線,匯率對受到0.03的壓制,突破則重新走強; 3.美聯儲宣佈聯邦基金利率維持在3.50%-3.75%不變,這是今年第五次按兵不動; 4.灰度:Hype仍被低估,遠期市盈率約為15至18倍; 5.富達 Q3 信號報告:BTC、ETH、SOL 的淨未實現盈虧均處歷史低位,多項指標接近投降區間;
❤2
以太過夜埋伏一筆多單📈 進場:1815-1775附近 止盈:1890-1930-🛫 防守:1730
Showing the 12 most recent of 23 posts we hold for @Traderfenggecn. 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.
Appears in Telegram’s recommendations for other channels
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.
@btcyouliang · 28,837
Telegram ranks this channel #11 of 92 here — alongside 91 others — read 9 September 2026
@feiyangkanbi · 23,581
Telegram ranks this channel #12 of 92 here — alongside 91 others — read 18 September 2026
@jin10light · 25,121
Telegram ranks this channel #13 of 78 here — alongside 77 others — read 3 September 2026
@bitebishuqin · 40,412
Telegram ranks this channel #13 of 90 here — alongside 89 others — read 30 August 2026
@sanmage · 30,951
Telegram ranks this channel #17 of 92 here — alongside 91 others — read 6 September 2026
@btc18688 · 25,268
Telegram ranks this channel #25 of 91 here — alongside 90 others — read 15 September 2026
@jinseBTC · 23,761
Telegram ranks this channel #35 of 72 here — alongside 71 others — read 17 September 2026
@ChannelPANews · 24,042
Telegram ranks this channel #45 of 96 here — alongside 95 others — read 17 September 2026
@blocktemponews · 39,179
Telegram ranks this channel #50 of 87 here — alongside 86 others — read 30 August 2026
@Computer_Science_IT_Notes_PDF · 42,227
Telegram ranks this channel #50 of 53 here — alongside 52 others — read 30 August 2026
@jinse2017 · 22,784
Telegram ranks this channel #53 of 60 here — alongside 59 others — read 20 September 2026
This channel appears in 11 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“寫輪眼致富基地(主動私訊都是騙子)” (@Traderfenggecn), 5,526 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Traderfenggecn.
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.