Channel
moien! ☁️
@moiien40
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,495subscribers
+71 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001799846363 |
|---|---|
| Type | Channel |
| Username | @moiien40 |
| Created | Between 1 March 2022 and 30 June 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/moiien40 |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 31 Oct 2026, 06:10 | 2,495 | +6 |
| 28 Oct 2026, 10:19 | 2,489 | +3 |
| 25 Oct 2026, 05:15 | 2,486 | -1 |
| 21 Oct 2026, 20:25 | 2,487 | -5 |
| 18 Oct 2026, 05:45 | 2,492 | -3 |
| 15 Oct 2026, 06:10 | 2,495 | +7 |
| 12 Oct 2026, 14:27 | 2,488 | +10 |
| 5 Oct 2026, 14:22 | 2,478 | +5 |
| 27 Sept 2026, 21:41 | 2,473 | +2 |
| 16 Sept 2026, 00:30 | 2,471 | no change |
| 14 Sept 2026, 01:36 | 2,471 | +1 |
| 10 Sept 2026, 08:38 | 2,470 | +1 |
| 5 Sept 2026, 06:38 | 2,469 | -1 |
| 1 Sept 2026, 09:24 | 2,470 | +7 |
| 29 Aug 2026, 19:37 | 2,463 | +3 |
| 27 Aug 2026, 06:17 | 2,460 | -1 |
| 24 Aug 2026, 00:08 | 2,461 | +3 |
| 20 Aug 2026, 13:46 | 2,458 | +10 |
| 17 Aug 2026, 16:38 | 2,448 | +11 |
| 14 Aug 2026, 03:26 | 2,437 | 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.
@dokhati_channel · 20,390
Telegram ranks this channel #21 of 67 here — alongside 66 others — read 26 September 2026
@Morphin_graphy · 19,266
Telegram ranks this channel #22 of 63 here — alongside 62 others — read 2 October 2026
@radiolimoo · 36,275
Telegram ranks this channel #33 of 85 here — alongside 84 others — read 1 September 2026
@Listenwitharad · 34,281
Telegram ranks this channel #51 of 72 here — alongside 71 others — read 2 September 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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“moien! ☁️” (@moiien40), 2,495 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/moiien40.
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.