Telegram RegisterThe public register of Telegram

Channel

اخبار هدرا

@HederaPersian

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

158subscribers

+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-1002828425267
TypeChannel
Username@HederaPersian
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/HederaPersian

Growth

1588 Aug 2026, 02:18 — 158 subscribers8 Aug 2026, 18:01 — 158 subscribers8 Aug 2026, 02:188 Aug 2026, 18: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 157–159 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 18:01158no change
8 Aug 2026, 02:18158first reading

Engagement

20 posts held, back to 2 December 2025the 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
74.3%
avg views ÷ 158 subscribers
Avg views / post
117
3 posts measured
Reaction rate
7.43%
reactions ÷ views · ER floor
Posts in window
3
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. It is computed over the 2 of 3 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 7 August 2026
Posts held20 (2 December 20257 August 2026)
Views total352
Reactions total11
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 18:01 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.

What this channel posts

Photos
108
Videos
1
Links
3

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

76 reactions across 17 posts, in 8 distinct kinds. The most used accounts for 39.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3039.5%
2127.6%
👏1317.1%
🔥67.89%
🥰22.63%
🥴22.63%
😨11.32%
😱11.32%

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 17 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 76reactions 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 December 2025 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, 08:48 UTC44 views5 reactionsread 8 August 2026
Photo

🟢شرکت گری‌اسکیل ترکیب صندوق Smart Contract Fund خود را به‌روزرسانی کرد. در آخرین بازنگری، BNB، اتریوم، سولانا، کاردانو، هدرا، آوالانچ و سویی همچنان در سبد این صندوق حضور دارند و بخش عمده دارایی‌های آن را تشکیل می‌دهند. حضور این پروژه‌ها در یکی از صندوق‌های سرمایه‌گذاری مطرح بازار، نشان‌دهنده ادامه توجه سرمایه‌گذاران نهادی به اکوسیستم قراردادهای هوشمند است. #Grayscale #Crypto #Altcoins

3👍1🔥1

27 Jul 2026, 11:41 UTC104 views6 reactionsread 8 August 2026
Photo

🟢غول مدیریت دارایی جهان با حدود ۱۱.۵ تریلیون دلار دارایی تحت مدیریت، از زیرساخت Hedera برای صندوق‌های بازار پول توکنیزه‌شده استفاده کرده است. #Hedera #Blockchain #BlackRock

3👍2👏1

17 Jul 2026, 07:53 UTC204 viewsread 8 August 2026
Photo

💰 بنیاد #هدرا از جبران خسارت قربانیان هک 9.05 میلیون دلاری پلتفرم Bonzo Finance حمایت کرد. 🔹تمام موقعیت‌های کاربران به‌طور کامل بازیابی و بازگردانده شده است. #Hedera #DeFi #Crypto

15 Jul 2026, 06:06 UTC201 viewsread 8 August 2026
Photo

🤑اولین معاملات فارکس با وثیقه دارایی‌های توکنیزه‌شده در بریتانیا انجام شد! بانک Lloyds، شرکت سرمایه‌گذاری Aberdeen و پلتفرم Archax نخستین معاملات FX با استفاده از دارایی‌های دنیای واقعی توکنیزه‌شده (RWA) به‌عنوان وثیقه را روی شبکه Hedera اجرا کردند. این اقدام در گزارش Wholesale Digital Markets Champion تحت حمایت وزارت خزانه‌داری بریتانیا نیز مورد توجه قرار گرفته است؛ نشانه‌ای از حرکت مؤسسات مالی بزرگ به سمت استفاده

11 Jul 2026, 17:05 UTC184 views5 reactionsread 8 August 2026

😲 هِدرا هرگونه هک شدن شبکه را رد کرد. 🔹تیم Hedera اعلام کرد که در جریان هک 9 میلیون دلاری پلتفرم Bonzo Lend، شبکه اصلی و لایه اجماع این بلاکچین هیچ‌گونه آسیبی ندیده‌اند. 🔹بررسی‌های اولیه نشان می‌دهد منشأ این رخداد، یک سرویس تأییدکننده اوراکل شخص ثالث بوده است. با احتساب این حمله و هک 5.25 میلیون دلاری قبلی یک بریج، مجموع خسارت‌ها اکنون از 14 میلیون دلار فراتر رفته است. #Hedera #HBAR #Crypto

2👏2👍1

11 Jul 2026, 09:07 UTC157 views5 reactionsread 8 August 2026
Photo

🚨هک #هدرا؛ بیش از 3.7 میلیون دلار به سرقت رفت. 🔻گزارش‌ها حاکی از آن است که شبکه Hedera (HBAR) با یک حمله هکری در حال وقوع مواجه شده و تاکنون بیش از 3.7 میلیون دلار دارایی به سرقت رفته است. #Hedera #HBAR #Hack

🥴2👍1😨1😱1

27 Feb 2026, 05:51 UTC216 views1 reactionsread 8 August 2026
Photo

🟢شرکت‌های State Street و BlackRock، هدرا را برای صندوق‌های بازار پول توکنیزه شده انتخاب کرده‌اند. #Hedera

👍1

26 Feb 2026, 15:32 UTC205 views4 reactionsread 8 August 2026
Photo

🟢​​برترین پروژه‌های #DEFI بر اساس فعالیت اجتماعی کاربران در سوشیال مدیا $SOL $XRP $HBAR $ZEC $VVS $LINK $ASTER $MON $AVAX $CELO

👍21👏1

25 Feb 2026, 11:13 UTC204 views4 reactionsread 8 August 2026
Photo

🟢شرکت Canary Capital سکه‌های بیشتری از HBAR خریداری کرد! 🔔با عرضه محدود 50 میلیارد واحد، این خرید تقریباً 1.1٪ از کل عرضه را در یک نهاد نهادی شامل می‌شود. 📊در حالی که تریدرهای خرد نگران‌اند، موسسات در حال انباشتن هستند. #HBAR #Crypto #Institutions

👍21🔥1

20 Feb 2026, 12:35 UTC201 views5 reactionsread 8 August 2026
Photo

🟢ارز هدرا اکنون 8.5% از صندوق Smart Contract Fund متعلق به Grayscale Investments را تشکیل می‌دهد. 📌هدرا همچنان جایگاه خود را در میان پلتفرم‌های برتر قرارداد هوشمند تثبیت می‌کند. #Hedera

2👍2👏1

29 Jan 2026, 06:51 UTC258 viewsread 8 August 2026
Photo

🚨شایعه: 🟢سامسونگ قصد دارد HBAR هدرایرا در دستگاه‌های جدید گلکسی ادغام کند. #HBAR

22 Jan 2026, 19:03 UTC285 views4 reactionsread 8 August 2026
Photo

🤑طبق گزارشات مک‌لارن ریسینگ با هِدِرا همکاری می‌کند تا تجربیات طرفداری مبتنی بر وب۳ و کلکسیون‌های دیجیتال را راه‌اندازی کند. #Hedera

👍21👏1

Showing the 12 most recent of 20 posts we hold for @HederaPersian. 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 — 1,225,785 of 1,336,469entries 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.

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

“اخبار هدرا” (@HederaPersian), 158 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/HederaPersian.

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.