Telegram RegisterThe public register of Telegram
Telegram profile photo for Радио Азия-Плюс

Channel

Радио Азия-Плюс

@radioasiaplus

Has discussion group

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

2,273subscribers

-38 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001198203176
TypeChannel
Username@radioasiaplus
Created10 January 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded18 September 2026
Last confirmed live18 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/radioasiaplus

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 18 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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

2,2682,3112,289.56 August 2026 — 2,311 subscribers7 August 2026 — 2,310 subscribers10 August 2026 — 2,307 subscribers14 August 2026 — 2,301 subscribers17 August 2026 — 2,296 subscribers20 August 2026 — 2,290 subscribers23 August 2026 — 2,280 subscribers26 August 2026 — 2,276 subscribers29 August 2026 — 2,271 subscribers5 September 2026 — 2,268 subscribers10 September 2026 — 2,269 subscribers14 September 2026 — 2,279 subscribers18 September 2026 — 2,279 subscribers18 September 2026 — 2,273 subscribers2,2736 August 202618 September 2026
14 measurements spanning 43 days, net -38. 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 2,262–2,317 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 22:402,273-6
18 Sept 2026, 00:242,279no change
14 Sept 2026, 05:572,279+10
10 Sept 2026, 08:212,269+1
5 Sept 2026, 01:372,268-3
29 Aug 2026, 19:262,271-5
26 Aug 2026, 17:452,276-4
23 Aug 2026, 15:542,280-10
20 Aug 2026, 07:352,290-6
17 Aug 2026, 12:152,296-5
14 Aug 2026, 03:372,301-6
10 Aug 2026, 21:412,307-3
7 Aug 2026, 16:292,310-1
6 Aug 2026, 22:482,311first 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 8 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.

Азия-Плюс | Все новости Таджикистана и мира
@asiaplus · 69,434
Telegram ranks this channel #6 of 78 here — alongside 77 others — read 20 August 2026
Азия-Плюс TJ
@asiaplustj · 23,155
Telegram ranks this channel #33 of 81 here — alongside 80 others — read 19 September 2026
dushanbepolice 🇹🇯
@dushanbe_police_tj · 50,028
Telegram ranks this channel #55 of 57 here — alongside 56 others — read 25 August 2026
Parviz TV
@ParvisTV · 99,741
Telegram ranks this channel #58 of 59 here — alongside 58 others — read 15 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“Радио Азия-Плюс” (@radioasiaplus), 2,273 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/radioasiaplus.

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.