Telegram RegisterThe public register of Telegram
Telegram profile photo for Niantic Spatial Recon/OPR UK

Channel

Niantic Spatial Recon/OPR UK

@niaspatialuk

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

229subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002533396630
TypeChannel
Username@niaspatialuk
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held2
Confirmed unchanged2 times, most recently 14 August 2026
On Telegramt.me/niaspatialuk

Growth

2297 Aug 2026, 08:17 — 229 subscribers8 Aug 2026, 01:36 — 229 subscribers7 Aug 2026, 08:178 Aug 2026, 01:36
2 measurements taken within a single day. 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 228–230 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 01:36229no change
7 Aug 2026, 08:17229first reading

Engagement

20 posts held, back to 6 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 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 17 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

89 reactions across 12 posts, in 12 distinct kinds. The most used accounts for 28.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😢2528.1%
🔥1415.7%
😱1415.7%
1112.4%
😭1011.2%
🤡33.37%
🤣33.37%
🤬33.37%
🥰33.37%
👍11.12%
👎11.12%
💩11.12%

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 12 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 89reactions 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 6 February 2026 to 17 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.

Recent posts

13 Jul 2026, 09:27 UTC483 viewsread 7 August 2026

💻 OPR UPDATE - THERE IS NO UPDATE 💻 Agent PkmnTrainerJ asked Brian Rose a few questions this past week, and got a response. One was about OPR. We haven't had time to make changes to OPR, but it's still on our to do list. It seems right now the priority is to update the backend to handle the game better following issues that happened in the Sydney and Prague Anomalies, and then move on the to-do list when this is i

6 Jul 2026, 12:42 UTC≈1,140 views7 reactionsread 7 August 2026
Photo

📸 PHOTO QUEUE DONE, ON TO NOMINATIONS ✍️ Niantic Spatial seem to have finished the OPR/Recon queue of new photos added since it was reopened. According to Agents, the team have now moved on reviewing new Portal Nominations. This means new Portals added to Ingress for the first time in many many months. Thanks to @iFrankmans for the report!

7

1 Jul 2026, 17:39 UTC726 views9 reactionsread 7 August 2026

🇳🇿 NIANTIC SPATIAL NZ CLOSES 🇳🇿 It’s been confirmed through (now former) Niantic Spatial employees on LinkedIn that the New Zealand Niantic Spatial offices are closing, along with the New Zealand branch of the company overall. This is likely the company NZXR which Niantic (now Scopely) acquired in 2022 (https://nianticlabs.com/news/welcome-nzxr) which then seemed to have moved to Niantic Spatial for the split. One

😱7🤣2

28 Jun 2026, 19:18 UTC335 views2 reactionsread 7 August 2026

🪒NEW VPS EXPERIENCE🪒 It’s not Ingress, or Recon. But a new “experience” has launched using Niantic Spatial’s VPS (which was powered by scans from Ingress & Pokémon GO players), exclusively for Boston and Manhattan to celebrate America’s 250th anniversary. This is in partnership with Ubisoft (for the Assassin’s Creed branding) and a company called Sugar Creative who are based in Wales. The apps will be around for t

🔥2

28 Jun 2026, 07:55 UTC402 views3 reactionsread 7 August 2026

🚨 FIRST SATURDAY 🚨 Mod abuse alert! This Saturday, PkmnTrainerJ is the ENL co-host at an Ingress First Saturday at Market Harborough this Saturday. By reading this, you agree to at least check the sign up page - https://fevgames.net/ifs/event/?e=29633

3

12 Jun 2026, 07:05 UTC441 views24 reactionsread 7 August 2026
Photo

3️⃣MONTHS SINCE PAUSE⏸️ It’s now been 3 months since Niantic Spatial paused OPR/Recon. Agents continue to get photos approved by “our team” but the Ingress map now remains static with no new Portals added, and in some cases will no longer reflect the real world which Ingress often prides itself on. There has been no communication as to what’s happening with Recon and when/if it will return.

😢23👎1

28 Apr 2026, 18:20 UTC466 views2 reactionsread 7 August 2026

📆 NIANTIC SPATIAL 2026 EVENTS You may remember our post last year about events and conventions that Niantic Spatial attend to show off their tech including VPS, Project Jade, Scaniverse (and maybe Ingress?) They have now updated their events page and you can see details below. Some are awaiting more information as we share this, and some have details of what Spatial will be speaking about. May GEOINT Symposium: Ma

😢2

7 Apr 2026, 17:37 UTC630 viewsread 7 August 2026

🚀 NIANTIC SPATIAL UPGRADES VPS Today, Niantic Spatial shared that they are providing an updated Scaniverse product, alongside VPS 2.0 (which was used for Overclock in it’s previous iteration) and an upcoming Development Kit for Scaniverse so all those former Lightship developers we had in our discussion group can deploy some fancy spatial applications! Read more: https://www.nianticspatial.com/blog/scaniverse

24 Mar 2026, 08:12 UTC631 views7 reactionsread 7 August 2026

👩‍💼 NEW NIANTIC SPATIAL CEO It was announced that John Hanke will be stepping down as Niantic Spatial CEO as of March 30th. He will move in to a new role as Executive Chairman. The new CEO will be Inhi Cho Suh as detailed in the blog post. Neither Ingress or Recon/OPR were mentioned in the blog post.

😱7

11 Mar 2026, 18:46 UTC533 views11 reactionsread 7 August 2026

🪦 RECON CHAT PAUSED BECOMES INGRESS CHAT As Recon is paused, the Recon chat is temporarily a general Ingress chat. This channel name won’t change as we will be back to being a Recon chat when it comes back and will also provide any Recon updates whenever they come.

🔥101

10 Mar 2026, 23:19 UTC926 views13 reactionsread 7 August 2026
Photo

😅 OPR CLOSED Visiting the opr.ingress.com link now redirects to the main Ingress website. Now wait for OPR³

😭10🤬3

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

Citation-graph rank — 544,191 of 1,481,306entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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

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.

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“Niantic Spatial Recon/OPR UK” (@niaspatialuk), 229 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/niaspatialuk.

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.