Channel
@WildTrades
On this record: Topic · Growth · Engagement · Posts · Cite this entry
113subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002740244793 |
|---|---|
| Type | Channel |
| Username | @WildTrades |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 10 October 2026 |
| On Telegram | t.me/WildTrades |
Marketing & affiliate — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Sept 2026, 11:54 | 113 | +2 |
| 8 Sept 2026, 10:19 | 111 | +1 |
| 16 Aug 2026, 15:55 | 110 | -2 |
| 9 Aug 2026, 06:45 | 112 | no change |
| 7 Aug 2026, 19:18 | 112 | first reading |
20 posts held, back to 21 July 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 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
🇧🇩 Bangladesh (BDT) – P2P Traders Wanted 🇧🇩 Methods: bKash, Nagad Limits: 300–30,000 BDT per tx Settlement: T+0 Looking for razor-sharp P2P operators to push high-volume BDT flows via bKash and Nagad. If you can move 30K BDT per deal without a hitch - let’s talk. DM @PayPortPartnersBot with: ➡️ In/out %, fixed fees & settle fee + cap ✏️ Tx limit 💱 Daily volume (in/out) ✏️ Settlement T+0 💵 Payout currency & rails ✏…
🇺🇿 Uzbekistan High-Risk Streams — Traders Wanted! 🇺🇿 Top-up fee: 3% Withdrawal fee: 1% We’re calling on sharp players working any routes: banks 🏦, e-wallets 💳, P2P 🔄, R2C 📈, C2C 🤝. High-risk flows are the game — and we’re in it for speed and precision. __ Drop your details straight: ➡️ Percentage & fixed fees (in/out/settle) + cap ➡️ Per-transaction limit ➡️ Daily volume (in/out) ➡️ Settlement: T+0 or T+1 ➡️ Payout…
🇰🇷 South Korea High-Risk Streams — Join the Fast Lane! ⚡ Top-up fee: 3% Withdrawal fee: 1% ________ Looking for sharp, driven traders ready to dominate high-risk flows across all channels banks 🏦, e-wallets 💳, P2P 🔄, R2C 📈, C2C 🤝. If speed, precision, and bold moves are your style, we want you on board! Show us your edge: ➡️ Percentages & fixed fees (in/out/settle) + cap ➡️ Max per-transaction limit ➡️ Daily volume…
🇧🇯 Benin (XOF) – P2P Traders Wanted 🇧🇯 Methods: MTN, Moov, Celtiis, Cash Limits: 200–2,000,000 XOF per tx Settlement: T+0 Looking for razor-sharp P2P operators to push high-volume XOF flows via MTN, Moov, Celtiis, and Cash methods. If you can move 2M XOF per deal without a hitch—let's talk. DM @PayPortPartnersBot with: ➡️ In/out %, fixed fees & settle fee + cap ✏️ Tx limit 💱 Daily volume (in/out) ✏️ Settlement T…
🇯🇴 Jordan (JOD) – P2P Traders Wanted 🇯🇴 Methods: CliQ, Orange Money Limits: 1 JOD – 4,000 USD per tx Settlement: T+0 Looking for razor-sharp P2P operators to push high-volume JOD flows via CliQ and Orange Money. If you can move 4K USD equivalent per deal without a hitch—let's talk. DM @PayPortPartnersBot with: ➡️ In/out %, fixed fees & settle fee + cap ✏️ Tx limit 💱 Daily volume (in/out) ✏️ Settlement T+0 💵 Payou…
🇧🇭 Bahrain (BHD) – P2P Traders Wanted 🇧🇭 Method: BenefitPay IPS Limits: 1–3,000 BHD per tx Settlement: T+0 Looking for razor-sharp P2P operators to push high-volume BHD flows via BenefitPay national instant payment system. If you can move 3K BHD per deal without a hitch—let's talk. DM @PayPortPartnersBot with: ➡️ In/out %, fixed fees & settle fee + cap ✏️ Tx limit 💱 Daily volume (in/out) ✏️ Settlement T+0 💵 Payou…
🇮🇶 Iraq (IQD) – P2P Traders Wanted 🇮🇶 Methods: FIB, Zeincash Limits: 2,500–50,000 IQD per tx Settlement: T+0 Looking for razor-sharp P2P operators to push high-volume IQD flows via FIB and Zeincash. If you can move 50K IQD per deal without a hitch—let's talk. DM @PayPortPartnersBot with: ➡️ In/out %, fixed fees & settle fee + cap ✏️ Tx limit 💱 Daily volume (in/out) ✏️ Settlement T+0 💵 Payout currency & rails ✏️ S…
🇰🇿 Kazakhstan — urgent search for high-risk flow traders! Top-up fee — 3%, withdrawal fee — 1%. We operate via banks, any wallets, P2P, R2C, C2C — if you work fast and efficiently, join us! Send your details immediately: ➡️ % / fixed fees for in, out, settle + cap ✏️ Per-transaction limit 💱 Daily volume (in/out) ✏️ Settlement — T+0 or T+1 💵 Payout currency and payment route ✏️ SLA, conversion rate 🗓 Actual start d…
🇵🇰 Seeking Pakistani Merchants for P2P & P2C Partnerships We’re launching a seamless high-risk payment corridor in PKR with ultra-competitive terms: Transaction limits: 2,000–500,000 PKR for both P2P and P2C __ Balances held in USDT (TRC-20) for P2P and PKR for P2C __ Settlement in USDT (TRC-20) with fixed fees—no volume surprises __ Lightning-fast settlements: T+0 payouts __ Rates pegged to Binance P2P for transpar…
🇧🇩 Bangladesh (BDT) – P2P Traders Wanted 🇧🇩 Methods: bKash, Nagad Limits: 300–30,000 BDT per tx Settlement: T+0 Looking for razor-sharp P2P operators to push high-volume BDT flows via bKash and Nagad. If you can move 30K BDT per deal without a hitch - let’s talk. DM @PayPortPartnersBot with: ➡️ In/out %, fixed fees & settle fee + cap ✏️ Tx limit 💱 Daily volume (in/out) ✏️ Settlement T+0 💵 Payout currency & rails ✏…
🇺🇿 Uzbekistan High-Risk Streams — Traders Wanted! 🇺🇿 Top-up fee: 3% Withdrawal fee: 1% We’re calling on sharp players working any routes: banks 🏦, e-wallets 💳, P2P 🔄, R2C 📈, C2C 🤝. High-risk flows are the game — and we’re in it for speed and precision. __ Drop your details straight: ➡️ Percentage & fixed fees (in/out/settle) + cap ➡️ Per-transaction limit ➡️ Daily volume (in/out) ➡️ Settlement: T+0 or T+1 ➡️ Payout…
🇰🇷 South Korea High-Risk Streams — Join the Fast Lane! ⚡ Top-up fee: 3% Withdrawal fee: 1% ________ Looking for sharp, driven traders ready to dominate high-risk flows across all channels banks 🏦, e-wallets 💳, P2P 🔄, R2C 📈, C2C 🤝. If speed, precision, and bold moves are your style, we want you on board! Show us your edge: ➡️ Percentages & fixed fees (in/out/settle) + cap ➡️ Max per-transaction limit ➡️ Daily volume…
Showing the 12 most recent of 20 posts we hold for @WildTrades. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Wild Trades Highrisk” (@WildTrades), 113 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/WildTrades.
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.