Channel
@tonup_cn
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,283subscribers
-2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001817050293 |
|---|---|
| Type | Channel |
| Username | @tonup_cn |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 15 August 2026 |
| On Telegram | t.me/tonup_cn |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 03:11 | 1,283 | -2 |
| 6 Aug 2026, 08:06 | 1,285 | no change |
| 6 Aug 2026, 01:46 | 1,285 | first reading |
20 posts held, back to 20 August 2024 — 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 pageof 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 28 October 2024. An engagement rate over an empty window would be a number about nothing.
注意!由我們合作夥伴 PiggyPiggy 支持的終極 1 億 $PGC 空投正在進行!🎉 #TonGoAirdrop 🐷 PiggyPiggy 是首款 100% 代幣空投的迷你遊戲,擁有令人驚嘆的遊戲設計和 1100 萬用戶。🚀 $PGC 將於 11 月 12 日在多個頂級交易所上市! 🌟 為了慶祝我們的合作夥伴關係和這個備受期待的 TGE,我們邀請您質押您的 $UP 代幣,有機會獲得 1000 $USDT, 並獲得額外的 $PGC 空投!🌟 如何符合 1 億 $PGC 空投的資格: 1️⃣ 加入 @PiggyPiggyofficialbot 並完成簽到。(您可以在 Piggy 的主頁上找到按鈕) 2️⃣ 在 https://tonup.io/stake 質押您的 $UP 代幣 3️⃣ 將於 11 月 7 日為所有 $UP 質押者進行快照! 4️⃣ 在您的 Piggy 帳戶中領取您的 $PGC! 不要錯過這個獲得驚人獎…
🔥 我們很高興宣布已經永久銷毀來自 DAO 分配的代幣，這導致 $UP 代幣的流通供應量減少了 30%。 🌐 這項重大行動是在我們社群一致通過提案後進行的，展現了我們對 #TonUP 生態系統未來的集體承諾。 🔗 代幣銷毀記錄： https://tonviewer.com/transaction/352cd8fcd383529db83a4776b46d56373372c3be43cd82ab2cc630f406acea13 💪 這項策略性舉措不僅強化了我們對 #TON 生態系統的堅定承諾，也突顯了我們對 $UP 長期潛力的信心。我們的目標是為所有代幣持有者提升價值，同時進一步強化我們的社群。 💎 我們衷心感謝您持續的支持和參與。 -------- TonUP Token: STON / DeDust / Bitget / Tonviewer / CoinTR / MEXC / Gate / BingX Chats …
💎 在此宣布，#TonUP 社群以壓倒性的支持率通過了減少 30% $UP 代幣供應量的提案，獲得了驚人的 99.24% 贊同率。 📷 最終快照： - 銷毀：584,852.04 $UP 投票 - 不銷毀：4,468.46 $UP 投票 這次 30% 的減少特別針對 TonUP DAO 分配的 30,000,000 $UP，相應的代幣將在明天進行銷毀。 ❤️ 這個決定標誌著一個重要的里程碑，因為這是首次交由我們社群決策的提案。我們相信這個舉措將為未來的提案和改進鋪平道路。 🫂 感謝您持續的支持和參與！您的積極參與非常寶貴，我們感謝您為塑造 #TonUP 的未來所做的貢獻。 -------- TonUP Token: STON / DeDust / Bitget / Tonviewer / CoinTR / MEXC / Gate / BingX Chats & Channels: English Group / M…
💎 我們很高興宣佈一項重要計劃，旨在加強我們對#TON生態系統和$UP持有者的承諾。 🔥 鑑於近期事件，我們提議將$UP代幣的總供應量減少30%，相當於從TonUP DAO中減少3000萬枚代幣。這項計劃不僅旨在提升$UP代幣的價值和稀缺性，還能讓您積極參與塑造我們的未來。 🌐 為確保您的意見得到聽取，我們將就這項提議的代幣銷毀進行為期3天的投票。投票期將從2024年9月19日12:00 UTC開始，到2024年9月22日12:00 UTC結束。在此期間，您可以質押您的$UP代幣來投票，並可隨時撤回。投票期結束時，我們將對投票進行快照以確定結果。 🔗 請在頁面底部投票表達您的意見：https://tonup.io/dao 這項提議不僅僅是數字，它體現了我們的韌性和對#TonUP長期成功的承諾。讓我們攜手建立一個有利於所有人的可持續且通縮的模式。 📖 如需查看完整提案詳情，請查看我們的社區帖子：https://commu…
🫂 鑑於最近發生的事件，包括杜洛夫被捕，#TON生態系統中的各個社群展現出了非凡的韌性。作為The Open Network上的領先發射台，TonUP自豪地表達我們堅定不移的信念。 💎 為了進一步強調我們對社群的承諾，我們團隊決定自願銷毀所有團隊持有和顧問分配的代幣，這佔總供應量的13%。這一行動不僅突顯了我們致力於提升$UP的價值和稀缺性，也展現了面對挑戰時的真正抵抗精神。 🔥 通過銷毀總計1300萬$UP，我們旨在強化我們對可持續和通縮模型的信念，這將使所有持有者受益。 ✉️ 查看銷毀記錄和TonUP團隊的信函：https://community.tonup.io/t/the-massive-up-token-burn-our-pledge-to-the-community-the-future-direction-of-tonup 👥 此外，我們將在明天更新TonUP DAO頁面，我們將就提議銷毀部分TonUP D…
🎉 我們很高興宣布 TonUP DAO 頁面正式上線！ 💎 DAO 治理的實施是 TonUP 路線圖中的一個重要里程碑，這個專門的資源旨在提高 $TONUP 代幣流通的透明度。 🪩 在 DAO 頁面上，您可以找到全面的資訊，以保持我們社群對治理過程的了解和參與：https://tonup.io/dao 此外，我們目前正在審查一項對 TonUP DAO 很重要的提案，而且有重大事項即將到來！ 🚀 請持續關注，我們將一起繼續成長並改進我們的平台，帶來更多令人興奮的更新。 -------- TonUP Token: STON / DeDust / Bitget / Tonviewer / CoinTR / MEXC / Gate / BingX Chats & Channels: English Group / Multilingual Discussion Group / Русский язык / 中文 / Tü…
✨ $BYIN IDO 退款和社群保護計劃最新消息 📅 $BYIN IDO 退款窗口已正式關閉，時間從世界標準時間 9 月 7 日 09:00 到 9 月 14 日 09:00。 💎 我們很高興宣布，所有收到的退款已分批處理完畢，總計退還 18896.6290909 $TON。 請注意，任何不符合退款規則的代幣將在稍後退還。 🔗 有關退款的詳細交易記錄，請參閱我們的社群公告 🫂 衷心感謝您的理解和持續支持。 -------- TonUP Token: STON / DeDust / Bitget / Tonviewer / CoinTR / MEXC / Gate / BingX Chats & Channels: English Group / Multilingual Discussion Group / Русский язык / 中文 / Türkçe / Español / Indonesia / T…
我們很遺憾地發現由於市場低迷，$BYIN的價格表現不如預期。因此，我們決定提前啟動CPP保護機制，並為參與$BYIN IDO的用戶提供退款。 誰可以參與退款？ 符合以下條件的帳戶可以獲得$BYIN IDO的全額退款： 1. 參與了$BYIN IDO但尚未領取代幣的帳戶 2. 已領取代幣但尚未轉出的帳戶 請注意，已經轉出和交易的代幣不符合此次退款資格。 如何進行退款？ 1. 將$BYIN轉到退款地址：UQCgo3EuKaOHFzVG3WwTV1UMtntecbLntICP1DaZmZQL7tIm 2. 我們將檢查錢包地址和代幣是否符合規定，如果符合規定，您將在不超過36小時內收到退還的$TON。 3. 如果代幣不符合退款規則，將在退款窗口結束後返還。 4. 退款窗口為2024年9月7日09:00（UTC）至2024年9月14日09:00（UTC）。 🔗 有關退款的更多信息和詳情，請參閱我們的社區帖子 感謝您的理解和支持！ …
🎉我們很高興祝賀 @Byin_Fun 在 Gate.io 成功上市！ 在 #TonUP 上的 $BYIN IDO 成功結束後，交易將於今天正式開始。 ⏰ 開始時間：9月6日 12:00 PM（UTC） 📈 交易對：$BYIN / $USDT 🔗 交易連結：https://www.gate.io/referral/invite/tonupref_1470_106 🦄這個重要里程碑突顯了我們對支持創新項目和促進 #TON 生態系統發展的承諾。 讓我們一起慶祝這個成就，並為之后的交易做好準備吧！ -------- TonUP Token: STON / DeDust / Bitget / Tonviewer / CoinTR / MEXC / Gate / BingX Chats & Channels: English Group / Multilingual Discussion Group / Русский яз…
TonUP 與 DePIN SIM 开展合作! 🌍 DePIN SIM 是第一個使用加密原生 (e)SIM 的無國界通信和支付去中心化網絡。這個創新平台提供無縫的全球漫遊和挖礦功能,兼作通信工具和加密貨幣錢包。 📱 用戶可以免費獲得 eSIM、數據,並參與旅行賺錢和空投等計劃。通過數據挖礦機會和交易未使用數據的市場,DePINSIM 提高了資源效率,同時在 55 多個國家提供免費通訊和數據漫遊。 在 #TonUP,我們致力於通過 TON 區塊鏈上的創新解決方案來賦能我們的社區,這個合作夥伴關係是擴展可能性的一步。 讓我們一起踏上這段無國界通信的旅程! -------- TonUP Token: STON / DeDust / Bitget / Tonviewer / CoinTR / MEXC / Gate / BingX Chats & Channels: English Group / Multilingual…
在杜洛夫8月24日被捕之後，「抗爭狗」已成為一個具有強大象徵意義的新符號。 「抗爭必勝！」 TMM俱樂部 正在透過免費的#FREEDUROV NFT系列發起一場社會運動，#TonUP很榮幸能與他們合作。 我們正在贈送5個免費鑄造白名單名額！ 🦄 參加方式： 🔁 追蹤、按讚並轉推 ✍️ 在評論中留下你的TON地址 ⏰ 得獎者將在24小時內公布。 加入我們，參與這場圍繞#TON上最重要NFT系列的歷史性運動！ -------- TonUP Token: STON / DeDust / Bitget / Tonviewer / CoinTR / MEXC / Gate / BingX Chats & Channels: English Group / Multilingual Discussion Group / Русский язык / 中文 / Türkçe / Español / Indonesia / Tiế…
🚀 我們很高興地宣布，$BYIN IDO 已成功結束，所有配額已售罄。 💎 總共有 1,312 名參與者籌集了 35,700 $TON。 🔗 所有輪次的代幣現已可在這裡領取：http://tonup.io/project/BYIN。 敬請期待，更多令人興奮的消息將隨著 CPP 計劃到來！ -------- TonUP Token: STON / DeDust / Bitget / Tonviewer / CoinTR / MEXC / Gate / BingX Chats & Channels: English Group / Multilingual Discussion Group / Русский язык / 中文 / Türkçe / Español / Indonesia / Tiếng Việt / 日本語 More: Blog / Twitter / Homepage / Community
Showing the 12 most recent of 20 posts we hold for @tonup_cn. 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.
Citation-graph rank — 81,238 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 7 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@tonup_cn named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“TonUP 中文” (@tonup_cn), 1,283 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/tonup_cn.
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.