
Channel
اسموزیس پرستاری
@osmosis_parastari
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,339subscribers
+371 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002069489636 |
|---|---|
| Type | Channel |
| Username | @osmosis_parastari |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 5 September 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/osmosis_parastari |
Topic
Education — 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 51% 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 |
|---|---|---|
| 15 Nov 2026, 11:06 | 4,339 | +55 |
| 10 Nov 2026, 11:50 | 4,284 | -5 |
| 7 Nov 2026, 07:09 | 4,289 | +1 |
| 4 Nov 2026, 11:58 | 4,288 | -1 |
| 1 Nov 2026, 11:57 | 4,289 | +42 |
| 29 Oct 2026, 11:29 | 4,247 | -1 |
| 26 Oct 2026, 18:18 | 4,248 | +48 |
| 23 Oct 2026, 22:09 | 4,200 | -9 |
| 21 Oct 2026, 04:47 | 4,209 | +37 |
| 18 Oct 2026, 02:54 | 4,172 | -5 |
| 15 Oct 2026, 09:49 | 4,177 | +50 |
| 12 Oct 2026, 09:20 | 4,127 | +18 |
| 5 Oct 2026, 17:02 | 4,109 | +43 |
| 27 Sept 2026, 18:15 | 4,066 | +62 |
| 18 Sept 2026, 00:38 | 4,004 | -12 |
| 13 Sept 2026, 10:16 | 4,016 | +30 |
| 9 Sept 2026, 14:21 | 3,986 | -22 |
| 5 Sept 2026, 19:33 | 4,008 | no change |
| 3 Sept 2026, 20:38 | 4,008 | +40 |
| 31 Aug 2026, 01:30 | 3,968 | 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.
@Parastari98B · 40,435
Telegram ranks this channel #31 of 94 here — alongside 93 others — read 31 August 2026
@vial_tadris · 36,489
Telegram ranks this channel #72 of 97 here — alongside 96 others — read 2 September 2026
@karamozigroup1 · 19,830
Telegram ranks this channel #84 of 94 here — alongside 93 others — read 30 September 2026
@daneshe_parastari · 18,947
Telegram ranks this channel #85 of 92 here — alongside 91 others — read 5 October 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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“اسموزیس پرستاری” (@osmosis_parastari), 4,339 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/osmosis_parastari.
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.