Channel
حياتنا وولادنا مع دعاء صفوت
@doaasafwat
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,641subscribers
-76 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001082632743 |
|---|---|
| Type | Channel |
| Username | @doaasafwat |
| Created | Between 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/doaasafwat |
Topic
Other / unclassifiable — 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 60% 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 |
|---|---|---|
| 7 Nov 2026, 12:26 | 4,641 | -4 |
| 4 Nov 2026, 07:26 | 4,645 | -3 |
| 1 Nov 2026, 01:38 | 4,648 | -1 |
| 28 Oct 2026, 17:48 | 4,649 | -3 |
| 25 Oct 2026, 20:05 | 4,652 | -4 |
| 22 Oct 2026, 13:31 | 4,656 | -4 |
| 18 Oct 2026, 22:06 | 4,660 | -3 |
| 15 Oct 2026, 12:18 | 4,663 | -2 |
| 12 Oct 2026, 14:41 | 4,665 | -10 |
| 5 Oct 2026, 20:41 | 4,675 | -5 |
| 28 Sept 2026, 19:01 | 4,680 | -10 |
| 16 Sept 2026, 05:39 | 4,690 | -3 |
| 8 Sept 2026, 22:41 | 4,693 | -6 |
| 3 Sept 2026, 19:36 | 4,699 | -3 |
| 2 Sept 2026, 20:15 | 4,702 | no change |
| 31 Aug 2026, 13:43 | 4,702 | -4 |
| 28 Aug 2026, 12:07 | 4,706 | -2 |
| 25 Aug 2026, 09:53 | 4,708 | -2 |
| 22 Aug 2026, 11:58 | 4,710 | -5 |
| 18 Aug 2026, 16:14 | 4,715 | 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.
@Mozkrat4prep · 34,808
Telegram ranks this channel #38 of 81 here — alongside 80 others — read 9 September 2026
@elmoslem_elsaghir · 22,547
Telegram ranks this channel #42 of 88 here — alongside 87 others — read 21 September 2026
@GKWSMZWjhJoyYjE0 · 19,168
Telegram ranks this channel #46 of 79 here — alongside 78 others — read 1 October 2026
@yallanzaker66 · 21,849
Telegram ranks this channel #51 of 72 here — alongside 71 others — read 23 September 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“حياتنا وولادنا مع دعاء صفوت” (@doaasafwat), 4,641 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/doaasafwat.
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.