Channel
@Khaierin_alaba
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
562subscribers
+14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001285809230 |
|---|---|
| Type | Channel |
| Username | @Khaierin_alaba |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/Khaierin_alaba |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 01:00 | 562 | -1 |
| 3 Sept 2026, 18:38 | 563 | +3 |
| 28 Aug 2026, 11:29 | 560 | +1 |
| 21 Aug 2026, 08:14 | 559 | +2 |
| 15 Aug 2026, 00:45 | 557 | +9 |
| 7 Aug 2026, 03:50 | 548 | no change |
| 6 Aug 2026, 20:16 | 548 | first reading |
6 posts held, back to 11 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
🔸مادر و فرزندی چشم به کمک های شما دارند... بیماران مادر و فرزند یک خانواده که باسوختگی ۴۵درصد که علت آتش سوزی موتور بخاطر شستشو با تینربوده که دربخش icu بیمارستان مطهری بستری می باشند با توجه به اینکه خانواده با درآمد فوق العاده پایین می باشدو دو فرزند دختر خانواده نیز تحت کفالت بهزیستی می باشد توانایی پرداخت هزینه ها رو ندارند. 6104338715777146 6037998246853963 6221061235959840 160120020000009135116013 880…
https://eitaa.com/khaierinalaba/1121 ادامه گزارش تصویری واریزی زوار
واریزی برای زوار
واریزی برای زوار
با هر مبلغی میتوانید در اعزام زوار اباعبدالله علیه السلام شرکت کنید. امسال اعزام #ویژه است چون به نام مبارک امام حسن مجتبی علیه السلام است و قصد دعا در تعجیل فرج صاحب الزمان روحی فداه. پس از هیچ مبلغی دریغ نکنید و خود را سهیم کنید. https://t.me/Khaierin_alaba/110?single https://t.me/Khaierin_alaba/302?single https://t.me/Khaierin_alaba/307?single https://t.me/Khaierin_alaba/1077?single https://t.me/Khaierin_alaba/11…
واریزی جهت سوختگی
Showing the 6 most recent of 6 posts we hold for @Khaierin_alaba. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“خیرین آل عبا” (@Khaierin_alaba), 562 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/Khaierin_alaba.
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.