Channel
Tropmaneco🇩🇪Германия
@tropmaneco
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,288subscribers
-31 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001742005371 |
|---|---|
| Type | Channel |
| Username | @tropmaneco |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/tropmaneco |
Topic
Personal blog — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 |
|---|---|---|
| 4 Nov 2026, 09:56 | 2,288 | -2 |
| 1 Nov 2026, 03:17 | 2,290 | -2 |
| 29 Oct 2026, 06:46 | 2,292 | -3 |
| 26 Oct 2026, 13:28 | 2,295 | -1 |
| 23 Oct 2026, 09:06 | 2,296 | -2 |
| 20 Oct 2026, 05:11 | 2,298 | -1 |
| 17 Oct 2026, 05:56 | 2,299 | -2 |
| 14 Oct 2026, 09:21 | 2,301 | -4 |
| 10 Oct 2026, 18:01 | 2,305 | +3 |
| 4 Oct 2026, 21:35 | 2,302 | -5 |
| 25 Sept 2026, 11:41 | 2,307 | +2 |
| 17 Sept 2026, 15:19 | 2,305 | no change |
| 13 Sept 2026, 14:38 | 2,305 | -3 |
| 10 Sept 2026, 00:16 | 2,308 | -1 |
| 4 Sept 2026, 13:38 | 2,309 | -3 |
| 1 Sept 2026, 05:35 | 2,312 | -4 |
| 27 Aug 2026, 00:58 | 2,316 | -2 |
| 24 Aug 2026, 02:42 | 2,318 | -1 |
| 23 Aug 2026, 04:30 | 2,319 | 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.
@doktor_kris · 55,352
Telegram ranks this channel #33 of 51 here — alongside 50 others — read 23 August 2026
@cryptohome7 · 22,861
Telegram ranks this channel #53 of 62 here — alongside 61 others — read 18 September 2026
@mamalapatundel · 32,011
Telegram ranks this channel #53 of 56 here — alongside 55 others — read 5 September 2026
@anyclass_supermama · 55,639
Telegram ranks this channel #74 of 79 here — alongside 78 others — read 24 August 2026
This channel appears in 4 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“Tropmaneco🇩🇪Германия” (@tropmaneco), 2,288 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/tropmaneco.
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.