大家有没有抓到这一波? 👀
- 👍 有,成功抓到!44%
- ❤️ 没有,下次继续!56%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
❤1

Channel
@vivianchan_tradinginfo
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Cite this entry
758subscribers
+308 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004467454340 |
|---|---|
| Type | Channel |
| Username | @vivianchan_tradinginfo |
| Created | Between 1 June 2026 and 5 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/vivianchan_tradinginfo |
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 |
|---|---|---|
| 12 Oct 2026, 22:31 | 758 | +21 |
| 2 Oct 2026, 04:02 | 737 | +33 |
| 17 Sept 2026, 08:55 | 704 | +27 |
| 8 Sept 2026, 22:39 | 677 | +76 |
| 29 Aug 2026, 18:15 | 601 | +27 |
| 22 Aug 2026, 15:08 | 574 | +59 |
| 15 Aug 2026, 01:15 | 515 | +61 |
| 8 Aug 2026, 11:41 | 454 | +4 |
| 8 Aug 2026, 05:02 | 450 | no change |
| 8 Aug 2026, 01:34 | 450 | first reading |
19 posts held, back to 5 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 19 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 videos 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.
36 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 58.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 21 | 58.3% | |
| ❤ | 5 | 13.9% | |
| 🔥 | 4 | 11.1% | |
| 👏 | 2 | 5.56% | |
| 🤡 | 2 | 5.56% | |
| 👎 | 1 | 2.78% | |
| 🤷♂ | 1 | 2.78% |
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 12 of the 19 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 5 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.
大家有没有抓到这一波? 👀
Shares as published. No per-option vote count is published by Telegram, so none is shown.
❤1
🔥 Gold 起飞了! 虽然今晚我没有参与,不过还是想看看大家的战况。
🔥2
📊 今天市场给了两次机会。 第一段,按照当下的结构完成布局; 第二段,等待新的结构出现,再重新跟随市场。 今天我就先收工了。😄 今晚如果还有继续看盘的朋友,记得留意 NFP,保持耐心,也别忘了做好风险管理。 祝大家今晚一切顺利,也提前祝大家周末愉快! 🍀
❤2
Photo, posted without a caption
Video, posted without a caption
❤1
📈 Guys,Gold 刚刚突破 4300! 这是近期重新站上 4300 美元 关口,市场情绪也开始明显升温。👀 不过今晚还有 非农就业数据(NFP) 公布,市场波动可能会进一步放大。📊 大家记得做好风险管理,保持耐心,不要急着追行情。 祝大家今晚一切顺利!🍀 我们一起关注市场接下来的反应。👀
👍5❤1
🥲 跟大家分享一个小插曲。 完成不到 20 分钟,市场就走到我原本的 TP 位子 了。😂 当然还是会觉得有一点点可惜,不过有时候市场就是这样,不一定每一次都能把整段走势完整拿下。 每一个决定,都是根据当下的市场结构做出的,而不是事后回头看结果。 市场每天都会有新的机会,最重要的还是保持纪律,按照计划执行。💪 🫶🏻值得开心的是,今早 AI 的布局,整体走势依然按照规划进行。 📈
👍6
📊 Trade Update 感谢大家刚刚一起参与讨论,也谢谢大家的建议。🙏 综合目前的市场结构,我决定先锁定这笔利润,完成今天这笔交易。✅ 市场每天都会有新的机会,把已经到手的利润稳稳收下,也是交易管理中很重要的一环。 🤖 今日 AI 布局再次顺利得到市场验证。 📈 4256 → 4267,成功走出 100+ pips。
👏2
你们会怎么选择?👇
Shares as published. No per-option vote count is published by Telegram, so none is shown.
📊 Morning Update 今早的 AI 信号 目前走势相当顺利。✅ 从 4256 一路来到 4266,目前已经走出 100+ pips。📈 今天也继续陪大家一起验证 AI 的市场布局,目前走势符合预期。 不过 4266 附近开始出现一些阻力,而我原本的 TP 是 4276。 现在有点纠结 🤔 是继续按照原计划持有,还是先把利润锁定?
👍1
Video, posted without a caption
📊 第二轮走势再次兑现。✅ 4266 → 4252,成功走出 140+ pips。📉 第一轮布局已经完成,所以第二轮我没有再参与,不过还是继续陪大家一起验证 AI 信号。 不过最终这轮走势也顺利得到市场验证 💯
👍3🤷♂1
Showing the 12 most recent of 19 posts we hold for @vivianchan_tradinginfo. 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 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
大家有没有抓到这一波? 👀
Shares as published. No per-option vote count is published by Telegram, so none is shown.
你们会怎么选择?👇
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 19 most recent posts we hold, published 5 August 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“vivian AI trading info 📈” (@vivianchan_tradinginfo), 758 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/vivianchan_tradinginfo.
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.