Channel
@ingressTaiwan543
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,813subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001082644452 |
|---|---|
| Type | Channel |
| Username | @ingressTaiwan543 |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 2 times, most recently 15 September 2026 |
| On Telegram | t.me/ingressTaiwan543 |
Gaming — 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 93% 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 |
|---|---|---|
| 11 Sept 2026, 03:19 | 1,813 | -2 |
| 2 Sept 2026, 05:53 | 1,815 | -1 |
| 29 Aug 2026, 19:35 | 1,816 | +1 |
| 26 Aug 2026, 15:35 | 1,815 | +3 |
| 23 Aug 2026, 09:12 | 1,812 | -1 |
| 19 Aug 2026, 12:35 | 1,813 | -2 |
| 16 Aug 2026, 18:26 | 1,815 | -2 |
| 13 Aug 2026, 11:39 | 1,817 | +2 |
| 10 Aug 2026, 04:45 | 1,815 | +1 |
| 6 Aug 2026, 19:52 | 1,814 | no change |
| 6 Aug 2026, 18:48 | 1,814 | first reading |
20 posts held, back to 11 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 2 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 20 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
233 reactions across 20 posts, in 16 distinct kinds. The most used accounts for 18.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6075825569176489671 | 44 | 18.9% | |
| ❤ | 35 | 15.0% | |
| 💩 | 29 | 12.4% | |
| 👍 | 24 | 10.3% | |
| custom 6098178636274209813 | 18 | 7.73% | |
| 👎 | 16 | 6.87% | |
| 🤔 | 16 | 6.87% | |
| 👀 | 12 | 5.15% | |
| 🤯 | 11 | 4.72% | |
| 😭 | 8 | 3.43% | |
| 😱 | 8 | 3.43% | |
| 🔥 | 4 | 1.72% | |
| 🤣 | 4 | 1.72% | |
| 👌 | 2 | 0.858% | |
| custom 6280733674275080299 | 1 | 0.429% | |
| 🎉 | 1 | 0.429% |
Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 20 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 233 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 11 July 2026 to 31 July 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.
【2026年 第三季 企業協同】 目前付費戰役已上架 免費戰役尚未出現 😀 Corporate Synergy 活動時間：8/1 02:00 ~ 9/1 02:00 戰役價格： 😀NIA 2026：😀 0 CMU 😀IQTech 2026：😀 15,000 CMU 😀Hulong Transglobal 2026：😀 15,000 CMU 😀Visur Tech 2026：😀 15,000 CMU 😀 助推 IngressTaiwan543 😀 @IngressTaiwan543 #Ingress #CorporateSynergy #Apollo 😀
💩11🤔3custom 60981786362742098132🎉1🤣1🤯1custom 60758255691764896711
【GORUCK Asia 未來數月行程發布】 未來幾個月的計畫正式揭曉‼️ 而這還只是個開始 🚩月： 箭頭指將指向首爾 迎來 Ingress 現場挑戰 🚩月： 跨越至新加坡 首先是 Ingress 賽事 接著是在 Funan Mall 登場的重磅企劃 全球首間 GORUCK 實體零售店 這也是我們前所未有的全新嘗試 🚩🚩月： 作為主贊助商 我們將在 Urban Throwdown 26 全力以赴 四個站點，每一站都值得你親臨現場、親身參與，而不只是當個旁觀者‼️ 😀 活動相關連結 🇰🇷 首爾 Ingress GORUCK（8/21~8/23） 🇸🇬 新加坡 Ingress GORUCK（9/18~9/20） 😀 Urban Throwdown ’26（10/20~10/25） 最新日期資訊將優先公布於： goruck.asia 🇰🇷 2026/8/22 首爾 異常 ENL Rocks 🇸🇬 2026/9/19 新…
🔥4custom 60981786362742098133😱2🤯1
【機械軍 特別報導】 - Machina 已回歸。 😀 助推 IngressTaiwan543 😀 @IngressTaiwan543 #Ingress #Machina #MachinaWeakening 😀
custom 60981786362742098138👀4❤1🤯1
【2026年 8級週 即將來襲】 😀 活動時間 ：8/8 02:00 ~ 8/18 02:00 😀戰役價格： 😀 Machina Forever 2026：😀 0 CMU 😀 Enlightened Forever 2026：😀 2,500 CMU 😀 Resistance Forever 2026：😀 2,500 CMU 活動內容 ： - 『AP』提高至 2 倍。 - 『APEX』提高至 3 倍。 - 『LV8 共振器』可部屬 2 隻。 - 『模組』可部屬 4 個。 - 『遙控機』冷卻時間降為 8 分鐘。 - 『Glyph 入侵』每成功 1 個多 80 AP。 - 『實驗性武器調整』。 😀 8 級週 注意事項： - 如果計劃達到特定的AP，請注意活動期間無法獲得奇數AP。 - 若您目標是獲得偶數AP，請確保活動開始時您的AP已經是偶數。 - 使用『Apex』一共可獲得 6 倍AP。 😀 商店販售 …
❤2custom 60758255691764896712👍1
【新功能 - Agent Protips】 我們最近更新了『新探員訓練』，讓新進人員能夠直接從 Devra 或 Hank 那裡快速學習 Ingress 掃描器的基礎操作。 我們正陸續新增全新的『情境提示視窗』與『Agent Protips』，將他們的實用建議延伸至教學流程之外。 這些偶爾出現的一次性小提示，旨在協助所有探員充分發揮掃描器的功能。 探員也可以隨時在『設定」選單中選擇關閉它們。 😀 助推 IngressTaiwan543 😀 @IngressTaiwan543 #Ingress #NEWS 😀
custom 60758255691764896717❤1👍1
【2026年08月01日 Taiwan FS】 😀 全國共 三 場 Event 供探員選擇 - 11:00 Taichung City, Taiwan 😀 XFAC : T.me/+FYYGM1YgoqwwZDY9 😀 詳細資訊 - 12:30 Taipei City, Taiwan 😀 XFAC : T.me/ifsTaipei 😀 詳細資訊 - 18:30 Kaohsiung City, Taiwan 😀 XFAC : T.me/+VAMhgn9Ru4mNxSkc 😀 詳細資訊 😀 代幣獎勵 ： - 每月領 2,500 Apollo Tokens。 😀 陣營貢獻 ： - 每月簽到增加己方陣營 0.1 賽季分數。 😀注意個人經驗數據需要增加10,000AP。 😀注意個人經驗數據需要增加10,000AP。 😀 必須入侵集合塔/解密塔才算完成FS活動。 😀 助推 IngressTaiwan543 😀 …
❤1👀1👍1
【2026年 第三季 企業協同】 探員們： 為了秉持我們對跨領域創新與營運效率的共同承諾，『國家情報局 - NIA』很高興能轉達來自我們核心戰略夥伴 『IQTech Research』、『Hulong Transglobal』與『Visur Tech』的高優先級招募派遣通告。 請審閱下方由企業人才招募部門轉發的訊息： 您好！我是來自 {IQTech / Hulong Transglobal / Visur Tech} 招募部門的 Nancy。我從我們的線上求職門戶收到了您的資料，我覺得您非常適合 {阿波羅受試者（消耗品）} 這個職位。 我注意到您作為 Ingress 探員的強大背景，並且一直有在關注您最近在 {候選人最新成就} 中的表現。我目前正在協助應用研發部門的一個團隊，他們正致力於開發創新且令人興奮的新型檢測演算法。 我們 {IQTech / Hulong Transglobal / Visur Tech} 非常看重跳…
custom 60758255691764896714custom 60981786362742098132👀1👍1
【2026/07/22 開發者日誌：極限壓力下重構 XM 網路】 今年 3 月換了全新的資料庫，前兩個月運作相當順暢。 但在 5 月 16 日當天，全球探員活動量暴增，直接打爆新資料庫的瓶頸： 🚩自動擴展反應太慢。 🚩動作紀錄嚴重塞車。 🚩幽靈紀錄暴增 100 倍，直接把系統吸進黑洞癱瘓。 ‼️13 天爆肝重構 5 大核心 為了不讓接下來的異常大戰再度癱瘓，團隊犧牲假期，在 13 天內完成以下關鍵改造： 🚩預熱戰場 戰鬥開始前提早加開伺服器，並預先載入『即將被暴打』的熱門數據，避免臨時分析卡死。 🚩清除日誌塞車 刪除依時間戳記排序的寫入索引，拯救幾百人同時開炸時的即時寫入效能。 🚩掃除幽靈紀錄 取消能量塔排序條件中的『最後更新時間』，改用現場即時排序，避免 100 倍幽靈紀錄塞爆系統。 🚩縮小炸彈傷害範圍 縮小 XMP 炸彈攻擊半徑，但提高範圍內的傷害。讓單顆炸彈影響的 Portal 數量減少，大幅降低伺…
custom 607582556917648967111👎7🤯4🤔2🤣2😱1
【IngressPrime 3.12.2 發佈說明】 錯誤修正與其他改進： - 『Unity 引擎』更新：『安卓系統』導覽列正常顯示。 - 『賞金通行證』更新：當開放購買後，『每日戰役』頁面將出現可購買的選項。 - 『賞金通行證』修復：『Learn More』畫面修復。 😀『Ingress』遇到Bugs ？ ‼️請至『支援中心』回報 這裡 ‼️ 😀 助推 IngressTaiwan543 😀 @IngressTaiwan543 #Ingress #update 😀
❤3👍1🤔1
【機械軍 特別報導】 😀 NIA : 一位神秘的訊號分析師推測，Machina 的核心網路可能正在進行週期性的重新校準，進而導致了這些可觀察到的活動波動。 每一次的衰弱，都可能是為了迎接更強大且具適應力之復甦的序曲。 😀 助推 IngressTaiwan543 😀 @IngressTaiwan543 #Ingress #Machina #MachinaWeakening 😀
💩18🤔2😱2🤣1🤯1
【2026年 第三季大戰 Apollo】 😀 全球挑戰：Apollo 最終分數 ：😀 0 與 😀 0 😀 First Saturday ：Apollo 七月份：😀145.9 與 😀156.4 八月份：😀 0 與 😀 0 九月份：😀 0 與 😀 0 目前總分 ：😀145.9 與 😀156.4 😀 異常活動 ：Apollo 🇫🇮 芬蘭，赫爾辛基😀103.4 與 😀176.6 🇨🇴 哥倫比亞，波哥大😀157.6 與 😀122.4 🇰🇷 韓國，首爾😀 0 與 😀 0 🇫🇷 法國，巴黎😀 0 與 😀 0 🇸🇬 新加坡😀 0 與 😀 0 🇺🇸 美國，丹佛 😀 0 與 😀 0 😀 第三季 目前總分 ： 😀406.9 與 😀 455.4 😀 助推 IngressTaiwan543 😀 @IngressTaiwan543 #Ingress #Anomaly #Apollo 😀
😭8custom 60758255691764896717👍3❤1👎1
【2026年 第三季大戰 Apollo】 😀 異常地面戰 - 🇨🇴 哥倫比亞，波哥大 戰鬥信號燈 原始點數 ：😀226 與 😀202 最終分數 ：😀52.8 與 😀47.2 碎片爭奪戰 原始數量 ：😀166 與 😀123 最終分數 ：😀57.4 與 😀42.6 特別行動戰 隱形行動 ：😀0 與 😀 0 城市行動 ：😀0 與 😀 0 最終分數 ：😀0 與 😀 0 異常獨特性 平均數量：😀186.97 與 😀128.52 最終獎勵：😀47.4 與 😀32.6 哥倫比亞 總分：😀157.6 與 😀122.4 😀 免疫不穩定 😀 迴圈能量塔 😀 助推 IngressTaiwan543 😀 @IngressTaiwan543 #Ingress #Anomaly #Apollo 😀
❤9👍3🤔1custom 60758255691764896711
Showing the 12 most recent of 20 posts we hold for @ingressTaiwan543. 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.
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 2 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.
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.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“543 Ingress Taiwan (綠軍編編543) 推播 Channel” (@ingressTaiwan543), 1,813 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/ingressTaiwan543.
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.