如果查询地址没有查到对方ID,宝子们可以尝试点击查询,输入关键词,比如:料,车,直盘,之内的关键词大概率也可以找到你们想要的资源。 交易务必走担保,不要被骗了,有问题可以多跟我们反馈哦。

Channel
地址库频道
@dizhiku1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
284subscribers
+4 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003695808029 |
|---|---|
| Type | Channel |
| Usernames | @dizhiku @dizhiku1 |
| Created | 2 February 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/dizhiku1 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 13:18 | 284 | no change |
| 19 Sept 2026, 04:41 | 284 | +5 |
| 11 Sept 2026, 23:35 | 279 | -1 |
| 10 Sept 2026, 10:01 | 280 | -5 |
| 25 Aug 2026, 02:45 | 285 | no change |
| 20 Aug 2026, 03:47 | 285 | +1 |
| 18 Aug 2026, 17:45 | 284 | +6 |
| 12 Aug 2026, 08:54 | 278 | no change |
| 12 Aug 2026, 08:32 | 278 | -2 |
| 11 Aug 2026, 20:00 | 280 | no change |
| 11 Aug 2026, 19:48 | 280 | first reading |
Engagement
9 posts held, back to 2 February 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 13 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 48s
- Average length
- 48s
Measured directly from 1 video 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.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.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 2 of the 9 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 2 February 2026 to 13 May 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
我们也很乐意看到你们通过地址库找到好的资源,但是本机器人只提供资源查询,如需交易,请走正规担保,切勿上当受骗。
地址库频道 pinned «私聊机器人发送地址即可查询 @dizhikubot»
跟我们团队有过合作的也可以联系我们,帮忙录入到公共地址库,只有在公共地址库其他人才可以查询到,私人地址库只对你自己显示,其他人看不到
私聊机器人发送地址即可查询 @dizhikubot
意见反馈:@Axe188 @Aliming8
全网最牛逼的找资源机器人!!!可以通过对方的地址流水,找到对方的上下家!!!
这款机器人不同于市场上的任何查U机器人,不止可以查U的流水,也可以查到对方地址的飞机号联系方式
❤1
Channel created
Showing the 9 most recent of 9 posts we hold for @dizhiku1. 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“地址库频道” (@dizhiku1), 284 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/dizhiku1.
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.