Telegram RegisterThe public register of Telegram
Telegram profile photo for dtbpyq

Channel

dtbpyq

@dtbpyq

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

13,334subscribers

+6,937 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002647737156
TypeChannel
Username@dtbpyq
Description№ 8424746355 “地推不累,客户翻倍—【地推宝】!🫵” #地推 #贴纸 #贴车 #扫楼 #盖章 #喷码 【地推交流】 @DiTuiBao 【粉圈交流】 @TianQue 【骗子曝光】 @HCCBG 【灰产揭秘】 @HuiShiJie 【电报业务】 @NFTXG 【能量租赁】 @NengLian 【业务对接】 @DTBUU
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 November 2026
Measurements held46
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/dtbpyq

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

6,39713,3349,865.58 August 2026 — 6,397 subscribers8 August 2026 — 6,397 subscribers8 August 2026 — 6,491 subscribers11 August 2026 — 6,718 subscribers15 August 2026 — 7,206 subscribers17 August 2026 — 7,340 subscribers20 August 2026 — 7,580 subscribers24 August 2026 — 7,685 subscribers27 August 2026 — 7,874 subscribers31 August 2026 — 8,101 subscribers3 September 2026 — 8,426 subscribers8 September 2026 — 8,905 subscribers12 September 2026 — 9,191 subscribers16 September 2026 — 9,446 subscribers24 September 2026 — 9,934 subscribers4 October 2026 — 10,458 subscribers9 October 2026 — 10,958 subscribers13 October 2026 — 11,427 subscribers14 October 2026 — 11,518 subscribers15 October 2026 — 11,633 subscribers16 October 2026 — 11,683 subscribers17 October 2026 — 11,768 subscribers18 October 2026 — 11,801 subscribers19 October 2026 — 11,859 subscribers20 October 2026 — 11,902 subscribers21 October 2026 — 11,953 subscribers22 October 2026 — 11,981 subscribers23 October 2026 — 12,069 subscribers24 October 2026 — 12,071 subscribers25 October 2026 — 12,112 subscribers27 October 2026 — 12,170 subscribers28 October 2026 — 12,217 subscribers29 October 2026 — 12,247 subscribers30 October 2026 — 12,342 subscribers31 October 2026 — 12,360 subscribers1 November 2026 — 12,481 subscribers1 November 2026 — 12,537 subscribers2 November 2026 — 12,589 subscribers3 November 2026 — 12,700 subscribers4 November 2026 — 12,770 subscribers5 November 2026 — 12,845 subscribers6 November 2026 — 12,920 subscribers8 November 2026 — 12,990 subscribers9 November 2026 — 13,045 subscribers11 November 2026 — 13,288 subscribers16 November 2026 — 13,334 subscribers8 August 202616 November 2026
46 measurements spanning 100 days, net +6,937. 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 5,356–14,375 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 46
Measured (UTC)SubscribersChange
16 Nov 2026, 08:4113,334+46
11 Nov 2026, 03:1513,288+243
9 Nov 2026, 08:4413,045+55
8 Nov 2026, 01:2112,990+70
6 Nov 2026, 20:2412,920+75
5 Nov 2026, 18:2612,845+75
4 Nov 2026, 21:0712,770+70
3 Nov 2026, 22:3612,700+111
2 Nov 2026, 20:4112,589+52
1 Nov 2026, 22:2612,537+56
1 Nov 2026, 00:5012,481+121
31 Oct 2026, 00:3612,360+18
30 Oct 2026, 02:0812,342+95
29 Oct 2026, 00:4912,247+30
28 Oct 2026, 01:4712,217+47
27 Oct 2026, 01:5512,170+58
25 Oct 2026, 22:1712,112+41
24 Oct 2026, 21:1612,071+2
23 Oct 2026, 21:3612,069+88
22 Oct 2026, 23:5911,981first reading

Engagement

