Channel
Osho English discourses all
@oshoenglishdiscources
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,013subscribers
+270 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001304886823 |
|---|---|
| Type | Channel |
| Username | @oshoenglishdiscources |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/oshoenglishdiscources |
Topic
Religion — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 |
|---|---|---|
| 3 Nov 2026, 02:46 | 5,013 | +4 |
| 31 Oct 2026, 02:19 | 5,009 | +5 |
| 28 Oct 2026, 01:30 | 5,004 | +3 |
| 25 Oct 2026, 00:46 | 5,001 | +18 |
| 22 Oct 2026, 07:21 | 4,983 | +7 |
| 18 Oct 2026, 21:28 | 4,976 | +10 |
| 16 Oct 2026, 01:18 | 4,966 | +7 |
| 12 Oct 2026, 17:31 | 4,959 | +19 |
| 5 Oct 2026, 23:02 | 4,940 | +13 |
| 28 Sept 2026, 07:37 | 4,927 | +78 |
| 15 Sept 2026, 17:20 | 4,849 | +7 |
| 12 Sept 2026, 10:38 | 4,842 | +31 |
| 8 Sept 2026, 05:02 | 4,811 | +23 |
| 2 Sept 2026, 17:06 | 4,788 | +3 |
| 2 Sept 2026, 12:27 | 4,785 | no change |
| 30 Aug 2026, 19:08 | 4,785 | +3 |
| 28 Aug 2026, 02:35 | 4,782 | +15 |
| 24 Aug 2026, 17:37 | 4,767 | +10 |
| 21 Aug 2026, 06:52 | 4,757 | +7 |
| 18 Aug 2026, 04:42 | 4,750 | 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.
@ashtavakra046 · 47,259
Telegram ranks this channel #3 of 48 here — alongside 47 others — read 19 September 2026
@AudiobooksArchive · 130,915
Telegram ranks this channel #55 of 61 here — alongside 60 others — read 13 August 2026
@onlinetnpsccoaching · 28,787
Telegram ranks this channel #66 of 77 here — alongside 76 others — read 12 September 2026
This channel appears in 3 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Osho English discourses all” (@oshoenglishdiscources), 5,013 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/oshoenglishdiscources.
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.