Telegram RegisterThe public register of Telegram

Channel

💊Niantic Spatial又给大家拉了什么

@shitofniantic

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

492subscribers

-2 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-1001405540629
TypeChannel
Username@shitofniantic
CreatedBetween 1 March 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 14 August 2026
On Telegramt.me/shitofniantic

Growth

4924944936 Aug 2026, 10:59 — 494 subscribers6 Aug 2026, 18:47 — 494 subscribers7 Aug 2026, 09:57 — 492 subscribers6 Aug 2026, 10:597 Aug 2026, 09:57
3 measurements taken within a single day, net -2. 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 492–494 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 09:57492-2
6 Aug 2026, 18:47494no change
6 Aug 2026, 10:59494first reading

Engagement

20 posts held, back to 18 May 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.

ERR · 30 days
37.6%
avg views ÷ 492 subscribers
Avg views / post
185
3 posts measured
Reaction rate
4.14%
reactions ÷ views · ER floor
Posts in window
3
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 22 July 2026
Posts held20 (18 May 202622 July 2026)
Views total555
Reactions total23
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 18:47 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.

Reaction mix

23 reactions across 3 posts, in 7 distinct kinds. The most used accounts for 52.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣1252.2%
🖕313.0%
👎28.70%
🔥28.70%
😁28.70%
💅14.35%
🥴14.35%

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 3 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 23reactions 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 18 May 2026 to 22 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

22 Jul 2026, 05:11 UTC149 views4 reactionsread 6 August 2026
Photo

brain rose小时候写作业写到一半出去吃个饭回来一看作业变回没写的时候了(操作一下刷新能好)

🔥2🤣1😁1

19 Jul 2026, 15:49 UTC267 views15 reactionsread 6 August 2026

Brian Rose小时候学校管不住学生作弊,于是直到毕业都没有恢复课堂作业和考试

🤣11👎2💅1🥴1

19 Jul 2026, 15:47 UTC139 views4 reactionsread 6 August 2026
Forwarded from @AgentMedal

#Recon 關於申Po 與超頻的最新動態:申Po 尚無恢復時間表,超頻不會復活 根據@IUENG 發布的最新資訊 顯示,腦花回應了一些大家關注的問題,以下為本台解讀 關於申Po 恢復,猩猩目前未找到可靠的方式來應對先前的作弊漏洞,因此仍放在待辦事項裡,未有實質的恢復時間表。 關於超頻功能,NIAS 分家後的替代方案僅面向遊戲以外的其他客戶群,不支援遊戲應用場景,也就是遊戲內的超頻功能不會復活。 腦花指出,猩猩開發團隊目前的工作重點是重構後端,以避免5月16日雪梨和布拉格XMA 的大規模遊戲故障事件再次發生。 過些日子,官方部落格會揭露更多後端工作的進度。 原文机翻: 特工 @PkmnTrainerJ 最近聯繫了 Ingress 的遊戲總監 Brian Rose,並詢問了一些關於 OPR/Recon、超頻以及其他一些問題。 關於 OPR/Recon,團隊目前還沒有時間對其進行任何實質性的改動,但它仍然在待辦

🖕3😁1

24 Jun 2026, 22:50 UTC389 viewsread 6 August 2026

改名卡确实早该有了,但是交钱无痛转阵营实在是太他妈难绷了

24 Jun 2026, 22:50 UTC279 viewsread 6 August 2026
Forwarded from @IngressChinesePhoto

「陣營令牌」及「代號令牌」隆重登場! 詳情請見: https://ingress.com/news/2026-factiontokencodenametoken

30 May 2026, 03:24 UTC215 viewsread 6 August 2026
Forwarded from @NianticOfficial

With the surge in Agent activity leading into Orion Kure and Orion Jersey City, the Portal Network is reacting with a temporary increase in Resonator, XMP, and Ultra Strike hack output. Additionally, we have added 2 new optional Load Out Kits to the in-game Store available for purchase: 500 Resonators and 500 XMPs (500 Resonators or 500 XMPs at your Access Level, up to L8). These bundles will be live until the end o

Showing the 12 most recent of 20 posts we hold for @shitofniantic. 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 — 900,844 of 1,340,412entries 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

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

Named by 1 registered channel — 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.

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

“💊Niantic Spatial又给大家拉了什么” (@shitofniantic), 492 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/shitofniantic.

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.