Telegram RegisterThe public register of Telegram
Telegram profile photo for Ingress南京

Channel

Ingress南京

@ingressnj

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

196subscribers

+1 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-1001129281521
TypeChannel
Username@ingressnj
CreatedBetween 1 June 2017 and 31 October 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live28 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/ingressnj

Growth

194197195.57 August 2026 — 195 subscribers8 August 2026 — 195 subscribers15 August 2026 — 194 subscribers21 August 2026 — 197 subscribers28 August 2026 — 196 subscribers1967 August 202628 August 2026
5 measurements spanning 20 days, net +1. 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 194–197 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 02:42196-1
21 Aug 2026, 18:09197+3
15 Aug 2026, 02:23194-1
8 Aug 2026, 11:47195no change
7 Aug 2026, 21:26195first reading

Engagement

11 posts held, back to 1 September 2023the 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 11 posts for this entry, the most recent from 20 March 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

20 Mar 2026, 04:18 UTC79 viewsread 8 August 2026
Forwarded from @jiangningifsPhoto

清明假期来美丽江宁! 美丽江宁,全域旅游,四处是美景 清明假期邀请您尽览春牛首,亲水百家湖。 4月4日我们齐聚百家湖1912,百家湖摩天轮见! 日期: 2026/4/4 14:00 Base Portal: 百家湖 跃迁门 // Intel Link // Google Maps Restocking Portal: LOVE爱在三点零七分 // Intel Link// Google Maps Event Channel: t.me/jiangningifs Group link: t.me/Ifsjiangning 报名链接: https://fevgames.net/ifs/event/?e=29163

3 Dec 2025, 13:46 UTC442 viewsread 8 August 2026

☆诚邀【2025南绿年终聚餐】 时间:12 月 27 日 地点:南京·蒋云庵 14 号 报名:https://forms.gle/aPRq5jwM5LmrSLSz5 群组:https://t.me/+Apcs8gIPXPEyNTc9j 详情:https://mp.weixin.qq.com/s/BPqHRGBlxYMHrUtEGJNulQ

1 Jun 2025, 10:04 UTC599 viewsread 8 August 2026

#南京好吃 #南绿食堂 家人们,掬豆重出江湖,还是原来的味道! 【掬豆·山野小食堂】 ★★★☆☆ 3.7 ¥76/人 夫子庙地区 特色菜 小西湖33号楼 https://m.dianping.com/shopshare/G3G3sN1vOWJWlz72?msource=Appshare2021&utm_source=shop_share&shoptype=10&shopcategoryid=34284&cityid=5&isoversea=0

21 Feb 2025, 14:31 UTC≈1,200 viewsread 8 August 2026
Photo

#南京好玩 南京首次!「过森日」 【全国女子美学市集】 2.20-2.23.2025 南京·越界梦幻城 亲子友好/原创手作/非遗/诗歌/音乐/分享会/WORKSHOP https://mp.weixin.qq.com/s/pguZc9ww-ib_QLp09VQbNg

11 Oct 2024, 14:29 UTC≈1,520 viewsread 8 August 2026
Photo

#南京好玩 2024南京咖啡节来咯 时间:10.25-27&11.1-3 地点:玄武湖·樱洲 https://mp.weixin.qq.com/s/ZB_YtfGWFh5I9JrURwU5HA

18 Jul 2024, 09:21 UTC≈1,530 viewsread 8 August 2026

#南京好玩 【三格回忆录·我在南京(杭州)很想你😘】 https://mp.weixin.qq.com/s/UF8JqAxfo-kmYDs0HRal9A

25 Apr 2024, 03:09 UTC≈1,610 viewsread 8 August 2026

#南京好玩 【第六届不熟艺术书展·南京站】 媒体预展:2024年5月30日(周四) 公众开放:2024年5月31日-6月2日(周五-周日) 活动地点:南京市秦淮区越界梦幻城 https://mp.weixin.qq.com/s/y5BBEwVDGo7UYXvgidUVoQ

9 Apr 2024, 15:31 UTC≈1,520 viewsread 8 August 2026

#南京好玩 南京·有手就行艺术节 4.19-4.21 鼓楼创新广场·华开IN BOX街区 https://mp.weixin.qq.com/s/4acc5AqMuPVr57-JyWWrmA

24 Mar 2024, 12:55 UTC≈1,320 viewsread 8 August 2026
Photo

#南京好玩 【樱开速归】 假人们,家乡的撒苦啦又开了,快回来看看吧!

14 Mar 2024, 13:15 UTC≈1,120 viewsread 8 August 2026

#南京好玩 #绿妹专属 ·插播广告一则 ·来定制你的专属INGRESS美甲吧 ·详情咨询 @lajituzhu https://mp.weixin.qq.com/s/BPRvyrrMtw0iax5CQMHKrA

1 Sept 2023, 04:40 UTC≈1,550 viewsread 8 August 2026

#南京好玩 2023南京咖啡节来咯 时间:10.20~10.22,10.27~10.29 地点:玄武湖·樱洲 https://mp.weixin.qq.com/s/f44aoQl9RtbvX_M7hVkrag

Showing the 11 most recent of 11 posts we hold for @ingressnj. 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

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

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

“Ingress南京” (@ingressnj), 196 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/ingressnj.

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.