Channel
@rdpguard
On this record: Topic · Growth · Engagement · Posts · Cite this entry
18subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002190600512 |
|---|---|
| Type | Channel |
| Username | @rdpguard |
| Created | 21 June 2024 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/rdpguard |
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 3 Oct 2026, 10:16 | 18 | +2 |
| 9 Sept 2026, 01:57 | 16 | +1 |
| 16 Aug 2026, 07:04 | 15 | +1 |
| 12 Aug 2026, 00:30 | 14 | no change |
| 7 Aug 2026, 23:12 | 14 | first reading |
5 posts held, back to 21 June 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 5 posts for this entry, the most recent from 11 May 2026. An engagement rate over an empty window would be a number about nothing.
RdpGuard Version 10.2.1 Released - New Geo-IP port scope settings: block or allow traffic only on selected ports - Improved HTTP and RD Web detection with better handling of X-Forwarded-For - Added Client IP fallback for HTTP and RD Web engines - Faster log-based detection engines, especially HTTP protection - Improved MailEnable, OpenSSH, and Microsoft Exchange detection engines - User interface improvements …
RdpGuard Version 9.9.9 Released - Added support for E-MailRelay SMTP Server - New logging settings - CLI improvements and bug-fixes - Improved support for dark theme - Varios internal improvements and bug-fixes https://rdpguard.com/download.aspx
RdpGuard Version 9.9.7 Released - Improved support for MS VPN (including Microsoft AlwaysOn VPN Server) - Improved support for FileZilla Server (SSH/SFTP) - New Geo-IP entries: Starlink, VPN, and hosting providers - New option to exclude VPN networks and Tor exit nodes in Geo-IP Allow mode - New option to exclude data center networks in Geo-IP Allow mode - Various UI improvements and bug fixes - Other interna…
RdpGuard Version 9.7.9 Released - Added support for the X-Forwarded-For field for the HTTP engine - Bug-fixes for the Send Telegram Message Custom Actions task - CLI improvements and bug-fixes - Geo-IP improvements and bug-fixes - User interface improvements and bug-fixes https://rdpguard.com/download.aspx
Channel created
Showing the 5 most recent of 5 posts we hold for @rdpguard. 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“RdpGuard” (@rdpguard), 18 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/rdpguard.
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.