Telegram RegisterThe public register of Telegram
Telegram profile photo for My ♥️

Channel

My ♥️

@malushka_001

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

1,429subscribers

-14 since we began measuring on 29 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001074007085
TypeChannel
Username@malushka_001
CreatedBetween 1 October 2016 and 31 July 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded29 September 2026
Last confirmed live4 November 2026
Measurements held10
Confirmed unchanged2 times, most recently 4 November 2026
On Telegramt.me/malushka_001

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 14 October 2026 and assigned it the closest of 31 fixed categories, at 98% 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

1,4291,4431,43629 September 2026 — 1,443 subscribers29 September 2026 — 1,443 subscribers11 October 2026 — 1,439 subscribers14 October 2026 — 1,437 subscribers17 October 2026 — 1,436 subscribers20 October 2026 — 1,435 subscribers23 October 2026 — 1,433 subscribers26 October 2026 — 1,432 subscribers29 October 2026 — 1,431 subscribers1 November 2026 — 1,429 subscribers29 September 20261 November 2026
10 measurements spanning 34 days, net -14. 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”. The vertical axis spans 1,427–1,445 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Nov 2026, 23:141,429-2
29 Oct 2026, 22:361,431-1
26 Oct 2026, 20:381,432-1
23 Oct 2026, 18:181,433-2
20 Oct 2026, 14:491,435-1
17 Oct 2026, 19:071,436-1
14 Oct 2026, 14:091,437-2
11 Oct 2026, 05:381,439-4
29 Sept 2026, 16:331,443no change
29 Sept 2026, 08:471,443first 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.

SabhiJobs.com 🇮🇳 Latest Govt Jobs
@sabhijobs · 19,184
Telegram ranks this channel #26 of 45 here — alongside 44 others — read 29 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 1 November 2026 — this entry's latest reading, not the date you are reading this.

“My ♥️” (@malushka_001), 1,429 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/malushka_001.

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.