
Channel
آبی
@my_blue_ocean
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,058subscribers
+27 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 | -1001081050578 |
|---|---|
| Type | Channel |
| Username | @my_blue_ocean |
| Description | تركتُ لَك الكثير مِني في أغنية... إِسْمَعني! مقدار زیادی از وجودم را درون آهنگی برایت جا گذاشتهام؛ مرا گوش کن...💙 |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 October 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 11 |
| On Telegram | t.me/my_blue_ocean |
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 8 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Oct 2026, 01:52 | 1,058 | no change |
| 7 Oct 2026, 06:41 | 1,058 | +8 |
| 30 Sept 2026, 12:56 | 1,050 | +3 |
| 15 Sept 2026, 09:39 | 1,047 | +2 |
| 30 Aug 2026, 09:32 | 1,045 | +5 |
| 24 Aug 2026, 01:34 | 1,040 | +3 |
| 20 Aug 2026, 12:35 | 1,037 | +5 |
| 14 Aug 2026, 03:06 | 1,032 | +1 |
| 11 Aug 2026, 01:15 | 1,031 | -1 |
| 8 Aug 2026, 10:24 | 1,032 | +1 |
| 7 Aug 2026, 19:37 | 1,031 | 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.
@MiraTweets · 25,776
Telegram ranks this channel #20 of 48 here — alongside 47 others — read 30 September 2026
@absurdmindsmedia · 30,734
Telegram ranks this channel #21 of 85 here — alongside 84 others — read 6 September 2026
@flowwithmusic · 21,598
Telegram ranks this channel #28 of 93 here — alongside 92 others — read 23 September 2026
@Dreaminng · 47,850
Telegram ranks this channel #43 of 79 here — alongside 78 others — read 26 August 2026
@TimeChay · 55,085
Telegram ranks this channel #56 of 88 here — alongside 87 others — read 25 August 2026
@radio_chehraziii · 62,794
Telegram ranks this channel #76 of 94 here — alongside 93 others — read 22 August 2026
@kafe_0_tanhaii · 58,519
Telegram ranks this channel #78 of 81 here — alongside 80 others — read 22 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 8 October 2026 — this entry's latest reading, not the date you are reading this.
“آبی” (@my_blue_ocean), 1,058 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/my_blue_ocean.
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.