Telegram RegisterThe public register of Telegram
Telegram profile photo for ••𝙃𝙖𝙖𝙡𝙛 𝙢𝙤𝙤𝙣••

Channel

••𝙃𝙖𝙖𝙡𝙛 𝙢𝙤𝙤𝙣••

@haalf_moon

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

200subscribers

-1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002077387536
TypeChannel
Username@haalf_moon
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/haalf_moon

Growth

198201199.57 August 2026 — 201 subscribers8 August 2026 — 201 subscribers16 August 2026 — 199 subscribers24 August 2026 — 198 subscribers30 August 2026 — 200 subscribers2007 August 202630 August 2026
5 measurements spanning 23 days, net -1. 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 198–201 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 09:14200+2
24 Aug 2026, 07:13198-1
16 Aug 2026, 14:25199-2
8 Aug 2026, 11:31201no change
7 Aug 2026, 12:49201first reading

Engagement

19 posts held, back to 27 July 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
20.5%
avg views ÷ 200 subscribers
Avg views / post
40.9
13 posts measured
Reaction rate
7.09%
reactions ÷ views · ER floor
Posts in window
13
of 19 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 6 of 13 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 8 August 2026
Posts held19 (27 July 20268 August 2026)
Views total532
Reactions total18
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 11:31 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

43 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 32.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥1432.6%
🌚1023.3%
👍1023.3%
🤝920.9%

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

Measured over the 19 most recent posts we hold, published 27 July 2026 to 8 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

8 Aug 2026, 09:23 UTC11 views4 reactionsread 8 August 2026

وضعیت : - چه احساسی داری؟ + نمیدونم!!

👍4

Signed Nima

7 Aug 2026, 16:35 UTC25 views1 reactionsread 8 August 2026

نمیدونما ولی این جمعه از همه غم‌انگیز‌تر بود

🌚1

7 Aug 2026, 14:11 UTC28 viewsread 8 August 2026

فکر کنم کل امروزو با دلتنگی و بی‌حوصلگی به سر ببرم

6 Aug 2026, 16:39 UTC29 views1 reactionsread 8 August 2026

ولی خدایی فضای اینستا واقعا خیلی مسمومه راست میگفتن!

🤝1

6 Aug 2026, 08:52 UTC31 viewsread 8 August 2026

کاش بندازمش جلو سگ بخوره یام‌یام‌یام🫶

5 Aug 2026, 14:54 UTC33 viewsread 8 August 2026

من باورم نمیشه طرف تو چنل خودش پست میزاره ولی یک ماهه پی‌وی منو سین نزده بلاکش کنم؟💅

5 Aug 2026, 10:14 UTC35 viewsread 8 August 2026

فارغ از هر چه که ناراحتم میکنه از بابت تو خوشحالم

4 Aug 2026, 09:25 UTC61 views5 reactionsread 8 August 2026

جدی برای تحمل ادامه تابستون نیاز دارم حداقل یه هفته زمستون باشه

👍5

3 Aug 2026, 19:14 UTC56 viewsread 8 August 2026

بچها فیلترشکن رایگان خوب معرفی میکنین؟

2 Aug 2026, 13:22 UTC63 views4 reactionsread 8 August 2026

همسایمون یه جوری میدوعه بچه‌هاش از صدای پدافند و انفجار بدتره دو دیقه اروم بشین دیگه اه

🌚2👍1🤝1

1 Aug 2026, 19:50 UTC65 views3 reactionsread 8 August 2026

غم عجیبی تمام وجودمو گرفته

🌚3

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

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.

“••𝙃𝙖𝙖𝙡𝙛 𝙢𝙤𝙤𝙣••” (@haalf_moon), 200 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/haalf_moon.

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.