Telegram RegisterThe public register of Telegram
Telegram profile photo for اخبار الجامعات ابن النجف

Channel

اخبار الجامعات ابن النجف

@O4_78

On this record: Topic · Observations · Growth · Engagement · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Cite this entry

20,824subscribers

-250,887 since we began measuring on 22 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002132124836
TypeChannel
Username@O4_78
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded22 August 2026
Last confirmed live8 November 2026
Measurements held48
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/O4_78

Topic

Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 23 August 2026 and assigned it the closest of 31 fixed categories, at 71% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Views per post sit far above this size band

63,800 average views per post against 21,602 subscribers — an engagement rate of 295.4%. Across the 4,836 registered channels in the same cohort — 10,004–31,619 subscribers, posting mainly in Arabic — the middle half sit between 2.98% and 14.2%, with a median of 7.18%.

What this was computed from
Window30 days (6 October 2026 – 5 November 2026)
Posts measured24 of 24 published in the window (0 exact, 24 rounded by Telegram)
Views totalled1,531,480
Mature posts only379.0% over 15 posts read at least 24h after publication
Subscribers21,602 measured 4 November 2026
Cohortb10000:ara · 4,836 channels · p10 1.05% · p25 2.98% · p50 7.18% · p75 14.2% · p90 25.0%
Position in cohort99.979th percentile · 41.1× the cohort median
Uncertainty±0.135% of the figure, from Telegram’s rounding
Post languageArabic · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the key err_high, last confirmed 5 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Growth

20,634541,660281,14722 August 2026 — 271,711 subscribers22 August 2026 — 271,711 subscribers24 August 2026 — 271,520 subscribers25 August 2026 — 271,586 subscribers26 August 2026 — 328,179 subscribers27 August 2026 — 332,606 subscribers28 August 2026 — 330,878 subscribers29 August 2026 — 329,240 subscribers30 August 2026 — 327,001 subscribers31 August 2026 — 325,657 subscribers1 September 2026 — 320,517 subscribers1 September 2026 — 319,166 subscribers3 September 2026 — 317,397 subscribers5 September 2026 — 313,645 subscribers8 September 2026 — 307,769 subscribers11 September 2026 — 304,469 subscribers13 September 2026 — 303,820 subscribers14 September 2026 — 313,126 subscribers16 September 2026 — 321,625 subscribers18 September 2026 — 376,855 subscribers25 September 2026 — 384,475 subscribers4 October 2026 — 401,003 subscribers8 October 2026 — 419,250 subscribers12 October 2026 — 541,660 subscribers14 October 2026 — 20,634 subscribers15 October 2026 — 21,911 subscribers16 October 2026 — 21,879 subscribers17 October 2026 — 21,865 subscribers18 October 2026 — 21,847 subscribers19 October 2026 — 21,840 subscribers20 October 2026 — 21,813 subscribers21 October 2026 — 21,792 subscribers23 October 2026 — 21,755 subscribers24 October 2026 — 21,740 subscribers25 October 2026 — 21,728 subscribers27 October 2026 — 21,709 subscribers28 October 2026 — 21,702 subscribers29 October 2026 — 21,679 subscribers30 October 2026 — 21,659 subscribers31 October 2026 — 21,643 subscribers1 November 2026 — 21,637 subscribers2 November 2026 — 21,625 subscribers3 November 2026 — 21,619 subscribers4 November 2026 — 21,602 subscribers5 November 2026 — 21,593 subscribers6 November 2026 — 21,578 subscribers7 November 2026 — 21,575 subscribers8 November 2026 — 20,824 subscribers20,82422 August 20268 November 2026
48 measurements spanning 78 days, net -250,887. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”.
Measurement log — every subscribers count we have recorded, most recent 20 of 48
Measured (UTC)SubscribersChange
8 Nov 2026, 15:5720,824-751
7 Nov 2026, 12:2621,575-3
6 Nov 2026, 15:5921,578-15
5 Nov 2026, 17:1921,593-9
4 Nov 2026, 16:5521,602-17
3 Nov 2026, 14:2021,619-6
2 Nov 2026, 16:4521,625-12
1 Nov 2026, 19:3121,637-6
31 Oct 2026, 16:2721,643-16
30 Oct 2026, 13:3821,659-20
29 Oct 2026, 10:1221,679-23
28 Oct 2026, 12:2021,702-7
27 Oct 2026, 08:4521,709-19
25 Oct 2026, 04:1621,728-12
24 Oct 2026, 02:1521,740-15
23 Oct 2026, 02:4921,755-37
21 Oct 2026, 23:0621,792-21
20 Oct 2026, 15:0921,813-27
19 Oct 2026, 17:0621,840-7
18 Oct 2026, 19:0921,847first reading

