Channel
@zebardast_dev
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
84subscribers
-3 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001835958965 |
|---|---|
| Type | Channel |
| Username | @zebardast_dev |
| Created | Between 1 October 2022 and 8 June 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/zebardast_dev |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 08:57 | 84 | -2 |
| 15 Aug 2026, 19:48 | 86 | -1 |
| 9 Aug 2026, 16:01 | 87 | no change |
| 8 Aug 2026, 00:23 | 87 | first reading |
20 posts held, back to 8 June 2023 — the 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 19 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
118 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 33.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 39 | 33.1% | |
| ❤ | 33 | 28.0% | |
| 👍 | 11 | 9.32% | |
| 👏 | 8 | 6.78% | |
| ⚡ | 5 | 4.24% | |
| 💯 | 5 | 4.24% | |
| 🥰 | 5 | 4.24% | |
| 🤩 | 4 | 3.39% | |
| 👨💻 | 2 | 1.69% | |
| 😇 | 2 | 1.69% | |
| 😍 | 2 | 1.69% | |
| ❤🔥 | 1 | 0.847% | |
| 🤗 | 1 | 0.847% |
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 118reactions 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 8 June 2023 to 19 July 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.
هلیکسپرس؛ نگاهی مدرن به توسعه وردپرس ✨ مدتها بود به این فکر میکردم که توسعه وردپرس میتونه تجربهای تمیز، منظم و خوشدست باشه؛ چیزی نزدیک به حسی که در فریمورکهای مدرن مثل لاراول داریم. HelixPress رو با همین نگاه جلو بردم؛ تلاشی برای اینکه توسعه تم های وردپرس ساختارمند، قابلفهم و برای برنامهنویسها روان باشه. ⚙️ بخشی از امکانات HelixPress که تا الان پیاده سازی شده: 🧩 Blade Renderer 🧱 Component System 🗂️ T…
👏2🔥2❤🔥1
تابعی بنویسین که یه رشته دودویی (فقط 0 و 1) دریافت کنه و تعداد 101 موجود تو رشته رو برگردونه: نکات مهم ✅ 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین. 🆔 Channel Id : @prog_challenge
👍1🔥1
تابعی بنویسین که عدد n رو دریافت کنه و سری اعداد زیبا رو چاپ کنه: اگه نمیدونین اعداد زیبا چیه، به مثال داخل عکس توجه کنین نکات مهم ✅ 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین. 3️⃣ از توابع آماده استفاده نکنین و خودتون الگوریتمشو بنویسین. 🆔 Channel Id : @prog_challenge
❤1👍1
تابعی بنویسین که عدد صحیح n رو از ورودی بگیره و ارقامی که بیشتر از یک بار استفاده شده رو حذف کنه نکات مهم ✅ 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین. 🆔 Channel Id : @prog_challenge
💯2👍1
تابعی بنویسین که عدد n را از ورودی دریافت کنه و ارقام اون عدد رو معکوس کنه و تو خروجی نمایش بده: نکات مهم ✅ 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین. 3️⃣ از توابعی مثل reverse استفاده نکنین و خودتون الگوریتمشو بنویسین. 🆔 Channel Id : @prog_challenge
🔥4⚡1
تابعی بنویسین که عدد n رو از ورودی بگیره و یه ماتریس n*n بصورتی که تو عکس مشخص شده چاپ کنه نکات مهم ✅ 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین. 🆔 Channel Id : @prog_challenge
❤3🔥1
تابعی بنویسین که عدد n رو از ورودی دریافت کنه و اعداد اول کوچکتر از n رو چاپ کنه: عدد اول، عددیه که از 1 بزرگتره و فقط بر خودش و 1 بخش پذیره نکات مهم ✅ 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین. 🆔 Channel Id : @prog_challenge
🔥4❤1
تابعی بنویسین که به ترتیب دو عدد n,m رو از ورودی دریافت کنه و با کاراکتر ستاره شکل H به ارتفاع m و عرض n رو تو خروجی چاپ کنه نکات مهم ✅ 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین. 🆔 Channel Id : @prog_challenge
❤3🔥2⚡1
تابعی بنویسین که یه عدد از ورودی بگیره و مشخص کنه که این عدد کامله یا نه: عدد کامل، عددیه که مجموع مقسوم علیه هاش (به جز خودش) باهاش برابر هست، مثلا ( 6 = 3 + 2 + 1 ) نکات مهم ✅ 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین. 🆔 Channel Id : @prog_challenge
🔥3👏1
تابعی بنویسین که عدد n و کاراکتر ch رو از ورودی بگیره، و در نهایت تو خروجی مثلث زیر رو چاپ کنه: نکات مهم ✅ 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین. 🆔 Channel Id : @prog_challenge
🔥3👏1👨💻1💯1
تابعی بنویسین که سه عدد از ورودی بگیره و این اعداد رو بصورت مرتب از کوچک به بزرگ چاپ کنه: نکات مهم ✅ 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین.
⚡1🔥1🥰1😇1
تابعی بنویسید که دو عدد از ورودی دریافت، سپس محتویات آن را بدون استفاده از متغیر کمکی جا به جا نماید: ✅ نکات مهم 1️⃣ به هر زبانی که تسلط دارین، برنامه رو بنویسین و به آیدی تلگرامی @zebardast_dev بفرستین. 2️⃣ بعد از انتشار هر سوال 72 ساعت فرصت دارین که جواب بدین و بفرستین. 3️⃣ در صورتی که نتونستین سوال بالا رو حل کنین، از متغیر کمکی استفاده کنین.
💯1🔥1🤗1🥰1
Showing the 12 most recent of 20 posts we hold for @zebardast_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.
Citation-graph rank — 173,813 of 1,581,209entries 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.
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.
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.
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.
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“zebardast.dev ᶜʰᵃⁿⁿᵉˡ” (@zebardast_dev), 84 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/zebardast_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.