Channel
@CPlugin
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
58subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001401979832 |
|---|---|
| Type | Channel |
| Username | @CPlugin |
| Created | Between 1 December 2018 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 3 October 2026 |
| On Telegram | t.me/CPlugin |
Technology — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 9 Sept 2026, 04:15 | 58 | +1 |
| 10 Aug 2026, 07:01 | 57 | no change |
| 7 Aug 2026, 20:39 | 57 | first reading |
20 posts held, back to 7 April 2025 — 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 19 July 2026. An engagement rate over an empty window would be a number about nothing.
9 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 77.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 7 | 77.8% | |
| ❤ | 1 | 11.1% | |
| 👍 | 1 | 11.1% |
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 6 of the 20 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 9 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 7 April 2025 to 19 July 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.
PayPal checkout that never leaves you hanging A small change with a real, everyday difference: your PayPal payment links now stay reliable — even if you come back to an invoice hours later. Before, a PayPal checkout link had a short shelf life. Open an invoice, get pulled away, come back later to pay — and the old link could quietly stop working, with no obvious way forward. Now, when you click Pay with PayPal, we…
🚀 PowerShell SDK for MyWebAPI.com is here Manage your trading platform straight from PowerShell. The new MyWebApi module is now on the PowerShell Gallery: Install-Module MyWebApi What's inside • Full REST v2 coverage — every endpoint as an idiomatic cmdlet (Get-… / Invoke-… / Update-…) • Real-time streaming over SignalR — live ticks, trades, margin calls and status • OAuth2 built in — connect once, tokens refresh …
📬 Email delivery reliability improved We found and fixed an issue that could cause invitation emails — like resending a team invite — to fail to send. The fix is live now. If you tried resending an invitation recently and it did not go through, please give it another try — it will work now. Thanks for your patience. We are always working to make the platform more reliable for you.
🚀 .NET SDK — now on NuGet Integrate our trading platform management API into any .NET application in minutes: dotnet add package MyWebApi.Sdk • One generated method per API endpoint — full v2 coverage • Automatic OAuth2 token management: acquire, cache, refresh — zero boilerplate • Real-time streaming over SignalR • Cursor pagination built in • Targets .NET Standard 2.0 and .NET 8 — works from C#, F# and VB Docs …
The new cplugin.com is live We have rebuilt our website from the ground up — same address, brand-new experience: • Faster everywhere — a lean, modern build; pages open in a blink on desktop and mobile. • Products, clarified — every plugin and tool now carries a concise summary, so you can tell in seconds whether it fits your brokerage. • Documentation, reorganized — full navigation across all records, refreshed gui…
🔥1
🚀 New: official TypeScript / JavaScript SDK for the MyWebAPI MT4/MT5 API Build broker integrations in minutes — install one package and you're connected: npm install @mywebapi.com/sdk What you get • Full API coverage — every MT4 and MT5 v2 endpoint, fully typed. • Real-time built in — stream live ticks, trades and margin calls over SignalR from the same client. • Auth on autopilot — OAuth2 tokens are acquired, cac…
🔥1
🔜 MT5 v2 API — coming soon A new v2 REST + real-time API for MetaTrader 5 is on the way — the same clean, modern contract as our MT4 v2. It's currently in staging for early testing; the production rollout will follow. What's coming: • Unified JSON envelope {data, error, meta} — predictable success/error handling; every response is HTTP 200 with errors in the body. • Configuration — read & partially update users, gr…
🔌 Find the 32-bit MT4 methods — right from the main page A handful of MT4 ManagerAPI calls have to run inside a 32-bit process and live on a separate companion host — the x86 sidecar. Until now, the main API page never pointed to it, so it was easy to miss. What's new: • The main API landing page now links straight to the x86 sidecar • A clear breakdown of what it serves — Messaging, Plugins, Batch snapshots, Plugi…
🚀 V2 API is in open beta — the full MT4 surface, end to end We've been rebuilding the API on a faster, cleaner v2 foundation — and it now covers practically the entire MT4 ManagerAPI. Time to put it through its paces. What's in the beta: • Complete MT4 coverage — every practical ManagerAPI method is now a v2 endpoint (just one method can't be expressed over REST by design) • One clean response shape — every call re…
#Toolbox (https://toolbox.cplugin.com) Good morning, everyone. Earlier today we resolved an infrastructure incident that, over the past few days, may have been affecting you as slowness or intermittent app behaviour. The service is fully restored, and we've added safeguards to prevent a repeat. Thanks for bearing with us — and our apologies for the disruption 🙏
#WebAPI https://mywebapi.com We wish you would like the updated design
🔥2
We have updated our infrastructure, some serviced might not be available during period of 17:12 .. 17:26
👍1
Showing the 12 most recent of 20 posts we hold for @CPlugin. 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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“CPlugin news” (@CPlugin), 58 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/CPlugin.
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.