Telegram RegisterThe public register of Telegram
Telegram profile photo for 宁波TG老师专榜

Channel

宁波TG老师专榜

@nbtgzb

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

28,308subscribers

+1,102 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1001942025496
TypeChannel
Username@nbtgzb
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live8 November 2026
Measurements held54
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/nbtgzb

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 64% 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

27,20628,49127,848.514 August 2026 — 27,206 subscribers16 August 2026 — 27,284 subscribers17 August 2026 — 27,322 subscribers18 August 2026 — 27,403 subscribers19 August 2026 — 27,579 subscribers20 August 2026 — 27,649 subscribers21 August 2026 — 27,735 subscribers22 August 2026 — 27,692 subscribers24 August 2026 — 27,852 subscribers25 August 2026 — 27,705 subscribers26 August 2026 — 27,742 subscribers27 August 2026 — 27,845 subscribers28 August 2026 — 27,927 subscribers29 August 2026 — 27,827 subscribers30 August 2026 — 27,894 subscribers31 August 2026 — 28,013 subscribers1 September 2026 — 28,086 subscribers2 September 2026 — 28,163 subscribers4 September 2026 — 28,254 subscribers7 September 2026 — 28,253 subscribers10 September 2026 — 28,467 subscribers12 September 2026 — 28,215 subscribers14 September 2026 — 28,225 subscribers15 September 2026 — 28,352 subscribers17 September 2026 — 28,491 subscribers28 September 2026 — 27,825 subscribers5 October 2026 — 27,879 subscribers9 October 2026 — 27,870 subscribers13 October 2026 — 27,958 subscribers14 October 2026 — 28,003 subscribers15 October 2026 — 28,039 subscribers16 October 2026 — 28,057 subscribers17 October 2026 — 28,095 subscribers18 October 2026 — 28,107 subscribers19 October 2026 — 28,129 subscribers20 October 2026 — 28,119 subscribers21 October 2026 — 28,148 subscribers22 October 2026 — 28,168 subscribers23 October 2026 — 27,992 subscribers24 October 2026 — 28,042 subscribers25 October 2026 — 28,067 subscribers26 October 2026 — 28,100 subscribers27 October 2026 — 28,124 subscribers28 October 2026 — 28,147 subscribers29 October 2026 — 28,166 subscribers30 October 2026 — 28,149 subscribers31 October 2026 — 28,181 subscribers1 November 2026 — 28,219 subscribers2 November 2026 — 28,242 subscribers3 November 2026 — 28,264 subscribers4 November 2026 — 28,292 subscribers5 November 2026 — 28,332 subscribers6 November 2026 — 28,280 subscribers8 November 2026 — 28,308 subscribers28,30814 August 20268 November 2026
54 measurements spanning 85 days, net +1,102. 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 27,013–28,684 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 54
Measured (UTC)SubscribersChange
8 Nov 2026, 02:1028,308+28
6 Nov 2026, 21:0728,280-52
5 Nov 2026, 19:5128,332+40
4 Nov 2026, 18:4028,292+28
3 Nov 2026, 20:1728,264+22
2 Nov 2026, 18:4528,242+23
1 Nov 2026, 17:2928,219+38
31 Oct 2026, 20:5428,181+32
30 Oct 2026, 20:1928,149-17
29 Oct 2026, 18:5828,166+19
28 Oct 2026, 21:2128,147+23
27 Oct 2026, 23:0128,124+24
26 Oct 2026, 19:1128,100+33
25 Oct 2026, 17:4828,067+25
24 Oct 2026, 20:0828,042+50
23 Oct 2026, 19:4727,992-176
22 Oct 2026, 23:0028,168+20
21 Oct 2026, 20:0028,148+29
20 Oct 2026, 14:3528,119-10
19 Oct 2026, 12:4928,129first reading

Engagement

178 posts held, back to 6 August 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 162 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
13.3%
avg views ÷ 28,308 subscribers
Avg views / post
3,770
71 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
71
of 178 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 November 2026
Posts held178 (6 August 2026 – 8 November 2026)
Views total267,930
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 19:26 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,240
Videos
≈1,110
Links
≈1,110

Lifetime counters from Telegram’s own channel header, read 8 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
22m 55s
Average length
9s

Measured directly from 153 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: 2 of 71 posts held from the last 30 days (2.82%) 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).

6 Nov 2026, 16:32 UTC≈3,850 viewsread 8 November 2026
Photo

【老师编号】:#NBTG1231 【老师昵称】:#棠柔 【修车水费】:#5P 【是否验证】:#已验 工兵报告1 【联系方式】:@yuuehe 【宁波天一生水】

6 Nov 2026, 10:19 UTC≈4,090 viewsread 8 November 2026
Photo

【老师编号】:#NBTG1232 【老师昵称】:#晨夕儿 【修车水费】:#6P 【是否验证】:#已验 工兵报告1 【联系方式】: @chenbo8881 【宁波天一生水】

6 Nov 2026, 06:39 UTC≈4,160 viewsread 8 November 2026
Photo

【老师编号】:#NBTG1230 【老师昵称】:#小妞 【修车水费】:#5P 【是否验证】:#已验 工兵报告1 【联系方式】: @xy10251688 【宁波天一生水】

5 Nov 2026, 15:37 UTC≈4,520 viewsread 8 November 2026
Photo

【老师编号】:#NBTG1223 【老师昵称】:#小曦 【修车水费】:#7P 【是否验证】:#已验 工兵报告1 【联系方式】: @xiaoxihenb 【宁波天一生水】

5 Nov 2026, 09:24 UTC≈4,770 viewsread 8 November 2026
Photo

【老师编号】:#NBTG1229 【老师昵称】:#晗露 【修车水费】:#5P 【是否验证】:#已验 工兵报告1 【联系方式】: @iiuuysw 【宁波天一生水】

4 Nov 2026, 00:28 UTC≈5,890 viewsread 8 November 2026
Photo

【老师编号】:#NBTG1228 【老师昵称】:#鸭鸭 【修车水费】:#5P 【是否验证】:#已验 工兵报告1 【联系方式】: @Pan989898 【宁波天一生水】

3 Nov 2026, 15:50 UTC≈6,060 viewsread 8 November 2026
Photo

【老师编号】:#NBTG1225 【老师昵称】:#景言 【修车水费】:#5P 【是否验证】:#已验 工兵报告1 【联系方式】: @jingtpei 【宁波天一生水】

3 Nov 2026, 12:37 UTC≈1,790 viewsread 4 November 2026
Video

💞 联系客服 / 女仆交流群 / 资料频道

3 Nov 2026, 07:27 UTC≈4,320 viewsread 6 November 2026
Photo

【老师编号】:#NBTG1227 【老师昵称】:#小兔兔 ,#美少女 【修车水费】:#12P 【特 色】:护士兼职、反差 【是否验证】:#未验 【联系方式】:@miaokryuedemei 【宁波天一生水】

2 Nov 2026, 01:13 UTC≈5,380 viewsread 6 November 2026
Photo

【老师编号】:#NBTG1226 【老师昵称】:#妮宝 【修车水费】:#6P 【是否验证】:#已验 工兵报告1 工兵报告2 工兵报告3 【联系方式】: 已离开宁波 【宁波天一生水】

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

@nbtgzb edited 3 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
16 August 2026
Most recent edit
4 November 2026

Posts recorded as deleted after publishing

We recorded 77 posts on @nbtgzb 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
16 August 2026
Most recent seen missing
8 November 2026
Median time before seen missing
37 hours
Seen missing in the last 30 days
30

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

“宁波TG老师专榜” (@nbtgzb), 28,308 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/nbtgzb.

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.