
Channel
اشعار وحید محمدی
@beithayesookhte
On this record: Growth · Engagement · Cite this entry
5,737subscribers
+35 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 | -1001004761179 |
|---|---|
| Type | Channel |
| Username | @beithayesookhte |
| Description | شعر کلاسیک و سبک های مداحی ادمین و راه ارتباطی: @AP_315 کانال هیئت: @rowzaat |
| Created | Between 1 September 2015 and 31 December 2015— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 10 |
| On Telegram | t.me/beithayesookhte |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 11:50 | 5,737 | no change |
| 28 Aug 2026, 07:08 | 5,737 | +7 |
| 25 Aug 2026, 10:52 | 5,730 | +1 |
| 22 Aug 2026, 02:05 | 5,729 | +4 |
| 18 Aug 2026, 21:06 | 5,725 | +9 |
| 15 Aug 2026, 18:28 | 5,716 | +5 |
| 12 Aug 2026, 12:43 | 5,711 | +10 |
| 9 Aug 2026, 22:31 | 5,701 | -2 |
| 6 Aug 2026, 15:46 | 5,703 | +1 |
| 6 Aug 2026, 08:57 | 5,702 | 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“اشعار وحید محمدی” (@beithayesookhte), 5,737 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/beithayesookhte.
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.