Telegram RegisterThe public register of Telegram
Telegram profile photo for AG Coding

Channel

AG Coding

@agcoding

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry

1,170subscribers

-4 since we began measuring on 1 September 2026

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

Register entry

Telegram ID-1001228241564
TypeChannel
Username@agcoding
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded1 September 2026
Last confirmed live19 September 2026
Measurements held5
Confirmed unchanged2 times, most recently 19 September 2026
On Telegramt.me/agcoding

Growth

1,1701,1751,172.51 September 2026 — 1,174 subscribers1 September 2026 — 1,174 subscribers5 September 2026 — 1,175 subscribers11 September 2026 — 1,172 subscribers14 September 2026 — 1,170 subscribers1 September 202614 September 2026
5 measurements spanning 14 days, net -4. 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 1,169–1,176 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 23:201,170-2
11 Sept 2026, 02:551,172-3
5 Sept 2026, 21:391,175+1
1 Sept 2026, 10:171,174no change
1 Sept 2026, 04:451,174first reading

Engagement

20 posts held, back to 18 July 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 page 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 19 March 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 02s
Average length
31s

Measured directly from 2 videos 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.

Reaction mix

21 reactions across 13 posts, in 2 distinct kinds. The most used accounts for 90.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1990.5%
👍29.52%

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 14 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 21 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 18 July 2025 to 19 March 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

19 Mar 2026, 17:26 UTC247 views2 reactionsread 1 September 2026
Photo

عيد فِطر مٌبارك عليكم جميعًا ♥️

2

19 Mar 2026, 13:39 UTC823 views1 reactionsread 1 September 2026
Video

ضفت feature في موقعي: AI Assistant للمقابلات تكتب أي سؤال ممكن يتسألك وهو: يجاوبك يشرح الفكرة ويربطها بمقالات أنا كاتبها يعني بدل ما تحفظ answer بتفهم system الميزة حاليًا شغالة على موديل مجاني وفيه شوية limitations بس قريب هتتنقل لموديل مدفوع وهيبقى أدق وأقوى جربه: https://agcoding-blog.vercel.app/

1

19 Mar 2026, 13:23 UTC614 views1 reactionsread 1 September 2026
Photo

https://www.linkedin.com/posts/abdoelazizgamal_%D8%A3%D8%AE%D8%B7%D8%B1-%D8%AD%D8%A7%D8%AC%D8%A9-%D9%81%D9%8A-middleware-%D8%A5%D9%86%D9%83-%D8%AA%D9%82%D8%AF%D8%B1-%D8%AA%D8%B3%D8%AA%D8%AE%D8%AF%D9%85%D9%87%D8%A7-share-7440386731897683968-N8Hj?utm_source=social_share_send&utm_medium=ios_app&rcm=ACoAAC5FoGcB_ZF-qqZyWU1avd4ojJ8sF-2l7Ss&utm_campaign=copy_link

1

26 Feb 2026, 20:00 UTC≈1,120 views2 reactionsread 1 September 2026
File

أغلب مشاريع Backend مش بتنهار بسبب Performance. بتنهار بسبب Project Structure. في الأول كل حاجة تبقى ماشية: controllers/ services/ utils/ models/ شكل Professional… لكن بعد شوية: Dependencies تتشابك كل Feature تبقى مخاطرة Bug صغير يكسر نص السيستم وساعتها تفهم الحقيقة: Project Structure مش تنظيم ملفات. Project Structure هو: Architecture متخفية. هو اللي بيحدد: مين يعتمد على مين إيه اللي مسموح يتوصل بإيه

1👍1

24 Feb 2026, 16:37 UTC637 views2 reactionsread 1 September 2026
File

Express مش هو السيرفر. هو مجرد comfort layer فوق: http.createServer() المشكلة مش إنك تستخدم Express. المشكلة إنك تستخدمه قبل ما تفهم هو بيخبي إيه. أول مرة تبني HTTP Server بإيدك بتكتشف الحقيقة: الـ Request مش JSON. هو Stream من bytes. والـ Routing ده مش: app.get('/users') هو فعلياً: if (req.method === 'GET' && req.url === '/users') مفيش Magic في Express. في abstractions بس. وكل abstrac

