Telegram RegisterThe public register of Telegram
Telegram profile photo for 南通公开榜

Channel

南通公开榜

@ntfpb

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

18,436subscribers

+1,809 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001843835711
TypeChannel
Username@ntfpb
Description致力于成为 #南通 最受信赖的出击群 【教务处】 : @Ntnb7 【上榜认证】: @Lufei777bot 【备用群组】: @NanT657 【联系管理】: @Lufei777bot 【靠谱包养】: @tangrenby 【查询】:导航 【工具】:汉化 出勤 让我们发现南通之美,发现美丽中国,主动私聊均为诈骗!!! 【聊天主群】 @ntsis 【报告区】 @ntbgb 【公开榜】 @ntfpb 【会所榜】 @ntspa8
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live10 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/ntfpb

Topic

Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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 the other topics.

Growth

14,12120,06217,091.512 August 2026 — 16,627 subscribers12 August 2026 — 16,627 subscribers12 August 2026 — 16,625 subscribers14 August 2026 — 16,633 subscribers15 August 2026 — 16,654 subscribers16 August 2026 — 16,660 subscribers17 August 2026 — 16,661 subscribers18 August 2026 — 16,660 subscribers19 August 2026 — 16,645 subscribers21 August 2026 — 16,653 subscribers22 August 2026 — 16,666 subscribers24 August 2026 — 16,671 subscribers25 August 2026 — 16,678 subscribers26 August 2026 — 16,683 subscribers27 August 2026 — 16,687 subscribers27 August 2026 — 16,699 subscribers28 August 2026 — 16,705 subscribers29 August 2026 — 16,712 subscribers30 August 2026 — 16,713 subscribers31 August 2026 — 16,714 subscribers2 September 2026 — 16,720 subscribers3 September 2026 — 16,730 subscribers5 September 2026 — 16,725 subscribers8 September 2026 — 16,746 subscribers11 September 2026 — 16,643 subscribers13 September 2026 — 16,349 subscribers14 September 2026 — 15,961 subscribers16 September 2026 — 15,594 subscribers19 September 2026 — 15,121 subscribers25 September 2026 — 14,121 subscribers4 October 2026 — 20,062 subscribers8 October 2026 — 19,712 subscribers13 October 2026 — 19,468 subscribers14 October 2026 — 19,350 subscribers15 October 2026 — 19,263 subscribers16 October 2026 — 19,180 subscribers17 October 2026 — 19,063 subscribers18 October 2026 — 19,037 subscribers19 October 2026 — 19,033 subscribers20 October 2026 — 19,043 subscribers22 October 2026 — 19,045 subscribers23 October 2026 — 19,008 subscribers23 October 2026 — 18,987 subscribers25 October 2026 — 18,977 subscribers25 October 2026 — 18,987 subscribers26 October 2026 — 18,978 subscribers27 October 2026 — 18,943 subscribers28 October 2026 — 18,924 subscribers29 October 2026 — 18,911 subscribers30 October 2026 — 18,774 subscribers31 October 2026 — 18,749 subscribers1 November 2026 — 18,715 subscribers2 November 2026 — 18,720 subscribers3 November 2026 — 18,707 subscribers4 November 2026 — 18,683 subscribers5 November 2026 — 18,644 subscribers6 November 2026 — 18,625 subscribers8 November 2026 — 18,570 subscribers9 November 2026 — 18,519 subscribers10 November 2026 — 18,436 subscribers18,43612 August 202610 November 2026
60 measurements spanning 91 days, net +1,809. 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 13,230–20,953 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
10 Nov 2026, 21:0118,436-83
9 Nov 2026, 07:1818,519-51
8 Nov 2026, 00:4018,570-55
6 Nov 2026, 20:2518,625-19
5 Nov 2026, 21:2418,644-39
4 Nov 2026, 21:3418,683-24
3 Nov 2026, 22:5518,707-13
2 Nov 2026, 21:3918,720+5
1 Nov 2026, 19:3718,715-34
31 Oct 2026, 22:2818,749-25
30 Oct 2026, 18:5618,774-137
29 Oct 2026, 17:2918,911-13
28 Oct 2026, 16:0818,924-19
27 Oct 2026, 17:3718,943-35
26 Oct 2026, 19:4018,978-9
25 Oct 2026, 23:1518,987+10
25 Oct 2026, 00:0418,977-10
23 Oct 2026, 21:2718,987-21
23 Oct 2026, 00:3019,008-37
22 Oct 2026, 01:4719,045first reading

