Channel
Oasis
@SolitarySolitude
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,058subscribers
+19 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001692366132 |
|---|---|
| Type | Channel |
| Username | @SolitarySolitude |
| Description | We Drop music here May our Soul Rest in Peace @durov The content published on this channel does not violate Telegram’s Terms of Service or Community Guidelines https://t.me/IncogNoteBot?start=6a3c8q8p68 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 20 September 2026 |
| Last confirmed live | 20 September 2026 |
| Measurements held | 11 |
| On Telegram | t.me/SolitarySolitude |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 20 Sept 2026, 02:32 | 2,058 | no change |
| 17 Sept 2026, 15:19 | 2,058 | -1 |
| 13 Sept 2026, 04:20 | 2,059 | -1 |
| 9 Sept 2026, 06:38 | 2,060 | -4 |
| 3 Sept 2026, 16:22 | 2,064 | -4 |
| 31 Aug 2026, 00:08 | 2,068 | +10 |
| 24 Aug 2026, 12:44 | 2,058 | +3 |
| 20 Aug 2026, 14:26 | 2,055 | +6 |
| 18 Aug 2026, 00:55 | 2,049 | +13 |
| 15 Aug 2026, 10:08 | 2,036 | -3 |
| 14 Aug 2026, 11:45 | 2,039 | 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.
@AAKLAB · 114,070
Telegram ranks this channel #10 of 74 here — alongside 73 others — read 14 August 2026
@arajifezehnegorbe · 22,728
Telegram ranks this channel #15 of 68 here — alongside 67 others — read 20 September 2026
@usuk1 · 47,527
Telegram ranks this channel #50 of 72 here — alongside 71 others — read 27 August 2026
@club27rock · 95,996
Telegram ranks this channel #56 of 78 here — alongside 77 others — read 21 August 2026
@drbehzadchavooshi · 54,820
Telegram ranks this channel #65 of 78 here — alongside 77 others — read 15 September 2026
This channel appears in 5 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 20 September 2026 — this entry's latest reading, not the date you are reading this.
“Oasis” (@SolitarySolitude), 2,058 subscribers as measured 20 September 2026. Telegram Register, tgregister.com/channel/SolitarySolitude.
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.