Telegram RegisterThe public register of Telegram
Telegram profile photo for 山东抵抗军

Channel

山东抵抗军

@ingressshandong

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

334subscribers

+5 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001440689212
TypeChannel
Username@ingressshandong
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held6
Confirmed unchanged3 times, most recently 19 September 2026
On Telegramt.me/ingressshandong

Topic

Other / unclassifiable — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.

Growth

3293353326 August 2026 — 329 subscribers6 August 2026 — 329 subscribers14 August 2026 — 333 subscribers20 August 2026 — 334 subscribers28 August 2026 — 335 subscribers3 September 2026 — 334 subscribers3346 August 20263 September 2026
6 measurements spanning 28 days, net +5. 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 328–336 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Sept 2026, 10:28334-1
28 Aug 2026, 04:43335+1
20 Aug 2026, 14:28334+1
14 Aug 2026, 09:36333+4
6 Aug 2026, 21:47329no change
6 Aug 2026, 09:28329first reading

Engagement

19 posts held, back to 9 February 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.

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 4 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

6 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👏583.3%
116.7%

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 4 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 6 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 9 February 2026 to 4 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.

Recent posts

4 Aug 2026, 01:36 UTC61 viewsread 6 August 2026
Photo

✈️ Telegram 目前在美区 App Store 下架 09:19更新:现已在全球 175 地区App Store下架。 09:27更新:TestFlight现已无法下载。 App Store Monitor | Apple App Store 🌸 在花频道 · 茶馆水群 · 投稿通道

24 Jun 2026, 07:21 UTC272 views1 reactionsread 6 August 2026

https://fevgames.net/ifs/event/?e=29727 欢迎参加2026年7月济南百花公园IFS!

1

29 May 2026, 10:53 UTC252 views0 reactionsread 6 August 2026
Forwarded from @foshanmissiondayVideo

📱【视频建议在wifi环境下观看】 任务图标设计,是本次活动筹备中最核心的部分之一。毕竟,许多现场记忆都会随着时间逐渐淡去,而任务图标会留在玩家的档案页中,长期记录这短短一两天的旅程。 在确定图标的整体色彩风格和视觉效果后,下一步便是为这24个Mission Day 任务选取合适而具有代表性的图标。 不同于大部分Mission Day 任务图标采用的景点地标直拍方案,筹备组在全市各地拍摄图标素材和参考优秀摄影作品后,还会对图标进行进一步的艺术处理。我们会根据图标主体的大小不同,通过局部描边的方式突出部分细节,同时调整阴影和亮度,使主体能被突出的同时,又能让24个原本风格各异的实物在艺术处理后作为图标并排在一起时,呈现出视觉观感上相近的一致性。 主体鲜明、风格各异,视觉统一,这便是我们追求和想呈现的效果。 希望这一系列图标能成为各位 Agent 任务列表中亮眼的存在,也希望大家喜欢这份属于佛山 Mission Day 的

22 May 2026, 10:32 UTC185 viewsread 6 August 2026
Forwarded from @FJRES

🌐 【Ingress 官方公告】5月16日服务器严重延迟技术简报与全员补偿方案 在 5 月 16 日(周六)的 Orion 悉尼与布拉格 Anomaly 期间,全球特工都遭遇了严重的服务器延迟、行动无法结算以及 Scanner 不稳定的情况。官方今日发布了技术复盘简报、后续优化计划及全球补偿方案。 🚨 核心故障原因 本次异常是 Ingress 迁移至新数据库后首次面临极高密度的玩家行为。由于瞬间产生的海量数据库写入请求,触发了三大瓶颈的“完美风暴”: 1. 写入冲突锁死(Write Contention Gridlock): 当并发流量超过特定阈值时,新数据库的重试机制导致重试操作远多于首次尝试,数据更新速度戏剧性下降。 2. 数万条“幽灵记录”阻塞(Ghost Records): Portal 和 Resonator 的每次变动都会留下至少 1 小时的临时“墓碑行(tombstone row)”。数据库因被数万条幽

17 Apr 2026, 00:47 UTC204 viewsread 6 August 2026
Photo

Telegram 现已内置官方简体中文/ 繁体中文 Via: CrazyWong | Police0CN | 𝑨𝒂 𝒅𝒊𝒖 不争 🌸 在花频道|茶馆讨论|投稿通道

15 Apr 2026, 23:37 UTC149 viewsread 6 August 2026
Forwarded from @NianticOfficialPhoto

NIA researchers have detected an XM resonance shift correlating with the Orion constellation. The Orion Global Op has been authorized to stabilize the Portal Network. High-order collaboration is key: Unique Fields with three distinct Link Owners yield maximum telemetry. Read more: https://ingress.com/news/2026-orion-globalop #IngressOrion

24 Mar 2026, 01:12 UTC193 viewsread 6 August 2026
Forwarded from @IngressBeijing

Ingress 3.6.1 更新:你的牌子终于不用像老太太的裹脚布一样长了 Wechat | 24.03.2026

21 Mar 2026, 03:16 UTC203 viewsread 6 August 2026
Forwarded from @TianjinResistancePhoto

《ENLCN大翻译运动揭秘——0318星落如雨的后续跟进》 新鲜出炉~~ https://vtx.space/archives/BigTransUncoverReport

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

Forward network

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.

Mentions

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.

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.

“山东抵抗军” (@ingressshandong), 334 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/ingressshandong.

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.