Engagement

21 posts held, back to 13 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 61 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 21 posts for this entry, the most recent from 6 October 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
32
Videos
1
Links
19

Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
17s
Average length
17s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

3,546 reactions across 21 posts, in 8 distinct kinds. The most used accounts for 28.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1,01428.6%
❤97127.4%
🔥89225.2%
🥰3319.33%
👏3138.83%
🦄170.479%
😍60.169%
💯20.056%

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 21 of the 21 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 3,546 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 13 November 2025 to 6 October 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

6 Oct 2026, 08:21 UTC≈18,800 views17 reactionsread 12 November 2026
Photo

⚠️⚠️⚠️防骗提醒 近期已多人被骗 一、不少老师炸号不管,被骗子抢注车牌为频道,频道内仅留存机器人联系方式,车库车牌点进去是频道的是骗子。 二、经常上线,但频道长期未更新请谨慎约课 三、被盗号要求给订金 以各种理由让兄弟们多付钱的请注意 🚗🚕🚙 四、频道盲盒活动及各种套路抽奖必是骗子 老师们不要轻信私聊,发送你的号标注诈骗,让你私聊某某机器人解封的,是专业盗号,个别老师总被骗,不要轻信私聊,多留个心眼去群内核对以防被骗 发现教务处老师换人、炸号请第一时间向管理举报 骗局无处不在请大家捂好自己的钱包

❤17

3 Oct 2026, 03:46 UTC≈15,100 views2 reactionsread 12 November 2026

航海经验兑换🎁 12222 ➡️ 飞机会员三个月 16666 ☝️ 150出击卷 26666 ☝️260出击卷 27777 ☝️飞机会员一年 36666 ☝️ 360出击卷 每人每月可兑换一次奖品 五选一兑换核销 (不可大小号同时兑换) 出击优惠卷核销: @xiaomaoniuniubot 先出击后核销

❤2

25 Aug 2026, 08:21 UTC≈9,520 views13 reactionsread 12 November 2026
Photo

✅ Telegram账号被限制公开群发言?一键解封教程(可直接复制) 很多人突然发现: 「Sorry, you are currently restricted from posting in public groups」 或者中文提示「抱歉,目前您被限制无法在公开群组发送消息」 这是Telegram官方的反垃圾限制(账号级),不是单个群管理员禁言。 下面是目前最有效、最安全的解封方法,按步骤操作即可。 --- 第一步:确认自己是否被限制 1. 打开Telegram,顶部搜索 @SpamBot (认准带蓝色认证勾的官方机器人) 2. 点 Start 或发送 /start 3. 看机器人回复: - 如果显示 “Good news, no limits...” → 说明没有全局限制 - 如果提示有限制 → 继续往下做 --- 第二步:正式申诉(核心步骤) 在 @SpamBot 里按顺序点击: 1. Thi…

❤13

18 Aug 2026, 23:59 UTC≈38,800 views1,623 reactionsread 12 November 2026
Photo

⛽️濠河映月色,七夕赴温柔 一河灯火,两心相守 祝有情人朝夕相伴,岁岁安甜

🔥352🥰325❤323👍314👏306💯2🦄1

17 Aug 2026, 01:17 UTC≈28,400 views8 reactionsread 12 November 2026

已经有几位老师的号被限制了,在这里提醒大家: 不管是用机场还是傻瓜式VPN,切记不要频繁切换IP。具体为:短时间内一会切香港,一会切新加坡、日本或者其他国家。这种行为极易触发TG官方风控系统,导致账号直接被限制。一旦被限制,群里无法发言,无法主动私信他人,后面申诉解禁的成功率也不是100% 建议固定节点使用,多买一家机场或者VPN备用,这家香港节点连不上,切到另一家香港节点,这样基本没事(你说你一会香港一会新加坡的,就是坐飞机也不可能瞬间抵达吧)

❤8

8 Aug 2026, 06:38 UTC≈29,800 views6 reactionsread 12 November 2026

🔥南通濠河风景区表情包 https://t.me/addstickers/pack_3eee4720_by_mwtzklbot https://t.me/addstickers/pack_b7861e62_by_mwtzklbot https://t.me/addstickers/pack_3c38539a_by_mwtzklbot https://t.me/addstickers/pack_f0b44610_by_mwtzklbot https://t.me/addstickers/pack_a3b16288_by_mwtzklbot https://t.me/addstickers/pack_f904b0eb_by_mwtzklbot https://t.me/addstickers/pack_695aa9bc_by_mwtzklbot https://t.me/addstickers/pack_dc8b18…

