Telegram RegisterThe public register of Telegram
Telegram profile photo for فرانت کد | FrontCode

Channel

فرانت کد | FrontCode

@frontcode01

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

2,471subscribers

-15 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001450646885
TypeChannel
Username@frontcode01
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/frontcode01

Growth

2,4642,4862,4756 August 2026 — 2,486 subscribers6 August 2026 — 2,486 subscribers10 August 2026 — 2,481 subscribers13 August 2026 — 2,483 subscribers17 August 2026 — 2,485 subscribers20 August 2026 — 2,484 subscribers27 August 2026 — 2,481 subscribers30 August 2026 — 2,476 subscribers2 September 2026 — 2,472 subscribers6 September 2026 — 2,464 subscribers11 September 2026 — 2,471 subscribers2,4716 August 202611 September 2026
11 measurements spanning 35 days, net -15. 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,461–2,489 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 08:402,471+7
6 Sept 2026, 11:352,464-8
2 Sept 2026, 01:532,472-4
30 Aug 2026, 08:282,476-5
27 Aug 2026, 01:582,481-3
20 Aug 2026, 02:342,484-1
17 Aug 2026, 09:542,485+2
13 Aug 2026, 11:142,483+2
10 Aug 2026, 03:412,481-5
6 Aug 2026, 21:452,486no change
6 Aug 2026, 21:012,486first reading

Engagement

20 posts held, back to 22 April 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of 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 25 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

758 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 48.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣36748.4%
👍15119.9%
13417.7%
🔥8210.8%
😍202.64%
10.132%
👎10.132%
💔10.132%
🤯10.132%

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 758 reactions 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 22 April 2025 to 25 June 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

25 Jun 2026, 12:50 UTC≈2,100 views16 reactionsread 7 August 2026
Photo

⚡️ Zustand vs Redux Toolkit 🆔 @frontcode01 | 👩‍💻🧑‍💻

🔥10👍42

Signed Mhmdrza

10 Jun 2026, 16:59 UTC≈4,460 views16 reactionsread 7 August 2026
Photo

🔺 اگه حوصله داکیومنت خوندن ندارید و یا پروژه‌ای داکیومنت درست حسابی نداره، به جای این‌که سر خودتون رو درد بیارید، یه سر به سایت DeepWiki بزنید و با کمک هوش‌مصنوعی، جواب سوال‌های خودتون در مورد رپوهای گیت‌هاب رو پیدا کنید. اون خودش داکیومنت و کد بیس رو کامل مطالعه می‌کنه و کار شما خیلی راحت‌تر می‌شه. 🔗 deepwiki.com 🆔 @frontcode01 | 👩‍💻🧑‍💻

🔥95👍2

Signed Mhmdrza

10 Jun 2026, 16:53 UTC≈1,140 views11 reactionsread 7 August 2026

برگشتیم ، خسته تر و امیدوار تر :)

91💔1

Signed Mhmdrza

26 Dec 2025, 10:41 UTC≈4,980 views37 reactionsread 7 August 2026
Photo

merry christmas 🎄🎅 درخت کریسمس آدم های پولدار 🆔 @frontcode01 | 👩‍💻🧑‍💻

20🤣8🔥5😍3👎1

Signed Mhmdrza

16 Dec 2025, 18:15 UTC≈5,040 views65 reactionsread 7 August 2026
Photo

وضعیت فرانت کار ادایی و وایب کدر ☕️ 🆔 @frontcode01 | 👩‍💻🧑‍💻

🤣631🤯1

Signed Mhmdrza

3 Dec 2025, 18:13 UTC≈5,760 views67 reactionsread 7 August 2026
Photo

مارکتینگ در ایران : 🆔 @frontcode01 | 👩‍💻🧑‍💻

🤣64🔥3

Signed Mhmdrza

20 Nov 2025, 16:49 UTC≈4,470 views40 reactionsread 7 August 2026
Photo

🔺 دیگه لازم نیست والد رو relative و بچه رو absolute کنی! 😇 با Anchor Positioning تو CSS، از هرجای DOM می‌تونی هر المانی رو پوزیشن بدی! 🚀 🛑 هنوز تو همه مرورگرها ساپورت نمیشه 🆔 @frontcode01 | 👩‍💻🧑‍💻

👍277🔥6

Signed Mhmdrza

1 Nov 2025, 09:29 UTC≈4,960 views14 reactionsread 7 August 2026
Photo

🧠 CSS Inherited Properties Cheatsheet 🆔 @frontcode01 | 👩‍💻🧑‍💻

🔥7👍32😍2

Signed Mhmdrza

13 Oct 2025, 08:30 UTC≈5,980 views23 reactionsread 7 August 2026
Photo

ری‌اکت ۱۹.۲ منتشر شد 🎉 ویژگی‌های جالبی در این نسخه منتشر شده : ⚡️ <Activity /> پیش‌رنـدرینگ، رندر در پس‌زمینه و حفظ state هنگام جابه‌جایی صفحات یا مخفی شدن کامپوننت‌ 🧠 useEffectEvent مدیریت event در افکت‌ها بدون dependency 🗂 cacheSignal مدیریت و به‌روزرسانی داده‌های cache شده در رندرهای async 📊 Performance Tracks ابزار دقیق برای بررسی عملکرد و بهینه‌سازی رندر 🧩 Partial Pre-rendering (PPR) ترکیب SSR و CSR برای ر

12🔥7👍3😍1

Signed Mhmdrza

29 Sept 2025, 09:29 UTC≈4,740 views74 reactionsread 7 August 2026
Photo

❌ Bug ✅ Feature 🆔 @frontcode01 | 👩‍💻🧑‍💻

🤣694👍1

Signed Mhmdrza

13 Sept 2025, 18:11 UTC≈5,100 views38 reactionsread 7 August 2026
Photo

امروز ، روز توست 🩵 🆔 @frontcode01 | 👩‍💻🧑‍💻

38

Signed Mhmdrza

6 Sept 2025, 17:38 UTC≈5,790 views9 reactionsread 7 August 2026
File

💊 5 دقیقه تا پایان سردرگمی با this ، گمشده معروف در JS ☺️🤌🏻 🆔 @frontcode01 | 👩‍💻🧑‍💻

6🔥2👍1

Signed Mhmdrza

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Crypto Insights Hub
@majale_digital · 37,394
Telegram ranks this channel #38 of 85 here — alongside 84 others — read 1 September 2026
برنامه نویسی | Programming
@Azad_Developers · 38,199
Telegram ranks this channel #62 of 88 here — alongside 87 others — read 31 August 2026
جاب‌ویژن | Jobvision | استخدام | کاریابی
@jobvision · 59,255
Telegram ranks this channel #81 of 98 here — alongside 97 others — read 22 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“فرانت کد | FrontCode” (@frontcode01), 2,471 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/frontcode01.

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.