Channel
@NG_63
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
8,132subscribers
-344 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001890941232 |
|---|---|
| Type | Channel |
| Username | @NG_63 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/NG_63 |
Gambling & betting — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 12:01 | 8,132 | -28 |
| 13 Sept 2026, 17:21 | 8,160 | -65 |
| 10 Sept 2026, 02:58 | 8,225 | -3 |
| 4 Sept 2026, 18:02 | 8,228 | -31 |
| 1 Sept 2026, 14:05 | 8,259 | -6 |
| 29 Aug 2026, 13:44 | 8,265 | -8 |
| 26 Aug 2026, 19:13 | 8,273 | -13 |
| 23 Aug 2026, 16:23 | 8,286 | +27 |
| 20 Aug 2026, 09:17 | 8,259 | -43 |
| 17 Aug 2026, 17:15 | 8,302 | -91 |
| 14 Aug 2026, 09:27 | 8,393 | -59 |
| 10 Aug 2026, 22:28 | 8,452 | -25 |
| 7 Aug 2026, 17:22 | 8,477 | +1 |
| 7 Aug 2026, 10:45 | 8,476 | no change |
| 7 Aug 2026, 10:33 | 8,476 | first reading |
4 posts held, back to 8 March 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 23 pages 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 4 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
凌晨大水 嘎嘎干就完了 推荐 问鼎娱乐 NG体育 高赔率 高爆台 PG电子 PP电子持续大水中 百倍 千倍 万倍 不停 🔥 🔥 活 动 客 服 : @ng_889 👍 新人100送100 ( 加拿大28预测群：@SS77887 ） 🔥 新人扶持累计充值满600送388 🧧 👍手 机 APP 注 册 下 载 (安 卓 手 机 关 闭纯 净 模 式 下 载， 机 型 不 会 的 百 度 一 下） …
Signed 南宫 集团
PG凌晨水位绝对哇塞~~认准老平台~世界杯不迷路~放心大胆干~~~推荐 问鼎娱乐 NG体育 高赔率 高爆台 PG电子 PP电子持续大水中 百倍 千倍 万倍 不停 🔥 🔥 活 动 客 服 : @ng_889 👍 新人100送100 ( 加拿大28预测群：@SS77887 ） 🔥 新人扶持累计充值满600送388 🧧 👍手 机 APP 注 册 下 载 (安 卓 手 机 关 闭纯 净 模 式 下 载， 机 型 不 会 的 百 度 一 下） …
Signed 南宫 集团
感谢老铁们的反馈~~十年老品牌 信誉台 现在活动超多 水位很大 不服就是干~~~~~~~~~~~推荐 问鼎娱乐 NG体育 高赔率 高爆台 PG电子 PP电子持续大水中 百倍 千倍 万倍 不停 🔥 🔥 活 动 客 服 : @ng_889 👍 新人100送100 ( 加拿大28预测群：@SS77887 ） 🔥 新人扶持累计充值满600送388 🧧 👍手 机 APP 注 册 下 载 (安 卓 手 机 关 闭纯 净 模 式 下 载， 机 型 不 会 的 百 度 一 下） …
Signed 南宫 集团
春节期间 水位都是直接拉满的 各位老哥牛逼 福利超多 奖励也超多~~~~~~~~~~~推荐 问鼎娱乐 NG体育 高赔率 高爆台 PG电子 PP电子持续大水中 百倍 千倍 万倍 不停 🔥 🔥 活 动 客 服 : @ng_889 👍 新人100送100 ( 加拿大28预测群：@SS77887 ） 🔥 新人扶持累计充值满600送388 🧧 👍手 机 APP 注 册 下 载 (安 卓 手 机 关 闭纯 净 模 式 下 载， 机 型 不 会 的 百 度 一 下） …
Signed 南宫 集团
Showing the 4 most recent of 4 posts we hold for @NG_63. 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.
Named by 2 registered channels — 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“南宫 壹号 问鼎 亿万 官方频道” (@NG_63), 8,132 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/NG_63.
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.