Channel
AbeerBarakat369
@abeerbarakat369
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,881subscribers
+74 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001304506996 |
|---|---|
| Type | Channel |
| Usernames | @abeerbarakat369 @AbeerBarakat369369 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/abeerbarakat369 |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 5 Nov 2026, 07:55 | 2,881 | +2 |
| 4 Nov 2026, 02:25 | 2,879 | +2 |
| 2 Nov 2026, 09:17 | 2,877 | -1 |
| 31 Oct 2026, 22:01 | 2,878 | +5 |
| 30 Oct 2026, 12:16 | 2,873 | +6 |
| 27 Oct 2026, 02:54 | 2,867 | no change |
| 25 Oct 2026, 12:36 | 2,867 | -1 |
| 24 Oct 2026, 06:56 | 2,868 | -2 |
| 22 Oct 2026, 06:57 | 2,870 | no change |
| 21 Oct 2026, 07:16 | 2,870 | +1 |
| 18 Oct 2026, 13:41 | 2,869 | +6 |
| 17 Oct 2026, 18:30 | 2,863 | +1 |
| 14 Oct 2026, 20:57 | 2,862 | no change |
| 12 Oct 2026, 20:37 | 2,862 | +1 |
| 11 Oct 2026, 23:15 | 2,861 | +8 |
| 6 Oct 2026, 06:18 | 2,853 | -2 |
| 5 Oct 2026, 03:39 | 2,855 | -3 |
| 29 Sept 2026, 07:20 | 2,858 | -1 |
| 26 Sept 2026, 01:41 | 2,859 | +9 |
| 17 Sept 2026, 07:57 | 2,850 | 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.
@MaisaralifeMeditations · 20,319
Telegram ranks this channel #3 of 84 here — alongside 83 others — read 28 September 2026
@sultan_wasmi · 31,544
Telegram ranks this channel #11 of 82 here — alongside 81 others — read 21 September 2026
@SmartsWay · 89,966
Telegram ranks this channel #14 of 85 here — alongside 84 others — read 17 August 2026
@rehamalrashidi · 23,314
Telegram ranks this channel #59 of 83 here — alongside 82 others — read 17 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“AbeerBarakat369” (@abeerbarakat369), 2,881 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/abeerbarakat369.
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.