🎉 AgentMetBot 一周年啦!🎉 2025 年 7 月 25 日,MetBot 正式上线。 这一年里,感谢每一位 Agent 的陪伴与支持 ❤️ 值此周年庆,限定纪念成就限时开放领取! 👉 点击链接即可解锁: https://t.me/AgentMetBot?start=swpjbWV0Ym90XzF5ZWFyfG1ydDNkd283fDI3MA==3cbs ⏰ 有效期至 8 月 1 日 00:00,过期不候~ 快叫上群里的小伙伴一起来领,咱们明年见!🥂

Channel
Ingress Chengdu&Chongqing
@IngressChengduChongqing
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
532subscribers
-10 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 | -1001112554588 |
|---|---|
| Type | Channel |
| Username | @IngressChengduChongqing |
| Created | 21 March 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/IngressChengduChongqing |
Topic
Gaming — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 00:00 | 532 | -4 |
| 3 Sept 2026, 10:23 | 536 | -1 |
| 26 Aug 2026, 13:48 | 537 | -4 |
| 20 Aug 2026, 11:34 | 541 | +1 |
| 12 Aug 2026, 22:33 | 540 | -2 |
| 6 Aug 2026, 18:18 | 542 | no change |
| 6 Aug 2026, 01:53 | 542 | first reading |
Engagement
20 posts held, back to 7 January 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 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 20 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
18 reactions across 4 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 9 | 50.0% | |
| ❤ | 7 | 38.9% | |
| 👍 | 1 | 5.56% | |
| 👎 | 1 | 5.56% |
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 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 18 reactions 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 7 January 2026 to 20 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
#Ingress #Passcode 0gzh7nemesism030f
👍1👎1
#Ingress #Passcode 4vuz7explorer537t
#Ingress #Passcode 8zyz4nagassay227q
#Ingress #Passcode 6xdr2darke400h
#Ingress #Passcode 2edc6controln045o
❤1
#Ingress #Passcode 4sec0operativey389h
#Ingress #Passcode 7uub9sitrept937q
#Ingress #Passcode 3xvn3reportt375v
#Ingress #Passcode 4tnq0chapeaux944k
#Ingress #Passcode 8tng8shapem477g
#Ingress #Passcode 5dsr3witnessq528o
Signed ꧁༺𝓒𝓱𝓲𝓷𝓰𝓒𝓱𝓾𝓷𝓰༻꧂ ꧁༺𝓣𝓪𝓸༻꧂
Showing the 12 most recent of 20 posts we hold for @IngressChengduChongqing. 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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“Ingress Chengdu&Chongqing” (@IngressChengduChongqing), 532 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/IngressChengduChongqing.
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.