Telegram RegisterThe public register of Telegram

Channel

daily ⇄ cf alhaitham // DCH

@dailycfAlhaitham

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

540subscribers

+0 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002173494524
TypeChannel
Username@dailycfAlhaitham
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 9 August 2026
On Telegramt.me/dailycfAlhaitham

Growth

5408 Aug 2026, 10:02 — 540 subscribers9 Aug 2026, 02:01 — 540 subscribers8 Aug 2026, 10:029 Aug 2026, 02:01
2 measurements taken within a single day. 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”. The vertical axis spans 539–541 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 02:01540no change
8 Aug 2026, 10:02540first reading

Engagement

20 posts held, back to 2 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.6%
avg views ÷ 540 subscribers
Avg views / post
78.7
20 posts measured
Reaction rate
27.8%
reactions ÷ views · ER floor
Posts in window
20
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (2 August 20267 August 2026)
Views total1,573
Reactions total437
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 10:02 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

437 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 17.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52222898924232661187717.6%
custom 52019175998179474765813.3%
custom 52222716774669621135813.3%
custom 52222914858561322185713.0%
custom 52986779516618783574510.3%
custom 5231296043705989058419.38%
custom 5222466677572134728358.01%
❤‍🔥276.18%
custom 5231137920190020894184.12%
💋132.97%
40.915%
💘20.458%
🔥20.458%

Custom emoji. 8 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 20 of the 20 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 437reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 2 August 2026 to 7 August 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.

Recent posts

7 Aug 2026, 05:03 UTC56 views22 reactionsread 8 August 2026

доброе утро, дкх спешим сообщить что с сегодняшнего дня до конца выходных у админов мини-каникулы в твиттере артов критически мало в последнее время, плюс мы с админами слегка заняты на этой неделе и заебались слегка ⚔️ надеемся на ваше понимание, любим, обнимаем ваши админы дкх

custom 520191759981794747611custom 52224666775721347285custom 52222716774669621132custom 52222898924232661182custom 52222914858561322182

6 Aug 2026, 17:25 UTC69 views18 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @NaN2_0817 on x. ✶ #адмтейк ; #others #fanart ㅤㅤㅤㅤㅤㅤㅤㅤ╰┈➤ #kaveh ㅤboost // take !не пейринг¡ ❤️ : извините за задержку у меня небольшой ремонт дома

custom 52222914858561322189custom 52224666775721347284custom 52986779516618783574❤‍🔥1

6 Aug 2026, 12:01 UTC75 views21 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @puka_puka_o on x. ✶ #адмтейк ; #fanart ㅤboost // take

custom 529867795166187835710custom 52222898924232661185custom 52224666775721347284❤‍🔥2

6 Aug 2026, 09:06 UTC79 views17 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @AnglyenArt on x. ✶ #адмтейк ; #fanart ㅤboost // take

custom 52019175998179474768❤‍🔥5custom 52222898924232661183custom 52986779516618783571

6 Aug 2026, 06:23 UTC73 views17 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @Zalyn211 on x. ✶ #адмтейк ; #fanart ; #chibi ㅤboost // take ❤️ : доброе утро. извините за задержку я только что проснулась.... в твиттере почти ничего нет это пиздец⚔️⚔️

custom 52222716774669621136custom 52312960437059890586custom 52224666775721347283❤‍🔥2

5 Aug 2026, 17:00 UTC75 views28 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @2ho_genshin on x. ✶ #адмтейк ; #fanart ㅤboost // take

custom 522228989242326611813custom 529867795166187835710custom 52312960437059890585

5 Aug 2026, 12:04 UTC79 views24 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @TaraWittich on x. ✶ #адмтейк ; #fanart ; #chibi ㅤboost // take

custom 520191759981794747610custom 52222716774669621137custom 52222898924232661185custom 52222914858561322182

5 Aug 2026, 09:12 UTC77 views18 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @NyanWasHere on x. ✶ #адмтейк ; #fanart ㅤboost // take ❤️ : извините я в тик токе засиделась

custom 522228989242326611810custom 52222716774669621134custom 52222914858561322184

5 Aug 2026, 06:02 UTC71 views28 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @slxxpynorski on x. ✶ #адмтейк ; #fanart ㅤboost // take ❤️ : доброе утро. я не згаю кого я кинню из анстара, ужасноооо я инфо переоформляю а тут этот затуп с киннами блять

custom 522228989242326611814custom 52224666775721347287❤‍🔥3custom 52312960437059890583💋1

4 Aug 2026, 20:01 UTC77 views16 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @slxxpynorski on x. ✶ #адмтейк ; #fanart ㅤboost // take ❤️ : сладких снов

custom 52019175998179474766❤‍🔥3💘2custom 52311379201900208942custom 52312960437059890582💋1

4 Aug 2026, 17:35 UTC77 views16 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @momochi_moch1 on x. ✶ #адмтейк ; #fanart ㅤboost // take ❤️ : суккааа простите за задержку, я была занята склейкой...... и все еще ее не закончила это ужас

custom 522227167746696211354custom 52312960437059890584❤‍🔥2custom 52311379201900208941

4 Aug 2026, 12:05 UTC76 views28 reactionsread 8 August 2026
Photo

ㅤㅤㅤ(( ??! )) @DCH ₊ 혔 ⌇ cr : @waternaeng on x. ✶ #адмтейк ; #others #fanart ㅤㅤㅤㅤㅤㅤㅤㅤ╰┈➤ #flins ㅤboost // take !не пейринг¡

custom 522227167746696211314custom 52019175998179474766custom 52222914858561322184custom 52986779516618783572💋1custom 52312960437059890581

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

Citation-graph rank

Citation-graph rank — 621,257 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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 3 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“daily ⇄ cf alhaitham // DCH” (@dailycfAlhaitham), 540 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/dailycfAlhaitham.

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.