Telegram RegisterThe public register of Telegram

Channel

devlab.uz

@devlabuz

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

11subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001243886340
TypeChannel
Username@devlabuz
DescriptionAsosan JavaScript and Front-End dasturlashga oid foydali postlar va darslar 👉 Sayt: https://devlab.uz/ 👉YouTube: https://www.youtube.com/@devlabuz
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/devlabuz

Growth

117 August 2026 — 11 subscribers12 August 2026 — 11 subscribers7 August 202612 August 2026
2 measurements spanning 4 days. 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 10–12 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 07:4511no change
7 Aug 2026, 20:5311first reading

Engagement

19 posts held, back to 22 December 2022the 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 19 posts for this entry, the most recent from 17 July 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
28
Videos
4
Links
55

Lifetime counters from Telegram’s own channel header, read 12 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.

Recent posts

17 Jul 2025, 22:37 UTC17 viewsread 12 August 2026
Photo

📈Title: Uncovering Emergency Trends: A Deep Dive into 911 Calls Data 🔗 Link: https://databit.hashnode.dev/911-calls-data-analysis 🖥 GitHub: https://github.com/haqqulzoda/911CallsAnalysis 📄 PDF: https://t.me/databitdocs/5 @databituz

9 Aug 2024, 10:04 UTC47 viewsread 12 August 2026
Forwarded from @javokhir_notesPhoto

Amazon intervyusidan o'tishimda tayyorlagan shablon Amazonda texnik intervyudan tashqari behavioural ya'ni xulq atvor intervyulariga ham jiddiy qaraydi, bunda ular o'zlarining Liderlik Prinsiplariga asoslanib tekshiradi. O'tgan yili jiddiy qabul qilmaganim tufayli bu rounddan yiqilganman, bu yil boshida yaxshiroq tayyorlanib intervyudan o'tgandim. - 50+ soat izlanib tayyorlangan shablon - eng tez tez tushadigan 1

22 Oct 2023, 05:04 UTC98 viewsread 12 August 2026

Code Review qilayotgan dastruchi: Yaxshi kod: "tushunmadim", "nima balo bu". Yomon kod: "tushunmadim", "nima balo bu" ,"qaysi qo'ling singur yozdi bu kodni", "kim ishga oldi buni".

19 Oct 2023, 14:28 UTC73 viewsread 12 August 2026

Linkedin profilimni biroz "tozalab", kerakli insonlarni follow qilishni boshlaganimdan beri o'ta qimmatli maslahatlar olyapman. Bunga 2 kun bo'ldi lekin bu professionallar meni Notion va yon daftarchamni to'ldirishda davom etishyapti.

24 Jan 2023, 08:47 UTC152 viewsread 12 August 2026

#leetcode https://www.youtube.com/watch?v=cmF08PCjCWQ&ab_channel=DeveloperLaboratory

18 Jan 2023, 07:22 UTC87 viewsread 12 August 2026

#javascript https://devlab.uz/null-va-undefined-qiymatlarni-filterlashning-yangi-usuli

15 Jan 2023, 09:23 UTC121 viewsread 12 August 2026

#leetcode https://www.youtube.com/watch?v=K4MID1SMIl4&t=185s&ab_channel=DeveloperLaboratory

12 Jan 2023, 10:26 UTC63 viewsread 12 August 2026

#javascript #conditional https://devlab.uz/javascriptda-ehtimollar-bilan-ishlash

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

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.

Mentions

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

“devlab.uz” (@devlabuz), 11 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/devlabuz.

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.