❤5👍1

1 Aug 2026, 05:58 UTC≈25,700 views14 reactionsread 12 November 2026
Photo

🔥有骗子,大家注意了,南通濠河小助手是机器人,不会有会员和国家、注册时间 🉑从群组内点击确认✅ @ntbbbb

❤13🥰1

28 Jul 2026, 07:24 UTC≈9,460 views6 reactionsread 12 November 2026
Photo

云南哪有真情在,花椒树下谈恋爱! 你麻我来,我麻你! 克嫖最有性价比! 欢迎加入云南昆明电报群! https://t.me/KMDBQ 群内正在抽取大量现金红包!

❤6

22 Jul 2026, 08:22 UTC≈30,100 views8 reactionsread 12 November 2026
Photo

千年濠河,醉美南通 热烈庆祝🪅南通濠河风景区 即将突破50000成员,特发出千元红包 https://t.me/ntbbbb

❤7🔥1

19 Jul 2026, 06:46 UTC≈30,700 views23 reactionsread 12 November 2026

华北地区/东北地区 天津 太原 石家庄 哈尔滨 华中地区: 郑州 南阳 新乡 武汉 武汉2 襄阳 宜昌 长沙 衡阳 常德 华东地区: 济南 临沂 枣庄泰安济宁 聊城 南京 苏州 淮安 南通 盐城 宿迁 扬州泰州镇江 徐州 连云港 无锡 常州 合肥 皖南 阜阳亳州 宿州淮北 蚌埠淮南 上海 杭州 宁波 湖州 嘉兴 绍兴 南昌 赣州 景德镇 福建 华南地区 广州 佛山 东莞 珠海 惠州 江门 中山 南宁 柳州 海口 三亚 琼海 儋州 西南地区/西北地区 西安 兰州 成都 贵阳 遵义 昆明

❤9🦄6👍4🔥3🥰1

14 Jul 2026, 04:50 UTC≈30,400 views39 reactionsread 12 November 2026
Photo

🌐 江苏联盟群组 🚗 连云港 🔹 https://t.me/cswzhgs 🚗 盐城 🔹 https://t.me/ycmly2 🚗 扬州泰州镇江 🔹 https://t.me/olddriveryz1 🚗 徐州 🔹 https://t.me/xzsngc 🚗 淮安 🔹 https://t.me/huaian0001 🚗 常州 🔹 https://t.me/xlstl 🚗 无锡 🔹https://t.me/+uB1uXIsfgCQzMzRk 🚗 南通 🔹https://t.me/ntbbbb 🚗 宿迁 🔹https://t.me/suqianshi

❤20🦄6👍4👏3🔥3😍2🥰1

9 May 2026, 01:34 UTC≈45,100 views19 reactionsread 12 November 2026
Photo

狼友出击前可以先看报告榜再出击,结合一下,看下那个老师合适你。报告只能作为参考,毕竟每个人喜好不同,要求不同,好不好自己判断,长相如有太大出入直接走人,没有人逼你一定要去了就要上课的。不是自己喜欢的还要抱着来都来了的?然后上完发雷报和差评?你发的报告只会是在你愤怒的情况下写出来的,而且你不喜欢这个,你故意刁难老师,老师也不会对你有好脸色自然而然的就是差评,遇到老师没有按课表做服务,有机车行为,可以根据实际情况如实写出击报告提交到报告榜,同时我们会跟老师沟通责令改正 不改正就下榜。 狼友约课要注意上课时间,如果你比较持久不够敏感难出水的话,请约课时更长的课,有时候老师催你是可能是要到钟了 后面还有别的狼友等着,到钟拖堂不走会导致别的狼友罚站,将心比心换谁也不想罚站! 狼友们 出击前收拾好一下自己的仪容仪表,邋里邋遢的 ,谁看见会喜欢呢,要🐍吻就提前准备刷个牙出门啥的,有口臭就不要怪老师课表有🐍却不给你🐍, 三不要 不要要求嫩…

👍9❤7👏3

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

Posts edited after publishing

@ntfpb edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
14 August 2026
Most recent edit
25 August 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @ntfpb as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
17 August 2026
Most recent seen missing
3 November 2026
Median time before seen missing
31 days
Seen missing in the last 30 days
1

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

“南通公开榜” (@ntfpb), 18,436 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/ntfpb.

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.