坐标:#南京 #秦淮区 花名:# 陈静怡 认证:已认证 课费:700P 1300PP 私聊:@chenjingy1 双向:@zizizib_bot 频道: @cjingy111 服务:看课表

Channel
南京资源认证榜
@njzyrzb2
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
84,084subscribers
+25,663 since we began measuring on 13 September 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001583269237 |
|---|---|
| Type | Channel |
| Username | @njzyrzb2 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/njzyrzb2 |
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 4 October 2026 and assigned it the closest of 31 fixed categories, at 88% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Nov 2026, 14:47 | 84,084 | -51 |
| 7 Nov 2026, 10:14 | 84,135 | +286 |
| 6 Nov 2026, 12:10 | 83,849 | +341 |
| 5 Nov 2026, 14:08 | 83,508 | +1,469 |
| 4 Nov 2026, 12:36 | 82,039 | +489 |
| 3 Nov 2026, 15:16 | 81,550 | +590 |
| 2 Nov 2026, 15:06 | 80,960 | +255 |
| 1 Nov 2026, 17:57 | 80,705 | +644 |
| 31 Oct 2026, 21:18 | 80,061 | -2,711 |
| 31 Oct 2026, 00:46 | 82,772 | +1,370 |
| 30 Oct 2026, 02:48 | 81,402 | +388 |
| 29 Oct 2026, 03:36 | 81,014 | +614 |
| 28 Oct 2026, 04:47 | 80,400 | +29 |
| 27 Oct 2026, 07:06 | 80,371 | +80 |
| 26 Oct 2026, 07:36 | 80,291 | +275 |
| 25 Oct 2026, 04:19 | 80,016 | +304 |
| 24 Oct 2026, 01:28 | 79,712 | -210 |
| 22 Oct 2026, 22:05 | 79,922 | +446 |
| 21 Oct 2026, 17:37 | 79,476 | +835 |
| 20 Oct 2026, 17:16 | 78,641 | first reading |
Engagement
113 posts held, back to 11 September 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 119 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.625%
- avg views ÷ 84,084 subscribers
- Avg views / post
- 526
- 76 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 77
- of 113 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.
| Window | Rolling 30 days · latest post in window 7 November 2026 |
|---|---|
| Posts held | 113 (11 September 2026 – 7 November 2026) |
| Views total | 39,957 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Nov 2026, 05:01 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.
What this channel posts
- Photos
- ≈1,580
- Videos
- ≈331
- Links
- ≈258
Lifetime counters from Telegram’s own channel header, read 9 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 9m 45s
- Average length
- 11s
Measured directly from 55 videos 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.
Recent posts
Telegram’s own ‘edited’ marker: 3 of 77 posts held from the last 30 days (3.90%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🎟️ 抽奖标题:南京栖霞区顶流模特36E大乔抽奖福利 📪抽奖说明:中奖者机器人会发送中奖信息 中奖截图联系:@njdqbb 🎫 参与条件: 🎫 加入-南京顶流模特大乔38E🔥 🎫 加入-南京资源认证榜 🎫 加入-南京修车聚集地 🎁 奖品内容: 💰️ 口令红包10 × 1 💰️ 包夜优惠500 × 5 💰️ 两次优惠300 × 10 💰️ 1p优惠卷200 × 10 📅 开奖时间:2026-11-10 21:00自动开奖 👉 参与抽奖链接: https://t.me/zzbjqrbot?start=join-L179404223331
🎟️ 抽奖标题:南京雨花区小羔羊老师抽奖福利 📪抽奖说明:中奖者机器人会发送中奖信息 中奖截图联系:@jiji2388 🎫 参与条件: 🎫 加入-小羊羔的窝 🎫 加入-南京修车聚集地 🎫 加入-南京资源认证榜 🎁 奖品内容: 💰️ 口令红包10 × 3 💰️ pp优惠200 × 10 💰️ 1p优惠100 × 10 📅 开奖时间:2026-11-12 20:00自动开奖 👉 参与抽奖链接: https://t.me/zzbjqrbot?start=join-L179403620483
坐标:#南京 #建邺区 花名:#沐兮 课费:600P 1100PP 私聊:@muxijiejie 双向:https://t.me/muxiibot 频道:https://t.me/muxidexiaowo 近期车评:https://t.me/muxidexiaowo/936 服务:看课表
🎟️ 抽奖标题:南京栖霞区兔子老师抽奖福利 📪抽奖说明:中奖者机器人会发送中奖信息 中奖截图联系:@vvao861 🎫 参与条件: 🎫 加入-💕南京兔子兼职朋友圈💗 🎫 加入-南京资源认证榜 🎫 加入-南京修车聚集地 🎁 奖品内容: 💰️ 口令红包15 × 1 💰️ 包夜优惠500 × 6 💰️ 2p优惠300 × 8 💰️ 1p优惠200 × 10 📅 开奖时间:2026-11-08 22:00自动开奖 👉 参与抽奖链接: https://t.me/zzbjqrbot?start=join-L179388520491
坐标:#南京 #南站 花名:#小V 课费:800P 1300PP 私聊:@xiaovdev 双向:@xiaovdzsglbot 服务:看课表
坐标:#南京 #栖霞区 花名:#兔子(兼职) 课费:800P 1500PP 私聊:@vvao861 双向:@tuzi22qzt_bot 频道:https://t.me/kkllw62 服务:看课表
🎟️ 抽奖标题:南京栖霞区允儿老师抽奖福利 📪抽奖说明:中奖者机器人会发送中奖信息 中奖截图联系:@mimils8 🎫 参与条件: 🎫 加入-允儿06自聊 🎫 加入-南京修车聚集地 🎫 加入-南京资源认证榜 🎁 奖品内容: 💰️ 口令红包28.88 × 1 💰️ PP优惠200 × 5 💰️ 1P优惠100 × 8 📅 开奖时间:2026-11-08 20:00自动开奖 👉 参与抽奖链接: https://t.me/zzbjqrbot?start=join-L179386737402
坐标:#南京 #建业区 花名:# 米小米 课费:700p-1300pp 私聊:@Llixaio 双向:@liqiaem253_bot 频道:https://t.me/lixiaoli935 服务:看课表
坐标:#南京 #雨花台 花名:# 笑笑 课费:700P 1300PP 私聊:@xoiuqwek 双向:@xiaoxiao084_bot 频道:@xiaoxiao080_bot 服务:看课表
坐标:#南京 #江宁区 /雨花区交界/龙西新寓 花名:# 晴儿(个人95) 课费:500p(50分钟起) 私聊:@nanjingqinger 双向:@Affgd_bot 群聊:https://t.me/nanjingdeqinger 频道:https://t.me/nanzhanqinger 服务:看课表
坐标:#南京 #建业区 花名:# 茉莉 课费:700P 1300PP 私聊:@moli_3330 频道:https://t.me/ml0555550 服务:看课表
Showing the 12 most recent of 113 posts we hold for @njzyrzb2. 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
@njzyrzb2 edited 1 post 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
- 23 September 2026
- Most recent edit
- 23 September 2026
Posts recorded as deleted after publishing
We recorded 7 posts on @njzyrzb2 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
- 14 September 2026
- Most recent seen missing
- 2 November 2026
- Median time before seen missing
- 31 hours
- Seen missing in the last 30 days
- 4
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.
Names
Channels on the register whose handles appear in this channel's posts.
@njltxcjjd1 · 100,95417 posts🧧GT免费抽奖机器人🧧
@zzbjqrbot · 18,96417 posts雪雪的聊天群💦💦
@xuexueChat · 5134 posts小羊羔的窝
@QloSfShpBt9mNTBk · 1,3573 posts南站晴儿个人95交流群
@nanjingdeqinger · 17,7832 posts南站晴儿95个人频道
@nanzhanqinger · 2,1842 posts音酱
@xiaoqingge546 · 22,2902 posts喷💦衣如雪后花园🌸
@xuangil · 1,3262 posts鱼糯糯的频道
@yueerkeyi · 1,0952 posts南京苏苏的后花园
@caomeicaoa · 1,4031 post豆豆的🎀秘密🎀
@doudounanjing · 8471 post梁楠楠
@duoduonjnj · 4381 post南京小宝修车喝茶交流群
@fm00012 · 5201 post桃子🍑
@gfggc85588 · 3241 post灵儿的频道
@lineriii · 771 post小蜜个人(大专商务)
@mimidgrdd52 · 5061 post💗熊宝宝的窝💗
@nanjingxiong · 7301 post南京私影女仆·南京西西里总频道
@NJSicily · 10,1061 post南京西西里·女仆私影交流总群
@NJXXLZQ · 12,8141 post糖糖的心事
@tangtangjianzhi · 1661 post南京老友汇
@tjxcyjs · 62,2231 post麦麦那么可爱
@tutunmka · 1,0761 post六六的小窝
@ww11081218 · 61 post小雅的频道
@xiaoyaya936 · 2,6731 post
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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“南京资源认证榜” (@njzyrzb2), 84,084 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/njzyrzb2.
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.