Telegram RegisterThe public register of Telegram
Telegram profile photo for 玖鼎集團 9 DYNASTY GROUP 每日汇率更新

Channel

玖鼎集團 9 DYNASTY GROUP 每日汇率更新

@JD_wallet

On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry

417subscribers

+1 since we began measuring on 2 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001861095656
TypeChannel
Username@JD_wallet
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live3 September 2026
Measurements held2
Confirmed unchanged1 time, most recently 3 September 2026
On Telegramt.me/JD_wallet

Growth

416417416.52 Sept 2026, 16:46 — 416 subscribers3 Sept 2026, 08:14 — 417 subscribers2 Sept 2026, 16:463 Sept 2026, 08:14
2 measurements taken within a single day, net +1. 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 416–417 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 08:14417+1
2 Sept 2026, 16:46416first reading

Engagement

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

ERR · 30 days
25.2%
avg views ÷ 417 subscribers
Avg views / post
105
18 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held20 (18 August 20262 September 2026)
Views total1,892
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 16:46 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

2 Sept 2026, 08:30 UTC33 viewsread 2 September 2026
Photo

公司發的 USDT,為什麼不建議直接轉進交易所出款? 很多人領薪時,會直接提供自己的 MAX、BitoPro、幣安等交易所 USDT 充值地址給公司。 但問題是,你知道 USDT 是公司發給你的,卻不一定知道公司的 USDT 是從哪裡來的。 01|上游資金出問題,可能一路追到你 假設公司的 USDT 上游曾涉及詐騙或其他案件,鏈上資金可能是: 涉案資金 → 中間錢包 → 公司錢包 → 你的交易所充值地址 一旦受害者報案,警方開始追查鏈上金流,就可能透過交易所的 KYC 實名資料找到帳戶持有人。 最後被找到的人,可能就是你。 02|即使只是領錢,也可能被要求說明 警方可能會詢問: 這筆 USDT 是誰轉的? 為什麼會收到? 你和轉帳方是什麼關係? 這筆錢的用途是什麼? 一旦上游資金涉案,你就可能需要解釋: 為什麼這筆涉案資金最後會進到你的帳戶? 03|交易所帳戶可能被限制或凍結 MAX、BitoPro、幣安等交易所都採用 KYC

2 Sept 2026, 04:10 UTC45 viewsread 2 September 2026

😵‍💫 2026.09.02匯率更新 😵‍💫 💰 USDT ➡️ 🇹🇼 台 币 ✖️ 31.75 💰 USDT ➡️ 🇨🇳 人民币 ✖️ 6.6 🇵🇭 披 索 ➡️ 🇹🇼 台 币 ✖️ 0.515 🇵🇭 披 索 ➡️ 🇨🇳 人民币 ➗ 9.25

1 Sept 2026, 06:28 UTC66 viewsread 2 September 2026

😵‍💫 2026.09.01匯率更新 😵‍💫 💰 USDT ➡️ 🇹🇼 台 币 ✖️ 31.65 💰 USDT ➡️ 🇨🇳 人民币 ✖️ 6.6 🇵🇭 披 索 ➡️ 🇹🇼 台 币 ✖️ 0.515 🇵🇭 披 索 ➡️ 🇨🇳 人民币 ➗ 9.25

31 Aug 2026, 03:40 UTC79 viewsread 2 September 2026

😵‍💫 2026.08.31匯率更新 😵‍💫 💰 USDT ➡️ 🇹🇼 台 币 ✖️ 31.75 💰 USDT ➡️ 🇨🇳 人民币 ✖️ 6.6 🇵🇭 披 索 ➡️ 🇹🇼 台 币 ✖️ 0.515 🇵🇭 披 索 ➡️ 🇨🇳 人民币 ➗ 9.25

30 Aug 2026, 03:05 UTC88 viewsread 2 September 2026

😵‍💫 2026.08.30匯率更新 😵‍💫 💰 USDT ➡️ 🇹🇼 台 币 ✖️ 31.7 💰 USDT ➡️ 🇨🇳 人民币 ✖️ 6.62 🇵🇭 披 索 ➡️ 🇹🇼 台 币 ✖️ 0.515 🇵🇭 披 索 ➡️ 🇨🇳 人民币 ➗ 9.25

29 Aug 2026, 03:20 UTC93 viewsread 2 September 2026

😵‍💫 2026.08.29匯率更新 😵‍💫 💰 USDT ➡️ 🇹🇼 台 币 ✖️ 31.7 💰 USDT ➡️ 🇨🇳 人民币 ✖️ 6.62 🇵🇭 披 索 ➡️ 🇹🇼 台 币 ✖️ 0.515 🇵🇭 披 索 ➡️ 🇨🇳 人民币 ➗ 9.25

28 Aug 2026, 04:57 UTC98 viewsread 2 September 2026

😵‍💫 2026.08.28匯率更新 😵‍💫 💰 USDT ➡️ 🇹🇼 台 币 ✖️ 31.7 💰 USDT ➡️ 🇨🇳 人民币 ✖️ 6.62 🇵🇭 披 索 ➡️ 🇹🇼 台 币 ✖️ 0.515 🇵🇭 披 索 ➡️ 🇨🇳 人民币 ➗ 9.25

27 Aug 2026, 05:08 UTC94 viewsread 2 September 2026

😵‍💫 2026.08.27匯率更新 😵‍💫 💰 USDT ➡️ 🇹🇼 台 币 ✖️ 31.8 💰 USDT ➡️ 🇨🇳 人民币 ✖️ 6.62 🇵🇭 披 索 ➡️ 🇹🇼 台 币 ✖️ 0.515 🇵🇭 披 索 ➡️ 🇨🇳 人民币 ➗ 9.25

26 Aug 2026, 04:39 UTC112 viewsread 2 September 2026

😵‍💫 2026.08.26匯率更新 😵‍💫 💰 USDT ➡️ 🇹🇼 台 币 ✖️ 31.9 💰 USDT ➡️ 🇨🇳 人民币 ✖️ 6.64 🇵🇭 披 索 ➡️ 🇹🇼 台 币 ✖️ 0.516 🇵🇭 披 索 ➡️ 🇨🇳 人民币 ➗ 9.25

25 Aug 2026, 14:51 UTC111 viewsread 2 September 2026

😵‍💫 2026.08.25匯率更新 😵‍💫 💰 USDT ➡️ 🇹🇼 台 币 ✖️ 31.9 💰 USDT ➡️ 🇨🇳 人民币 ✖️ 6.64 🇵🇭 披 索 ➡️ 🇹🇼 台 币 ✖️ 0.516 🇵🇭 披 索 ➡️ 🇨🇳 人民币 ➗ 9.25

24 Aug 2026, 07:02 UTC120 viewsread 2 September 2026

😵‍💫 2026.08.24匯率更新 😵‍💫 💰 USDT ➡️ 🇹🇼 台 币 ✖️ 31.9 💰 USDT ➡️ 🇨🇳 人民币 ✖️ 6.64 🇵🇭 披 索 ➡️ 🇹🇼 台 币 ✖️ 0.516 🇵🇭 披 索 ➡️ 🇨🇳 人民币 ➗ 9.25

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

佳运支付
@jyzf27 · 45,348
Telegram ranks this channel #27 of 32 here — alongside 31 others — read 2 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 3 September 2026 — this entry's latest reading, not the date you are reading this.

“玖鼎集團 9 DYNASTY GROUP 每日汇率更新” (@JD_wallet), 417 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/JD_wallet.

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.