Telegram RegisterThe public register of Telegram
Telegram profile photo for 发财猫数据-🌈全行业抓取

Channel

发财猫数据-🌈全行业抓取

@dpi106sdk

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

2,142subscribers

-201 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001949733778
TypeChannel
Username@dpi106sdk
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live30 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/dpi106sdk

Growth

2,1422,3432,242.511 August 2026 — 2,343 subscribers11 August 2026 — 2,343 subscribers11 August 2026 — 2,342 subscribers15 August 2026 — 2,289 subscribers17 August 2026 — 2,221 subscribers20 August 2026 — 2,208 subscribers24 August 2026 — 2,192 subscribers26 August 2026 — 2,170 subscribers30 August 2026 — 2,142 subscribers11 August 202630 August 2026
9 measurements spanning 19 days, net -201. 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 2,112–2,373 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 05:522,142-28
26 Aug 2026, 21:282,170-22
24 Aug 2026, 01:152,192-16
20 Aug 2026, 11:162,208-13
17 Aug 2026, 21:262,221-68
15 Aug 2026, 01:082,289-53
11 Aug 2026, 06:362,342-1
11 Aug 2026, 05:152,343no change
11 Aug 2026, 05:022,343first reading

Engagement

20 posts held, back to 17 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
3.69%
avg views ÷ 2,142 subscribers
Avg views / post
79.0
4 posts measured
Reaction rate
2.50%
reactions ÷ views · ER floor
Posts in window
4
of 20 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 2 of 4 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 10 August 2026
Posts held20 (17 July 202610 August 2026)
Views total316
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 05:15 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.

Reaction mix

5 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5100.0%

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

Measured over the 20 most recent posts we hold, published 17 July 2026 to 10 August 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

10 Aug 2026, 08:09 UTC40 views0 reactionsread 11 August 2026
Photo

认准群里置顶的客服号,其他的都是骗子。都别被骗了。。

10 Aug 2026, 07:18 UTC41 viewsread 11 August 2026

唯一客服号,唯一客服号,唯一客服号,其他都是骗子 这个号掉了我会在频道里发通知

7 Aug 2026, 23:41 UTC80 views3 reactionsread 11 August 2026

DPI 依然出数 每天非常的多 在此 说一下 DPI 的原理 说白了就是比库而已 即使你的URL拆包在精准你的库匹配不出来最优质的数据也是白扯 追求回头客才是源动力

3

4 Aug 2026, 06:13 UTC155 viewsread 11 August 2026
Photo

#fc短信还款 短信劫持台子更新如下; 【银行产品】 邮储银行 公积金贷 |中国银行 随心智贷 | 建设银行 建易贷 | 农业银行 网捷贷 | 中信银行 信秒贷 | 徽商银行 徽银e贷 |宁波银行 宁来花 |招商银行 闪电贷 | 南京银行 你好e贷 |光大银行 阳光贷 | 温州银行 温信贷 | 农业银行 乐分易 | 交通银行 惠民贷 | 苏商银行 微商贷 | 宁波银行 白领通 | 江苏银行 消费随e贷 | 【消费金融】 南银法巴消费金融 | 中邮钱包 | 中银消费 | 中信消费 | 平安担保 | 招联金融 | 兴业消费金融 | 海尔消费金融 | 携程金融 | 新网银行 | 北银消费 | 阳光消费 | 马上消费 | 苏银消费 | 尚诚消费金融 |盛银消费金融 |星图金融 |京东金融 |度小满消费金融 |众安贷 |58数科 |金美信金融 【网贷】 洋钱罐 | 小赢卡贷 | 桔多多 | 恒小花 | 羊小咩 | 360 | 安逸花

29 Jul 2026, 12:42 UTC217 viewsread 11 August 2026
Photo

今天晚上 FC 短信 出货 要延迟了 比较晚了 预计 11点 各位稍安勿躁哈

28 Jul 2026, 12:23 UTC216 views1 reactionsread 11 August 2026
Photo

百度关键词: 提单时间:周日晚至周四晚均可提单,T2交付。 实际是:周一到周五工作日每天中午11点之前截止提单,T2交付。也就是周一中午11点之前截止提单,周三中午交付数据。 有提过的词组模型可以工作日T1交付。 选择周日晚到周四晚收单是考虑到极大部分客户都是晚上活跃,白天早上基本没有人上线提单。 提单数量:1000起提,可到地级市 限制:不接黑灰 关键词自填,不懂的自己去问豆包,问ai:“(行业)装修的百度关键词是什么” 他会告诉你答案。 百度关键词量很少,不出量是正常的。 百度关键词是用户个人主动搜索,与往常我们找竞品提数据的逻辑相反。 关键词很贵,不免测,不打钱不提单。不出数想撤单,随时退款。

1

24 Jul 2026, 08:05 UTC242 viewsread 11 August 2026

小程序、公众号、抖音、小红书周五周六不提单,周日来。

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

Citation-graph rank

Citation-graph rank — 1,270,594 of 1,628,927entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“发财猫数据-🌈全行业抓取” (@dpi106sdk), 2,142 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/dpi106sdk.

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.