@Tortue_ninja ⚠️ SCAMMER ⚠️ scam 40€
Channel
PROOF @RDPetVPS
@RDPetVPSproof
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
55subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001774587654 |
|---|---|
| Type | Channel |
| Username | @RDPetVPSproof |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 6 times, most recently 10 November 2026 |
| On Telegram | t.me/RDPetVPSproof |
Topic
Other / unclassifiable — 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 96% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 14:38 | 55 | -2 |
| 8 Sept 2026, 03:39 | 57 | -1 |
| 21 Aug 2026, 16:59 | 58 | +1 |
| 14 Aug 2026, 19:49 | 57 | -1 |
| 10 Aug 2026, 06:01 | 58 | no change |
| 7 Aug 2026, 17:16 | 58 | first reading |
Engagement
16 posts held, back to 9 May 2023 — 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 16 posts for this entry, the most recent from 9 March 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
@shopsupportof SCAM 🚨 ENVOIE VIRUS + SCAM
PLESK: 1 mois 8 2 mois 14 3 mois 18 RDP 64gb 12vcpu / (gtx inclu) 32gb 8vcpu 16gb 4vcpu 8gb 2vcpu DM @FRENCHCRACKER Je Send First
@MP4099V2 gros scammeurs de merde ⚠️⚠️🚫
TOOLS GRATUIT - Sender SMS - SMTP CRACKER - SUPER U CONFIG - Cheat fortnite - Carrefour config lien: t.me/CRACKING_T00LS
Sender SMS 3K/num onoff Lien: t.me/CRACKING_T00LS
@Sentrance ✅ Validé 100% legit pour vos RDP & PLESK passer qque par lui c un bon en plus wAllah
Qui a un num vs cc ou rdp ! Dm @RDPetPLESK
pour vos plesk & RDP passez que pars @Sentrance il les fait a 6€ et il envoie en premier 0 scam ✅
🍀 SELL RDP/VPS/PLESK 🍀 Me dm: @RDPetPLESK ⚡️ Je send first ⚡️ Full proof ici: @RDPetVPSproof
🍀 SELL RDP/VPS/PLESK 🍀 🐝 PAS CHÈRE 🐝 ⚡️ Je send first ⚡️ 🌼 RAPIDE EFFICACE 🌼 WINDOWS 11 DISPO Me dm: @RDPetPLESK PAYMENT : PSF/BTC/ TRANSCASH 32gb 12vcpu 25€ / 3 MOIS 16gb 4vcpu 10€ / 3 MOIS 8gb 2vcpu 6€ / 3 MOIS Full proof ici: @RDPetVPSproof
🍀 SELL RDP & PLESK 🍀 ⚡️ Je send first ⚡️ RDP 64gb 12vcpu 25€ / 3 mois (gtx inclu ) 32gb 8vcpu 15€ / 3 mois 16gb 4vcpu 10€ / 3 mois 8gb 2vcpu 8€ / 3 mois PLESK 20€ / 3 mois 10 NDD Me dm: @RDPetPLESK ⚡️ Je send first ⚡️ Full proof ici: @RDPetVPSproof
Showing the 12 most recent of 16 posts we hold for @RDPetVPSproof. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Handles this channel named that no longer answer
- Dead references
- 5
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 5
- vacant every time we have ever looked
@RDPetVPSproof named 5 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 7 posts, 11 August 2026 – 11 August 2026
named in 2 posts, 11 August 2026 – 11 August 2026
named in 2 posts, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
Cite this entry
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 October 2026 — this entry's latest reading, not the date you are reading this.
“PROOF @RDPetVPS” (@RDPetVPSproof), 55 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/RDPetVPSproof.
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.