Channel
@jdmtptm
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
10,051subscribers
+1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003682827850 |
|---|---|
| Type | Channel |
| Username | @jdmtptm |
| Description | 柬埔寨博彩中小额 盘口直营放料群 |
| Created | 6 August 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 4 times, most recently 12 August 2026 |
| On Telegram | t.me/jdmtptm |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 12 August 2026 and assigned it the closest of 31 fixed categories, at 79% 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 why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
2.7 average views per post against 10,051 subscribers — an engagement rate of 0.026%. Across the 1,871 registered channels in the same cohort — 10,003–31,611 subscribers, posting mainly in Chinese — the middle half sit between 1.94% and 11.5%, with a median of 4.82%.
| Window | 30 days (13 July 2026 – 12 August 2026) |
|---|---|
| Posts measured | 12 of 13 published in the window (12 exact, 0 rounded by Telegram) |
| Views totalled | 32 |
| Mature posts only | 0.026% over 8 posts read at least 24h after publication |
| Subscribers | 10,051 measured 9 August 2026 |
| Cohort | b10000:zho · 1,871 channels · p10 0.566% · p25 1.94% · p50 4.82% · p75 11.5% · p90 24.9% |
| Position in cohort | 0.535th percentile · 1/200 the cohort median |
| Uncertainty | ±0% of the figure, from Telegram’s rounding |
| Post language | Chinese · 100.0%of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal.A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_low, last confirmed 12 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 20:35 | 10,051 | +1 |
| 9 Aug 2026, 10:00 | 10,050 | first reading |
13 posts held, back to 6 August 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 8 pagesof Telegram’s post history, 20 posts per page.
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 1 of 12 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 13 (6 August 2026 – 11 August 2026) |
| Views total | 32 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 14:33 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.
Lifetime counters from Telegram’s own channel header, read 12 August 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.
Measured directly from 2 videos 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.
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 1 of the 13 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 6 August 2026 to 11 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.
✅ 卡密回收项目，通过支付宝，闲鱼app，拿京东E卡，话费卡帮BC平台核销，简单讲就是，你从我们这里低价买充值卡密，到支付宝上回收赚差价。 ✅ 比如京东E卡面值300元的充值卡，支付宝和闲鱼回收价格279元，我这里拿货价200元。到支付宝或闲鱼回收可赚79元，闲鱼一个号每天可回收20张，20×79=1580元。 ✅ 卡券由官方回收，无需等待他人购买，输入卡号卡密后约2分钟即可成功回收，官方会把款项直接打到你的支付宝。
怎么兑换 ⬇️⬇️⬇️ 🔘闲鱼省心卖➖卖卡劵➖话费充值卡➖面值300➖填写卡号密码➖提交➖等待质检➖完成收款 🔘京东➖首页搜索拍拍回收➖70+品类➖虚拟卡券➖卖卡劵➖话费充值➖移动充值卡➖选择面值300➖输入卡号卡密后提交 🔘微信方法1:➖微信公众号➖搜索人人销卡➖关注公众号➖点我要卖卡➖话费充值卡➖面值300➖填写卡号密码➖提交➖等待收款 🔘微信方法2:➖微信小程序➖搜【猫卡回收】【财回收】【淘淘收】【抖抖收】自行选择➖点我要卖卡➖填写卡密➖提交➖等待收款 🔘支付宝➖首页上行搜索➖京e收卡➖批量或单卡提交➖等待收款 #京东E卡 #跑分 #项目 #网赚 #灰产 #0风险高回报 🛳平台为24小时自助下单⛴ 自助做单网站👇👇👇 http://www.yyl999.top/ 🧐🧐🧐🧐🧐@JD66990 双向客服✈️ @JD66990_bot
问题汇总（没有做过的朋友请从头看到尾）： 1、卡从哪来？ 是来自于博彩平台的玩家以充值卡密的方式来平台充值玩菠菜项目和进行所谓的上分，和其他的一些要洗Q的老板，安全大于天。其次，只要市场有洗Q需求，货是一直有的。 玩家充值进菠菜公司的卡密，因为卡数量太多。变现不了这么多卡。外包找专业团队来帮忙回收。因为一个账号一天只能销5张卡（5000元）。所以需要大量人手来操作以此达到变现的目的 2、为什么这么便宜？ 因为菠菜公司变现也是需要折30-45个点。 你要知道没有任何一家菠菜公司是自己设立团队来帮忙洗钱！加上现在银行卡风控严重。所以用充值卡是最好用的方法。 3、为什么要在TG卖卡不去其他明面上的平台出售？ 如果可以暴露身份肆意在国内大流量媒体平台公开项目，那还需要博彩公司找我们这么辛苦的洗卡变现么。 4、对你们来说有没有风险？ 单日1W以下的量0风险。我自己团队和合作的工作室回收量过于庞大，个人做回收额度不大不会被监管，所…
🌐在【微信】里搜索【财回收】小程序，回收京东E卡 卡密教程 🌐京东E卡质检时间1小时内到账 🌐建议使用微信小程序，搜财回收平台，质检30分钟内到账。 🌐以上有任何不懂的问题 随时咨询客服
怎么兑换 ⬇️⬇️⬇️ 🔘闲鱼省心卖➖卖卡劵➖话费充值卡➖面值300➖填写卡号密码➖提交➖等待质检➖完成收款 🔘京东➖首页搜索拍拍回收➖70+品类➖虚拟卡券➖卖卡劵➖话费充值➖移动充值卡➖选择面值300➖输入卡号卡密后提交 🔘微信方法1:➖微信公众号➖搜索人人销卡➖关注公众号➖点我要卖卡➖话费充值卡➖面值300➖填写卡号密码➖提交➖等待收款 🔘微信方法2:➖微信小程序➖搜【猫卡回收】【财回收】【淘淘收】【抖抖收】自行选择➖点我要卖卡➖填写卡密➖提交➖等待收款 🔘支付宝➖首页上行搜索➖京e收卡➖批量或单卡提交➖等待收款 #京东E卡 #跑分 #项目 #网赚 #灰产 #0风险高回报 🛳平台为24小时自助下单⛴ 自助做单网站👇👇👇 http://www.yyl999.top/ 🧐🧐🧐🧐🧐@JD66990 双向客服✈️ @JD66990_bot
✅ 卡密回收项目，通过支付宝，闲鱼app，拿京东E卡，话费卡帮BC平台核销，简单讲就是，你从我们这里低价买充值卡密，到支付宝上回收赚差价。 ✅ 比如京东E卡面值300元的充值卡，支付宝和闲鱼回收价格279元，我这里拿货价200元。到支付宝或闲鱼回收可赚79元，闲鱼一个号每天可回收20张，20×79=1580元。 ✅ 卡券由官方回收，无需等待他人购买，输入卡号卡密后约2分钟即可成功回收，官方会把款项直接打到你的支付宝。
问题汇总（没有做过的朋友请从头看到尾）： 1、卡从哪来？ 是来自于博彩平台的玩家以充值卡密的方式来平台充值玩菠菜项目和进行所谓的上分，和其他的一些要洗Q的老板，安全大于天。其次，只要市场有洗Q需求，货是一直有的。 玩家充值进菠菜公司的卡密，因为卡数量太多。变现不了这么多卡。外包找专业团队来帮忙回收。因为一个账号一天只能销5张卡（5000元）。所以需要大量人手来操作以此达到变现的目的 2、为什么这么便宜？ 因为菠菜公司变现也是需要折30-45个点。 你要知道没有任何一家菠菜公司是自己设立团队来帮忙洗钱！加上现在银行卡风控严重。所以用充值卡是最好用的方法。 3、为什么要在TG卖卡不去其他明面上的平台出售？ 如果可以暴露身份肆意在国内大流量媒体平台公开项目，那还需要博彩公司找我们这么辛苦的洗卡变现么。 4、对你们来说有没有风险？ 单日1W以下的量0风险。我自己团队和合作的工作室回收量过于庞大，个人做回收额度不大不会被监管，所…
怎么兑换 ⬇️⬇️⬇️ 🔘闲鱼省心卖➖卖卡劵➖话费充值卡➖面值300➖填写卡号密码➖提交➖等待质检➖完成收款 🔘京东➖首页搜索拍拍回收➖70+品类➖虚拟卡券➖卖卡劵➖话费充值➖移动充值卡➖选择面值300➖输入卡号卡密后提交 🔘微信方法1:➖微信公众号➖搜索人人销卡➖关注公众号➖点我要卖卡➖话费充值卡➖面值300➖填写卡号密码➖提交➖等待收款 🔘微信方法2:➖微信小程序➖搜【猫卡回收】【财回收】【淘淘收】【抖抖收】自行选择➖点我要卖卡➖填写卡密➖提交➖等待收款 🔘支付宝➖首页上行搜索➖京e收卡➖批量或单卡提交➖等待收款 #京东E卡 #跑分 #项目 #网赚 #灰产 #0风险高回报 🛳平台为24小时自助下单⛴ 自助做单网站👇👇👇 http://www.yyl999.top/ 🧐🧐🧐🧐🧐@JD66990
❤1
🌐在【微信】里搜索【财回收】小程序，回收京东E卡 卡密教程 🌐京东E卡质检时间1小时内到账 🌐建议使用微信小程序，搜财回收平台，质检30分钟内到账。 🌐以上有任何不懂的问题 随时咨询客服
✅ 卡密回收项目，通过支付宝，闲鱼app，拿京东E卡，话费卡帮BC平台核销，简单讲就是，你从我们这里低价买充值卡密，到支付宝上回收赚差价。 ✅ 比如京东E卡面值300元的充值卡，支付宝和闲鱼回收价格279元，我这里拿货价200元。到支付宝或闲鱼回收可赚79元，闲鱼一个号每天可回收20张，20×79=1580元。 ✅ 卡券由官方回收，无需等待他人购买，输入卡号卡密后约2分钟即可成功回收，官方会把款项直接打到你的支付宝。
问题汇总（没有做过的朋友请从头看到尾）： 1、卡从哪来？ 是来自于博彩平台的玩家以充值卡密的方式来平台充值玩菠菜项目和进行所谓的上分，和其他的一些要洗Q的老板，安全大于天。其次，只要市场有洗Q需求，货是一直有的。 玩家充值进菠菜公司的卡密，因为卡数量太多。变现不了这么多卡。外包找专业团队来帮忙回收。因为一个账号一天只能销5张卡（5000元）。所以需要大量人手来操作以此达到变现的目的 2、为什么这么便宜？ 因为菠菜公司变现也是需要折30-45个点。 你要知道没有任何一家菠菜公司是自己设立团队来帮忙洗钱！加上现在银行卡风控严重。所以用充值卡是最好用的方法。 3、为什么要在TG卖卡不去其他明面上的平台出售？ 如果可以暴露身份肆意在国内大流量媒体平台公开项目，那还需要博彩公司找我们这么辛苦的洗卡变现么。 4、对你们来说有没有风险？ 单日1W以下的量0风险。我自己团队和合作的工作室回收量过于庞大，个人做回收额度不大不会被监管，所…
1
Showing the 12 most recent of 13 posts we hold for @jdmtptm. 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 — 416,755 of 1,151,006entries 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.
Named by 13 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“小额洗资京东E卡话费卡充值卡24h自助公群” (@jdmtptm), 10,051 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/jdmtptm.
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.