314 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 58 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.754%
avg views ÷ 13,334 subscribers
Avg views / post
101
136 posts measured
Reaction rate
0.357%
reactions ÷ views · ER floor
Posts in window
136
of 314 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. It is computed over the 3 of 136 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 19 November 2026
Posts held314 (6 August 2026 – 19 November 2026)
Views total13,675
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken19 Nov 2026, 01:36 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
35
Videos
5
Links
21

Lifetime counters from Telegram’s own channel header, read 19 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.

Reaction mix

3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤266.7%
👌133.3%

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

Measured over the 314 most recent posts we hold, published 6 August 2026 to 19 November 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

Telegram’s own ‘edited’ marker: 3 of 136 posts held from the last 30 days (2.21%) 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).

19 Nov 2026, 00:16 UTC18 viewsread 19 November 2026

😊【地推宝】 @DiTuiBao 🎁 🎁 会员代开 |🎁 电报业务 🤑 能量租赁 |♥ 香烟专卖 🌐 闪连VPN |📱 PikPak下载 娱乐导航 🎁【灰世界】实时新闻推送 🔍【搜Now】全网搜索神器 📱【QQ传媒】一站式免费看片 ❗❗❗❗❗❗❗❗❗❗ 点击⬇按钮即可跳转对应价格 希望能更快速简单的帮助到您🎁

18 Nov 2026, 12:16 UTC15 viewsread 18 November 2026

😊【地推宝】 @DiTuiBao 🎁 🎁 会员代开 |🎁 电报业务 🤑 能量租赁 |♥ 香烟专卖 🌐 闪连VPN |📱 PikPak下载 娱乐导航 🎁【灰世界】实时新闻推送 🔍【搜Now】全网搜索神器 📱【QQ传媒】一站式免费看片 ❗❗❗❗❗❗❗❗❗❗ 点击⬇按钮即可跳转对应价格 希望能更快速简单的帮助到您🎁

18 Nov 2026, 12:12 UTC84 viewsread 19 November 2026

博信 如意团队:ry7554 恒信 乐乐团队:ll4983 安盛 可爱团队:ka3329 移动 移动团队:yy8752

18 Nov 2026, 00:16 UTC8 viewsread 18 November 2026

😊【地推宝】 @DiTuiBao 🎁 🎁 会员代开 |🎁 电报业务 🤑 能量租赁 |♥ 香烟专卖 🌐 闪连VPN |📱 PikPak下载 娱乐导航 🎁【灰世界】实时新闻推送 🔍【搜Now】全网搜索神器 📱【QQ传媒】一站式免费看片 ❗❗❗❗❗❗❗❗❗❗ 点击⬇按钮即可跳转对应价格 希望能更快速简单的帮助到您🎁

17 Nov 2026, 12:16 UTC19 viewsread 17 November 2026

😊【地推宝】 @DiTuiBao 🎁 🎁 会员代开 |🎁 电报业务 🤑 能量租赁 |♥ 香烟专卖 🌐 闪连VPN |📱 PikPak下载 娱乐导航 🎁【灰世界】实时新闻推送 🔍【搜Now】全网搜索神器 📱【QQ传媒】一站式免费看片 ❗❗❗❗❗❗❗❗❗❗ 点击⬇按钮即可跳转对应价格 希望能更快速简单的帮助到您🎁

17 Nov 2026, 12:10 UTC166 viewsread 19 November 2026

博信 如意团队:ry7554 恒信 乐乐团队:ll4983 安盛 可爱团队:ka3329 移动 移动团队:yy8752

Showing the 12 most recent of 314 posts we hold for @dtbpyq. 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 recorded as deleted after publishing

We recorded 15 posts on @dtbpyq 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
8 August 2026
Most recent seen missing
4 November 2026
Median time before seen missing
7.7 hours
Seen missing in the last 30 days
5

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“dtbpyq” (@dtbpyq), 13,334 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/dtbpyq.

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.