Channel
𝐏𝐚𝐫𝐚𝐧𝐨𝐢𝐚•
@Gothicwatch
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,709subscribers
-43 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001548029482 |
|---|---|
| Type | Channel |
| Username | @Gothicwatch |
| Description | 𝖨 𝗅𝗂𝗌𝗍𝖾𝗇 𝗍𝗈 𝗆𝗎𝗌𝗂𝖼 𝖻𝖾𝖼𝖺𝗎𝗌𝖾 𝗆𝗎𝗋𝖽𝖾𝗋 𝗂𝗌𝗇’𝗍 𝖺 𝗀𝗈𝗈𝖽 𝗍𝗁𝗂𝗇𝗀” |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 24 September 2026 |
| Last confirmed live | 24 September 2026 |
| Measurements held | 12 |
| On Telegram | t.me/Gothicwatch |
Topic
Music — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Sept 2026, 16:19 | 1,709 | no change |
| 19 Sept 2026, 16:57 | 1,709 | -4 |
| 15 Sept 2026, 15:41 | 1,713 | -5 |
| 12 Sept 2026, 08:15 | 1,718 | -7 |
| 8 Sept 2026, 10:01 | 1,725 | -3 |
| 3 Sept 2026, 14:01 | 1,728 | -2 |
| 30 Aug 2026, 23:28 | 1,730 | -5 |
| 27 Aug 2026, 21:25 | 1,735 | -1 |
| 24 Aug 2026, 22:59 | 1,736 | -7 |
| 21 Aug 2026, 06:52 | 1,743 | -7 |
| 18 Aug 2026, 01:03 | 1,750 | -2 |
| 14 Aug 2026, 20:15 | 1,752 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@ahnGeme · 108,539
Telegram ranks this channel #1 of 71 here — alongside 70 others — read 14 August 2026
@BullVpnNet · 62,378
Telegram ranks this channel #17 of 28 here — alongside 27 others — read 21 August 2026
@MusiC_OffiCiaal · 37,942
Telegram ranks this channel #27 of 72 here — alongside 71 others — read 31 August 2026
@Dep_MuSiCx · 51,140
Telegram ranks this channel #29 of 79 here — alongside 78 others — read 25 August 2026
@DepMusicam · 33,373
Telegram ranks this channel #32 of 72 here — alongside 71 others — read 4 September 2026
@Music1Play · 33,039
Telegram ranks this channel #44 of 82 here — alongside 81 others — read 4 September 2026
@NabMusicsTel · 52,898
Telegram ranks this channel #68 of 77 here — alongside 76 others — read 24 August 2026
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 24 September 2026 — this entry's latest reading, not the date you are reading this.
“𝐏𝐚𝐫𝐚𝐧𝐨𝐢𝐚•” (@Gothicwatch), 1,709 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/Gothicwatch.
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.