真心永远换不回真心 流浪合作几个月 没钱我给你送人送卡 扶持你 后面你有卡 我给你打 进算 利润全部给你 不说了 心累 5月14日 15w+4.2w 5月15日 8万6 还好13万拉了 不然赔大了 以后所有车队 无压不开工 无压不接人 😁
👍1

Channel
@DDJT10
On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry
27subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002127151909 |
|---|---|
| Type | Channel |
| Username | @DDJT10 |
| Created | Between 1 November 2023 and 5 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 3 times, most recently 18 November 2026 |
| On Telegram | t.me/DDJT10 |
Hacking & security — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Nov 2026, 17:20 | 27 | -1 |
| 18 Oct 2026, 15:09 | 28 | -1 |
| 11 Oct 2026, 16:17 | 29 | -2 |
| 15 Sept 2026, 06:17 | 31 | -2 |
| 11 Aug 2026, 01:16 | 33 | no change |
| 7 Aug 2026, 12:37 | 33 | first reading |
15 posts held, back to 5 April 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 15 posts for this entry, the most recent from 15 May 2024. An engagement rate over an empty window would be a number about nothing.
6 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 50.0% | |
| 🤯 | 2 | 33.3% | |
| 👍 | 1 | 16.7% |
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 15 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 5 April 2024 to 15 May 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
真心永远换不回真心 流浪合作几个月 没钱我给你送人送卡 扶持你 后面你有卡 我给你打 进算 利润全部给你 不说了 心累 5月14日 15w+4.2w 5月15日 8万6 还好13万拉了 不然赔大了 以后所有车队 无压不开工 无压不接人 😁
👍1
支付宝 微信码接回u 上次谁找我来着 0司法 码多来
✅需:一道纯色 专卡/额度卡/取现卡😀😀 ✅ 可以双押保料子, 有卡滴滴滴 !!😀😀 可提供二道卸货 三方 代扣 救火 业务对接 @ddjt9 @DDJT4040
❤1
需:二道卡 精聊2000-10000二道卡 色料1000-10000二道卡 量大,全天24h开车🚗🚗
😀😃😀😃😀😃😀😃😀😃 诚招:贷款卡盘工作室合作,人头卡 贷款户,各种客户配合 点位置顶高价买断,卡费➕开车利润 卡商发财致富的最佳选择 全国车队,上门服务,完美配合 😀😃😀😃😃😃地方地方银行,地方农信,点位置顶,卡费加分红。 诚招:上押操作车队
🤯2
乌鲁木齐 打昆仑 7个点 来车
乌鲁木齐 来个带操作车 点位6 昆仑银行100 押金低于5000勿扰
@laoli667 变更 @ddjt9 大家注意辨别
云南昆明 缺带操作车 点位6 押金5000起 有车私 招全国带操作车队 每天稳定送卡
山东靠谱的带操作车过来 济南最好 华夏100 点位置顶
安徽安庆 安徽可移动车 明天约 贷款户 保操作费 押金低于5000u勿扰 @ddjt9
全国招代操作车队 每天稳定供卡 地区不限 押金5000u起 认准多多 @ddjt9
Showing the 12 most recent of 15 posts we hold for @DDJT10. 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.
@DDJT10 named 3 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“多多支付集团频道” (@DDJT10), 27 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/DDJT10.
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.