Channel
@TDDB_111
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 1 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002109302964 |
|---|---|
| Type | Channel |
| Username | @TDDB_111 |
| Created | 11 March 2024 — measured — dated from the channel’s first post |
| First recorded | 1 September 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/TDDB_111 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 13:14 | 1 | no change |
| 1 Sept 2026, 15:00 | 1 | first reading |
4 posts held, back to 11 March 2024 — 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 4 posts for this entry, the most recent from 22 May 2026. An engagement rate over an empty window would be a number about nothing.
需☹️☹️☹️☹️☹️ 需求类型：招滴滴拿现/卡密核销车🥰🥰🥰 招：【滴滴车】U商拿现/证劵/滴滴/丢包 招：【核销车】: 油卡 E卡 抖币 QB核销 招：【卡码车】一/二道 卡接码接回U车队 料性： 大区精聊 维护时间长，料性安全稳定 优势：双押 /保到/验货回u量大不罚站/全程丝滑 新车可教可扶持，老车量大管饱全程护航单量无忧 对接方式/对接人：@tzdb996 @daishoudaifui
https://t.me/daishoudaifui
业务联系 @tzdb66 https://t.me/daishoudaifui 各种丝滑通道 代收代付 承兑白资换u 高价收u 招话费车 口令车 个码车 卡车 一手直盘 合作联系 @tzdb66
Channel created
Showing the 4 most recent of 4 posts we hold for @TDDB_111. 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.
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.
Named by 8 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“天斗国际一组” (@TDDB_111), 1 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/TDDB_111.
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.