Telegram RegisterThe public register of Telegram
Telegram profile photo for Dubcy castle

Channel

Dubcy castle

@dubcycastle

On this record: Topic · Growth · Engagement · Posts · Cite this entry

6subscribers

-58 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-1003230492502
TypeChannel
Username@dubcycastle
Created30 November 2025 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live19 November 2026
Measurements held7
Confirmed unchanged6 times, most recently 19 November 2026
On Telegramt.me/dubcycastle

Topic

Hacking & security — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 99% 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

664357 August 2026 — 64 subscribers10 August 2026 — 64 subscribers14 August 2026 — 52 subscribers23 August 2026 — 23 subscribers31 August 2026 — 21 subscribers10 September 2026 — 7 subscribers13 October 2026 — 6 subscribers7 August 202613 October 2026
7 measurements spanning 66 days, net -58. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Oct 2026, 03:276-1
10 Sept 2026, 05:387-14
31 Aug 2026, 10:0321-2
23 Aug 2026, 09:3523-29
14 Aug 2026, 22:3552-12
10 Aug 2026, 03:0164no change
7 Aug 2026, 17:5664first reading

Engagement

3 posts held, back to 30 November 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 3 posts for this entry, the most recent from 30 November 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Nov 2025, 09:52 UTC≈4,470 viewsread 10 August 2026

🏎Rosso Lookup is LIVE! A premium-grade Telegram Lookup Bot ⛏️ 🧛 Ultra-Fast Results 🧛 Secure Transaction System 🎯 Accurate & Up-to-Date Lookups 💳 Crypto-Friendly Payments 📱Telegram lookup bot - username to number & addy ( whole doxx 🔑 Get your keys : rossolookup.astck.io

30 Nov 2025, 09:18 UTC≈4,600 viewsread 10 August 2026
Photo

Old account got banned gonna post new vouches here Regards ~ @dubcy

Showing the 3 most recent of 3 posts we hold for @dubcycastle. 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.

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 13 October 2026 — this entry's latest reading, not the date you are reading this.

“Dubcy castle” (@dubcycastle), 6 subscribers as measured 13 October 2026. Telegram Register, tgregister.com/channel/dubcycastle.

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.