Telegram RegisterThe public register of Telegram
Telegram profile photo for 东莞公开榜2.0

Channel

东莞公开榜2.0

@dg98JT88

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry

20,837subscribers

+1,785 since we began measuring on 26 August 2026

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

Register entry

Telegram ID-1001063009959
TypeChannel
Username@dg98JT88
Description更多资源: @DG98JTbot Hello @Telegram My channel has not violated the rules and policy of using Telegram. Please pay attention. @rove
CreatedBetween 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded26 August 2026
Last confirmed live7 November 2026
Measurements held45
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/dg98JT88

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 11 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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

19,05220,83719,944.526 August 2026 — 19,052 subscribers26 August 2026 — 19,052 subscribers27 August 2026 — 19,093 subscribers28 August 2026 — 19,131 subscribers29 August 2026 — 19,180 subscribers30 August 2026 — 19,234 subscribers31 August 2026 — 19,263 subscribers1 September 2026 — 19,296 subscribers2 September 2026 — 19,313 subscribers4 September 2026 — 19,359 subscribers6 September 2026 — 19,409 subscribers9 September 2026 — 19,507 subscribers11 September 2026 — 19,592 subscribers13 September 2026 — 19,651 subscribers15 September 2026 — 19,676 subscribers17 September 2026 — 19,721 subscribers25 September 2026 — 19,820 subscribers4 October 2026 — 20,025 subscribers8 October 2026 — 20,107 subscribers13 October 2026 — 20,224 subscribers14 October 2026 — 20,264 subscribers15 October 2026 — 20,276 subscribers16 October 2026 — 20,312 subscribers17 October 2026 — 20,332 subscribers18 October 2026 — 20,366 subscribers19 October 2026 — 20,382 subscribers20 October 2026 — 20,400 subscribers21 October 2026 — 20,425 subscribers22 October 2026 — 20,452 subscribers23 October 2026 — 20,477 subscribers24 October 2026 — 20,515 subscribers25 October 2026 — 20,530 subscribers26 October 2026 — 20,566 subscribers27 October 2026 — 20,602 subscribers28 October 2026 — 20,618 subscribers29 October 2026 — 20,634 subscribers30 October 2026 — 20,636 subscribers31 October 2026 — 20,659 subscribers1 November 2026 — 20,667 subscribers2 November 2026 — 20,702 subscribers3 November 2026 — 20,723 subscribers4 November 2026 — 20,742 subscribers5 November 2026 — 20,750 subscribers6 November 2026 — 20,793 subscribers7 November 2026 — 20,837 subscribers26 August 20267 November 2026
45 measurements spanning 73 days, net +1,785. 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 18,784–21,105 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 45
Measured (UTC)SubscribersChange
7 Nov 2026, 12:5220,837+44
6 Nov 2026, 11:0820,793+43
5 Nov 2026, 08:0920,750+8
4 Nov 2026, 09:2120,742+19
3 Nov 2026, 11:1720,723+21
2 Nov 2026, 12:0820,702+35
1 Nov 2026, 09:0520,667+8
31 Oct 2026, 11:5620,659+23
30 Oct 2026, 13:3920,636+2
29 Oct 2026, 15:5520,634+16
28 Oct 2026, 16:2220,618+16
27 Oct 2026, 16:5520,602+36
26 Oct 2026, 17:4120,566+36
25 Oct 2026, 20:3020,530+15
24 Oct 2026, 17:5120,515+38
23 Oct 2026, 14:5520,477+25
22 Oct 2026, 17:5720,452+27
21 Oct 2026, 14:3920,425+25
20 Oct 2026, 10:5620,400+18
19 Oct 2026, 12:5720,382first reading

Engagement

84 posts held, back to 26 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 27 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.11%
avg views ÷ 20,837 subscribers
Avg views / post
439
30 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
30
of 84 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 held84 (26 August 2026 – 8 November 2026)
Views total13,168
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 15:11 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
≈25,900
Videos
≈5,100
Links
≈4,990

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
8m 54s
Average length
9s

Measured directly from 57 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: 1 of 30 posts held from the last 30 days (3.33%) 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).

8 Nov 2026, 12:18 UTC247 viewsread 8 November 2026
Photo

#南城 晓晓 (新人可🐍) 600一 1200二 电报: @xxixxo88 机器人 :@xiaoxiaoasd_bot 频道:https://t.me/xiaoxiaoghk88 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

8 Nov 2026, 12:05 UTC269 viewsread 8 November 2026
Photo

#大朗 丹妮可 P600 PP1200 私信:@danni16888889 频道:https://t.me/danni168888899 双向:@danni16888889_bot 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

8 Nov 2026, 11:39 UTC261 viewsread 8 November 2026
Photo

#东城 小小苍井空 600一 1200二 私聊:@Canjinkon1 双向:@Canglaoshi123bot 频道:https://t.me/shhtt520/20 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

8 Nov 2026, 10:25 UTC336 viewsread 8 November 2026
Photo

#虎门 花花 700一 1300二 电报: @huahua666682 双向:@huahuahuadqjrbot 频道:https://t.me/huahuasj787 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

7 Nov 2026, 15:15 UTC525 viewsread 8 November 2026
Photo

#南城 奶羞羞 600一 1100二 电报: @xiuxiu657 频道:@xiuxiu796 双向:@xiuxiu78bot 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

7 Nov 2026, 14:36 UTC535 viewsread 8 November 2026
Photo

#大朗 曦儿 500一 900二 私信: @xier389 双向: @danji69bot 频道: @xier783 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

7 Nov 2026, 14:13 UTC520 viewsread 8 November 2026
Photo

#南城 冉冉 700一 1400二 机器人🤖:@ranranzs_bot 频道:https://t.me/rnfse_hebd 私聊:@ranran8860 公开链接: @DG98JTbot 出击报告(置顶模版): @DG98jituan

7 Nov 2026, 12:58 UTC523 viewsread 8 November 2026
Photo

#大朗 洋洋 500P 1000PP 频道: t.me/Ayangyang88 双向:@Ayangyangbotbot 私信:@Ayangyang66 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

7 Nov 2026, 12:52 UTC221 viewsread 7 November 2026
Photo

#南城 晓晓 (新人可🐍) 600一 1200二 电报: @xxixxo88 机器人 :@xiaoxiaoasd_bot 频道:https://t.me/xiaoxiaoghk88 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

6 Nov 2026, 14:07 UTC560 viewsread 7 November 2026
Photo

#虎门 小倩 500一 900二 电报:@laty236 频道:https://t.me/yuehj76 机器人:@yyuir76Bot 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

6 Nov 2026, 13:24 UTC579 viewsread 7 November 2026
Photo

#大朗 小柔 500一 1000二 频道:https://t.me/huihuiqq12 双向:@huihui12bot 私信:@huihuimm12 公开链接: @DG98JTbot 出击报告(置顶模版): @DG98jituan

6 Nov 2026, 13:01 UTC486 viewsread 7 November 2026
Photo

#大朗 洋洋 500P 1000PP 频道: t.me/Ayangyang88 双向:@Ayangyangbotbot 私信:@Ayangyang66 更多资源: @DG98JTbot 出击报告(置顶模版): @DG98jituan

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

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.

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

“东莞公开榜2.0” (@dg98JT88), 20,837 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/dg98JT88.

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.