Channel
@foshanmissionday
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
489subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003744058000 |
|---|---|
| Type | Channel |
| Username | @foshanmissionday |
| Created | Between 1 February 2026 and 5 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/foshanmissionday |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 03:37 | 489 | -3 |
| 7 Aug 2026, 10:01 | 492 | -1 |
| 6 Aug 2026, 21:48 | 493 | first reading |
20 posts held, back to 5 June 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 1 August 2026 |
|---|---|
| Posts held | 20 (5 June 2026 – 1 August 2026) |
| Views total | 964 |
| Reactions total | 17 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 21:48 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.
407 reactions across 16 posts, in 11 distinct kinds. The most used accounts for 35.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 144 | 35.4% | |
| 🎉 | 90 | 22.1% | |
| 🔥 | 58 | 14.3% | |
| 🥰 | 38 | 9.34% | |
| 👍 | 34 | 8.35% | |
| 👏 | 14 | 3.44% | |
| 🫡 | 13 | 3.19% | |
| 😭 | 10 | 2.46% | |
| ⚡ | 4 | 0.983% | |
| ❤🔥 | 1 | 0.246% | |
| 😨 | 1 | 0.246% |
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 17 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 407reactions 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 5 June 2026 to 1 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.
佛山 Mission Day 纪念T恤｜到货提醒 大家好，本轮佛山 Mission Day 纪念T恤包裹目前已全部送达。请大家留意物流信息、取件短信或电话，尚未领取的请尽快取件，避免因存放超时被退回。 收到后，请及时检查T恤的颜色、尺码、数量及整体情况。如有错发、漏发、明显质量问题或物流异常，请保留商品、包装及快递面单，并尽快联系我们，同时提供订购 Agent ID 和付款单号，方便我们核实处理。 感谢大家的耐心等待与支持，希望大家都能顺利收到这份属于佛山 Mission Day 的纪念。
❤8🫡1
佛山 Mission Day 纪念T恤｜发货通知 大家好，本轮佛山 Mission Day 纪念T恤已经完成制作，预计将于 7月27日至7月28日 陆续发出。不同订单的揽收及物流更新时间可能存在一定差异，请大家耐心等待。 收到快递后，请及时检查T恤的颜色、尺码、数量及整体情况。如存在错发、漏发或明显质量问题，请保留商品、包装及快递面单，并于快递签收之日起7天内联系我们，我们会尽快核实处理。 因个人尺码选择、颜色选择或主观穿着感受等非质量问题，原则上不支持退换。 如物流信息长时间未更新、包裹出现异常，或签收后发现问题，也请及时联系我们，并提供订购agent id 和 付款单号，方便我们快速查询。 感谢大家的耐心等待，也再次谢谢大家对佛山MD纪念T恤的支持。希望这件衣服能够继续陪大家保存这段共同的回忆。
❤7🥰1
佛山 Mission Day纪念T恤｜最后一轮追加订购 活动结束后，我们陆续收到大家关于纪念T恤补订的询问。应大家的需求，我们决定再开放最后一轮T恤订购，也让这份关于佛山MD的纪念，能够继续留在大家身边。 本轮保留原有黑色款，新增白色款及童装尺码。 售价：67元/件，中国大陆非偏远地区包邮 预定时间：7/13 ~ 7/20 12:00 （公告发出后一周） 截止后统一制作，后续不再追加或补单。 本轮如有结余，将由团队统筹用于后续周边打样、模具制作、无料礼品、社群创作，或为未来国内相关活动提供适当支持。 错发、漏发或明显质量问题可联系处理；因个人尺码、颜色选择等非质量问题，原则上不支持退换，详细说明请查看表单。 订购表单：【填写链接】 谢谢大家喜欢这件衣服，也谢谢大家让佛山MD的故事还能继续延伸一小段。
🔥14❤3👏1
一场 Mission Day 很奇妙的地方在于，它并不是把一座城市摆在玩家面前，然后告诉大家：“这里值得一看。” 更多时候，是玩家真的走进街巷、走过河岸、穿过公园和商场，在任务之间停下来拍照、聊天、交换 Biocard、寻找下一个 Portal。城市也就在这些脚步里，一点一点被重新看见。 佛山 Mission Day 结束之后，我们看到了很多玩家的照片、游记和反馈，也收到了不少鼓励。很多内容，我们都认真看了。对筹备组来说，最开心的并不只是活动顺利结束，而是看到大家真的在用自己的方式体验佛山。 当然，这个过程背后，也有很多取舍、遗憾和临场调整。 有些地点我们很喜欢，但最后没有选上；有些想法一开始很兴奋，后来发现根本做不动；有些细节活动当天看起来很自然，其实前面反复讨论了很多次。 所以，我们整理了这篇 Q&A，想把这些没来得及说完的幕后故事，慢慢讲出来。 👉 点击阅读：《佛山 Mission Day 筹备组回顾 Q&A》…
🥰37👍3❤2👏2
筹备组回顾现正撰写中✍️ 活动结束以来，筹备组收到了很多支持和鼓励，非常感谢大家对佛山Mission Day 活动的认可。 这几天我们在撰写回顾的同时，收到了许多朋友的疑问，希望筹备组能分享一些筹备活动的细节。 我们有很多东西想写出来，同时也很好奇大家对活动哪个部分的细节更感兴趣。于是我们打算面向所有关心佛山Mission Day 活动的玩家们征集大家感兴趣的话题和疑问，这些天我们已经收集到一些话题，例如： - 你们是怎么想到租酒店的 - 活动选点的怎么选出来，有什么侧重点？ - 活动结束后几天筹备组成员都在做什么？ - 如果将来佛山有XMA，附带的MD会选哪里地点？ - 那个高德地图太好用了，是怎么弄出来的？ 筹备组会将前面收集到的和这轮收集到的问题和话题一起讨论，一起选一些有意思的和有代表性的话题进行回答，然后会在筹备组回顾中一起和大家分享细节。所有问题/话题在文章中均以匿名提出，所以大家可以尽情在这条推送评论区（…
❤17👍2
“......呼叫所有特工——早上好！就在前不久的任务日，我们真切感受到了你们的积极和热情，干得漂亮！辛苦了，特工，多得你的一份参与和支持，真的，让整个任务日都充满了它该有的意义..” “.....我们的前线特工通过现场采集到了数据，这就分享给你，注意查收..” “...目前我们的行动结算已在进程当中，后续会再推送详细的任务日总结，相信很快就会有结果……那么，保持频道畅通，回见了！Over...”
🎉36
📡 BIOCARD 档案已更新 各位 Agent，佛山 Mission Day 的 BIOCARD 档案现已完成整理。 在活动期间，许多 Agent 携带自己的 BIOCARD 来到现场，并通过与佛山 Mission Day 专属 BIOCARD 进行交换，留下了属于自己的信号记录。 这张大合照中的每一张 BIOCARD，均来自一次次真实的 Agent-to-Agent 交换。 不同的阵营， 不同的城市， 不同的旅程， 最终汇聚在同一个 佛山 。 感谢所有参与 BIOCARD 交换的 Agent。 你的信号已被接收、记录，并留存在佛山 Mission Day 的记忆里。 直到下一次，我们的 Scanner 再次在路上相遇。 Collect the city. Complete the story. 原图下载
❤49
🎬 佛山 Mission Day 回顾视频来啦！ 这几天，我们从大家的镜头里，看见了许多个佛山。 于是，我们把这些关于佛山的碎片，拼凑成了一小段视频。 这不是一支完整记录所有人的视频，但它记录了这个周末里，佛山被 Agent 们点亮过的许多瞬间。 感谢所有来到佛山的你们。 也感谢每一个愿意分享画面的 Agent。 📍佛山 Mission Day 2026， 谢谢你们一起完成这段旅程。 我们下一站见！
❤47
📦 预购周边邮寄信息收集中！ 各位久等了！ 如果你因各种原因未能到现场提货，或在下单时选择了邮寄提货，请填写以下表单，方便我们确认邮寄信息。 我们预计会在信息收集完成后的一周内陆续发出快递，具体寄出时间可能会根据表单填写进度有所调整。 📦 预购周边邮寄信息确认表 温馨提示： 所有快递均为顺丰到付，暂不接受指定快递，暂时咨询了顺丰会有8.5折的运费优惠。如有疑问，欢迎随时联系筹备组，或直接在群内提出，我们会尽快解答。 我们也收到了一些关于是否开放第二次周边预定的询问。目前我们会优先完成现有订单的整理、邮寄与收尾工作，后续是否追加预定，将根据实际情况再做评估。如有新的安排，我们会第一时间在频道内通知大家，也请大家再给我们一些时间。 最后，也再次感谢大家对本次佛山 Mission Day 周边的支持。正是因为有了这些预购订单，我们才能把许多关于活动的设想真正带到现场、带到大家手中。 感谢每一位购买周边、支持活动的 Age…
🫡12❤2❤🔥1
😎 佛山 Mission Day 现已正式结束。 如果按照最多agent完成的任务【祖庙圣域】来算，已经有 603 名agent参加了本次佛山Mission Day。截止6月7日 23:59 分，已有 123 名agent登上了【67制霸纪念榜】。 📱如果喜欢这次Mission Day活动，欢迎向我们投稿，我们会将所有来稿发表在我们的官方博客。同时也欢迎在群里留下你们的反馈，你们的反馈对我们来说意义万分。 🕶 作为筹备组来说，我们没有办法看到活动的全貌，所以也私心拜托大家，在以下共享相册留下更多照片。让我们也能从你们的镜头里，看到佛山的更多角度。至少让我们看看，你们这个周末是否玩得开心；又或者，让我们数数你们一共吃了多少顿饭？ 📷纪念相册链接 目前还没有提货和邮寄的订单，请允许筹备组躺几天，我们会尽快处理。后续将会发放 Google Form 问卷收集邮寄地址和联系方式。 也许……有没有人希望开第二次纪念T-shir…
🎉54❤7
MD Base 将于 17:45 开始撤场，不便之处敬请谅解。
😭9🔥7😨1
佛山IFS&MD纪念相册已创建🏞 纪念相册链接 欢迎你在任务日的路上，留下更多的佛山仲夏回忆！
👍17👏2❤1
Showing the 12 most recent of 20 posts we hold for @foshanmissionday. 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 — 202,514 of 1,481,217entries 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 3 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Foshan Mission Day 2026” (@foshanmissionday), 489 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/foshanmissionday.
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.