Telegram RegisterThe public register of Telegram
Telegram profile photo for HYPHEN

Channel

HYPHEN

@hyphen_dev

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

2,178subscribers

+123 since we began measuring on 26 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1004412270402
TypeChannel
Username@hyphen_dev
Created6 August 2026measured — dated from the channel’s first post
First recorded26 August 2026
Last confirmed live10 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/hyphen_dev

Growth

2,0542,1782,11626 August 2026 — 2,055 subscribers27 August 2026 — 2,054 subscribers29 August 2026 — 2,064 subscribers1 September 2026 — 2,073 subscribers5 September 2026 — 2,106 subscribers10 September 2026 — 2,178 subscribers26 August 202610 September 2026
6 measurements spanning 15 days, net +123. 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 2,035–2,197 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 21:182,178+72
5 Sept 2026, 13:402,106+33
1 Sept 2026, 14:422,073+9
29 Aug 2026, 18:352,064+10
27 Aug 2026, 04:342,054-1
26 Aug 2026, 12:152,055first reading

Engagement

16 posts held, back to 6 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
16.5%
avg views ÷ 2,178 subscribers
Avg views / post
360
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
5
of 16 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 20 August 2026
Posts held16 (6 August 202620 August 2026)
Views total1,802
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Aug 2026, 12:15 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.

Recent posts

20 Aug 2026, 13:16 UTC251 viewsread 26 August 2026
Photo

🔄 Flood Auto retry ⏳ در حین انجام عملیات های جوینی، هرموقع هرکدوم از اکانت ها لیمیت‌جوین بشه، تایم محدودیت هرکدوم از اکانت ها بررسی میشه و برای تلاش مجدد همونقدر صبر میکنه. 🤚 همچنین دکمه توقف هم برای متوقف کردن ادامه تلاش ها وجود داره که با کلیک کردن روش دیگه جوینی در ادامه صورت نمیگیره. ⚙️ این آپشن از طریق پنل تنظیمات قابل فعالسازی/غیرفعالسازی هست. 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

20 Aug 2026, 01:36 UTC642 viewsread 26 August 2026

⬆️ آپدیت روی سرور ها اعمال شد. 🗂 مقدار فضای فایل منیجر از 50MB به 100MB تغییر پیدا کرد. 💬 مدیریت درخواست های همزمان تا ۳ برابر دقیق تر و سریع تر شد. 💬 کامنت خودکار از این به بعد با Typing… همراه میشه. 🛒 خرید پورت از طریق پورت سلر مجدد باز شد. 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

19 Aug 2026, 20:51 UTC258 viewsread 26 August 2026

〰️ امشب همراه با آپدیت، چند سرور جدید اضافه میشن و ظرفیت بیشتری در دسترس داریم. ✅ به محض آپدیت، خرید پورت های جدید مجدد قابل انجام میشه. 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

19 Aug 2026, 14:42 UTC268 viewsread 26 August 2026

🧊 اگر ایده ای برای آپدیت های بعدی داشتید،(چه برای تلگرام و چه اپ های دیگه) حتما باهامون در میون بزارید. 😘 عجیب غریب بودن و یا سختیش مهم نیست، ایده با شما و عملی کردنش با ما. ⬇️⬇️⬇️

16 Aug 2026, 01:09 UTC383 viewsread 26 August 2026

🐥 قراره هفته پر آپدیتی رو تجربه کنیم. 😊 از ابزار های مختلف تا بخش های جدید، همگی با بیشترین کیفیت و منصفانه ترین قیمت ممکن. 🤖 Link Bot ➡️@tabchi_port_bot 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

13 Aug 2026, 16:42 UTC422 viewsread 26 August 2026

💎 تغییراتی که روی رفتار پیوی خودکار اعمال شد: ✅ سین کردن پیوی دیگه بلافاصله نیست، بعد از چند ثانیه اتفاق میوفته که خیلی انسانی تره. 💬 تایپینگ پیام ها فعال شده و در حین ارسال پیام ها، متن …Typing مثل مواقع واقعی نشون داده میشه. ⏱️ فاصله بین ارسال پیام ها نسبت به خود پیام ها متغیر شده، زمان تایپینگ هر پیام، نسبت به تعداد کاراکتر های پیام انتخاب میشه. 🤖 Link Bot ➡️@tabchi_port_bot 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

13 Aug 2026, 14:19 UTC710 viewsread 26 August 2026

🔄 آپدیت V1.6.3 روی تمامی پورت ها اعمال شد. تغییرات 👇 • اضافه شدن رفتار انسانی به بخش پیوی خودکار. • افزایش پایداری هندلینگ پیام های همزمان. • رفع مشکل کم بودن کیفیت عکس های پروفایل. 🤖 Link Bot ➡️@tabchi_port_bot 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

13 Aug 2026, 13:41 UTC344 viewsread 26 August 2026

〰️ ساعت 17:30 پورت ها برای آپدیت خاموش میشن، آمادگی داشته باشید. 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

12 Aug 2026, 08:35 UTC206 viewsread 26 August 2026
Photo

👤 | آپدیت اد خودکار. 🔧 | توی آپدیت جدید، قابلیت اد خودکار از پنل تنظیمات قابل روشن کردنه! 💬 | با روشن کردن این آپشن، هر کسی روی پیام اکانت های شما ریپلای بزنه و کلماتی مثل: اد کن - ادکن - اد - پی - پیوی - سیو کن و … ارسال کنه، اکانتش به صورت خودکار به مخاطبین اکانت شما اضافه میشه. ✅ | بعد از اد موفق، به شخص مورد نظر اطلاع میده که اد کرده. 🤖 Link Bot ➡️@tabchi_port_bot 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

12 Aug 2026, 08:02 UTC710 viewsread 26 August 2026

🧊 | آپدیت روی پورت سلر اعمال شد. تغییرات 👇 👤 اضافه شدن انتقال مالکیت پورت 🔑 اضافه شدن قابلیت تغییر توکن بات 👥 اضافه شدن قابلیت تغییر گپ‌پنل 🤖 Link Bot ➡️@tabchi_port_bot 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

10 Aug 2026, 09:49 UTC904 viewsread 26 August 2026

🌐 | آپدیت پایداری روی اکانت منیجر اعمال شد و پایداری به بهترین حد ممکن رسید. 💎 | تبچی و سندر پایدار تر شدن. 〰️ | 4 سرور جدید آماده و نصب شدن. 🤖 Link Bot ➡️@tabchi_port_bot 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

6 Aug 2026, 21:44 UTC575 viewsread 26 August 2026

🤖 ربات فروش پورت اکانت منیجر هایفن فعال شد. ⬇️ بخشی از قابلیت های اکانت منیجر. ✈ سندر حرفه ای برای ارسال هر پیام یا فایلی به پیوی و گروه های اکانت. ↗️ تبچی خودکار و قدرتمند با متود های دیلی و اسلیپ که از ریپ شدن اکانت هاتون به شدت جلوگیری میکنه. 💬 رد کردن جوین اجباری، به صورت خودکار جوین اجباری گپ ها رو دور میزنه. 🤩 پاسخگوی خودکار به پیوی ها، هر تعداد پیامی رو که شما مشخص کنید با هر محتوایی، به هرکسی که به اکانت

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

Forward network

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.

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.

Named by

Channels on the register whose posts name this channel's handle.

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

“HYPHEN” (@hyphen_dev), 2,178 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/hyphen_dev.

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.