2

22 Feb 2026, 21:03 UTC532 viewsread 1 September 2026

https://agcoding-blog.vercel.app/posts/nodejs-internals-simplified/

22 Feb 2026, 20:58 UTC785 views1 reactionsread 1 September 2026
File

Node.js مش “Single Threaded” زي ما فاكرين. هو Single Threaded في تنفيذ JavaScript… لكن مش في الانتظار. السيرفرات التقليدية كانت بتعمل Thread لكل Request. 10,000 مستخدم = 10,000 Thread = RAM ضخمة + Context Switching + انهيار تحت الضغط. Node عمل حاجة أذكى: نقل “الانتظار” لنظام التشغيل. الـ Main Thread: • يستقبل الطلب • يفوض الـ I/O • يكمل يخدم غيره • يرجع ينفذ الـ Callback لما الرد يجه يعني المشكلة عمرها ما كانت

1

21 Feb 2026, 15:24 UTC507 views2 reactionsread 1 September 2026
File

What is Backend Really? معظم الـ Frontend Devs شايفين الـ Backend بالشكل ده: fetch("/api/users") يرجع JSON… وخلاص. لكن قبل ما السطر ده يشتغل، بيحصل: DNS TCP Handshake TLS Encryption Reverse Proxy Load Balancing Authentication Caching Database Indexing الـ Backend مش “API”. الـ Backend هو نظام كامل بيشتغل تحت ضغط آلاف المستخدمين وبيحمي الداتا وبيضمن الاستقرار وبيتعامل مع الفشل قبل ما إ

1👍1

20 Feb 2026, 12:22 UTC678 views1 reactionsread 1 September 2026
Photo

كل سنة وانتوا طيبين ورمضان مٌبارك عليكم يارب♥️ Deep Dive into Zustand with Next.js: Architecture & Hydration لو اشتغلت بـ Next.js + Zustand قبل كده، فأكيد قابلت مشاكل زي: • Hydration mismatch • State بيختلف بين الـ server والـ client • Errors من نوع: “Text content does not match server-rendered HTML” في المقال ده شرحت: • ليه التحديات دي بتحصل فعلًا • إزاي تبني Store architecture صح مع SSR • أنماط عملية لتجنب

1

20 Feb 2026, 00:13 UTC164 views2 reactionsread 1 September 2026
Photo

رمضان مُبارك عليكم جميعًا ♥️

2

20 Dec 2025, 16:18 UTC≈1,160 viewsread 1 September 2026
Photo

https://www.linkedin.com/posts/activity-7408176678646063104-cZVw?utm_medium=ios_app&rcm=ACoAAC5FoGcB_ZF-qqZyWU1avd4ojJ8sF-2l7Ss&utm_source=social_share_send&utm_campaign=copy_link

19 Dec 2025, 12:40 UTC≈1,020 views0 reactionsread 1 September 2026

بعد ما خلّصنا وجع دماغ this… جه دور شنطة الذكريات: الـ Closures في المقال اللي فات فهمنا إن: this = مين ندهني؟ النهاردة بقى بنفهم: Closure = أنا فاكر أنا اتكتبت فين، ومش ناسي اللي شوفته. الدالة في JavaScript لما تخلص: مش بتمشي فاضية بتمشي بشنطة والشنطة دي فيها المتغيرات اللي محتاجاها وعشان كده: setTimeout بيطبع أرقام غريبة Event Listeners تفضل فاكرة كل click React state ما يضيعش ولو شنطتك تقيلة… Memory Leak المقالة

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

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.

تجميعة عصير الكتب ( الأعمال الكاملة )
@aseeralkotob · 37,193
Telegram ranks this channel #60 of 72 here — alongside 71 others — read 1 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 14 September 2026 — this entry's latest reading, not the date you are reading this.

“AG Coding” (@agcoding), 1,170 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/agcoding.

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.