Engagement

120 posts held, back to 22 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 112 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
274.7%
avg views ÷ 20,824 subscribers
Avg views / post
57,200
23 posts measured
Reaction rate
0.007%
reactions ÷ views · ER floor
Posts in window
23
of 120 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 7 of 23 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 October 2026
Posts held120 (22 July 2026 – 13 October 2026)
Views total1,315,480
Reactions total29
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Oct 2026, 09:00 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

647 reactions across 11 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤647100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 15 of the 120 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 647 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 120 most recent posts we hold, published 22 July 2026 to 13 October 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
4
across the posts below
Posts paid on
4
of 120 we hold a reading for · 3%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @O4_78. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 120 most recent posts we hold for this entry, published 22 July 2026 to 13 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 21 of 23 posts held from the last 30 days (91.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

13 Oct 2026, 07:33 UTC≈9,880 viewsread 13 October 2026
Photo

#عــاجــل التربية تطلق التقديم الإلكتروني للانتساب وتحدد 30 تشرين الثاني موعدا نهائيا للتسجيل https://t.me/O4_78

12 Oct 2026, 22:59 UTC≈23,900 views0 reactionsread 13 October 2026

المحافظات التي تعرضت للعاصفة الترابية: - كربلاء ( عاصفة ترابية ) - النجف ( مطر - تراب ) - بغداد ( عاصفة ترابية ) - بابل ( مطر - تراب )

12 Oct 2026, 22:46 UTC≈24,800 viewsread 13 October 2026

#عــاجــل العاصفة الترابية تصل بغداد قادمة من كربلاء

12 Oct 2026, 22:31 UTC≈25,900 viewsread 13 October 2026

#عــاجــل بدأ هطول الامطار في اغلب المحافظات

12 Oct 2026, 22:26 UTC≈26,500 viewsread 13 October 2026

#عــاجــل عاصفة ترابية تجتاح أجواء محافظة كربلاء والنجف وبابل والديوانيه

12 Oct 2026, 19:14 UTC≈36,700 viewsread 13 October 2026

#عــاجــل التربية النيابية : تواصلنا مع وزير التربية لبحث إمكانية منح طلبتنا دوراً ثالثاً،

12 Oct 2026, 17:19 UTC≈44,200 viewsread 13 October 2026

#عــاجــل موافقة وزير التربية على عقد جلسة طارئة لهيئة الرأي لحسم ملف الدور الثالث .

12 Oct 2026, 11:56 UTC≈54,400 views0 reactions1 Starread 13 October 2026

#عــاجــل هيئة الرأي تقرر إضافة درجتين لمعالجة الدرجات الحرجة للصفوف غير المنتهية.

12 Oct 2026, 09:32 UTC≈57,200 views0 reactions1 Starread 13 October 2026

#عــاجــل موافقة شفهية للمتظاهرين علئ الدور الثالث لطلبة السادس الابتدائي والثالث متوسط والسادس الاعدادي

11 Oct 2026, 20:59 UTC≈64,600 views0 reactionsread 13 October 2026

#عــاجــل وزير التربية يبشر طلبة الانتساب بأن الحل بالمدرسة الالكترونية وتمكينهم بمواصلة دراستهم • من الممكن اعلان الانتساب خلال هذه الايام القادمة

11 Oct 2026, 15:56 UTC≈73,000 viewsread 13 October 2026

#عــاجــل تعطيل الدوام الرسمي في جميع المحافظات ليوم الاحد الموافق 10/25 بمناسبة استشهاد السيدة فاطمة الزهراء (ع)

11 Oct 2026, 15:03 UTC≈70,700 viewsread 13 October 2026

#عاجل_جدا عاصفة رعدية مصحوبة بالأمطار الغزيرة تتجه من منفذ طريبيل الحدودي الى الرطبة

Showing the 12 most recent of 120 posts we hold for @O4_78. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@O4_78 edited 19 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
4 September 2026
Most recent edit
12 October 2026

Posts recorded as deleted after publishing

We recorded 17 posts on @O4_78 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
24 August 2026
Most recent seen missing
13 October 2026
Median time before seen missing
46 hours
Seen missing in the last 30 days
6

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

13 Sept 2026, 09:02 UTCAnonymous Poll16,800 voters approx.

هل انت مع او ضد تاجيل الدوم الى 10/1

  1. مع ✅78%
  2. ضد ❌24%

The shares total 102%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 120 most recent posts we hold, published 22 July 2026 to 13 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Mentions

Named by 1 registered channel — 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.

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 8 November 2026 — this entry's latest reading, not the date you are reading this.

“اخبار الجامعات ابن النجف” (@O4_78), 20,824 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/O4_78.

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.