Telegram RegisterThe public register of Telegram

Channel

bilol_tech

@bilol_tech

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

25subscribers

+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-1001905040603
TypeChannel
Username@bilol_tech
Description👨‍💻 Flutter Dev at Smart Card Co. 📅 19 Years Old | Tech Setup Enthusiast 🌐 Spreading IT News & Motivation 🚀 Motivating coders, one algorithm at a time
CreatedBetween 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/bilol_tech

Growth

257 August 2026 — 25 subscribers11 August 2026 — 25 subscribers7 August 202611 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 24–26 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 09:4725no change
7 Aug 2026, 14:0525first reading

Engagement

18 posts held, back to 21 January 2024the 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 18 posts for this entry, the most recent from 16 April 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
14
Videos
23
Links
24

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

Video runtime
1m 47s
Average length
27s

Measured directly from 4 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

123 reactions across 16 posts, in 22 distinct kinds. The most used accounts for 21.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2621.1%
❤‍🔥2318.7%
👍1310.6%
97.32%
🥰86.50%
75.69%
😢75.69%
🏆43.25%
👏43.25%
👀32.44%
😁32.44%
🤯32.44%
👎21.63%
💯21.63%
🤬21.63%
🎉10.813%
😍10.813%
😎10.813%
😭10.813%
🤝10.813%
2 further kinds21.63%

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 16 of the 18 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 123reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 21 January 2024 to 16 April 2025, 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

16 Apr 2025, 18:47 UTC528 views2 reactionsread 11 August 2026

🎬 7-bo‘limdagi mo‘jiza Aqli zaif, begunoh bir ota. Uni chin dildan yaxshi ko‘radigan qizi. Ularni ayirishga urinayotgan shafqatsiz dunyo. Bu film shunchaki voqea emas — bu yurakdan chiqqan faryod. Tomosha qilganimda ko‘z yoshlarimni tiya olmadim. Avval yuragimni ezdi… keyin esa eng go‘zal tarzda tikladi. Agar biror narsani chin dildan sevgan yoki adolatsizlikni his qilgan bo‘lsangiz — bu film yuragingizga muhrlanad

🔥2

29 Mar 2025, 19:10 UTC470 views7 reactionsread 11 August 2026

Ushbu muborak kunda barchangizni qalbimizdagi eng chuqur tilaklar bilan tabriklayman! Ramazon hayiti barchangizga fayz, baraka va tinchlik olib kelsin. Ishlaringiz bardavom, oilalaringiz tinch va baxtli bo‘lsin! Id Muborak!

🥰311❤‍🔥1👍1

28 Feb 2025, 18:34 UTC485 views5 reactionsread 11 August 2026

Assalomu Aleykum Ramazon oyi muborak bo’lsin! Ushbu muqaddas oy siz va yaqinlaringizga tinchlik, baraka va fayz olib kelsin. Duo va ibodatlaringiz qabul bo‘lsin! @bilol_tech

👍3🔥1🥰1

11 Feb 2025, 16:57 UTC552 views4 reactionsread 11 August 2026

iOS va Android uchun lokal bildirishnomalarni qo‘shish bo‘yicha oson tushuntiruvchi maqola yozdim. Unda flutter_local_notifications kutubxonasidan qanday foydalanishni ko‘rsatdim. 📖 Maqola ingliz tilida yozilgan. Bu yerda o‘qishingiz mumkin: Implementing Local Notifications in Flutter for iOS and Android using flutter_local_notifications PS. Agar maqola foydali bo‘lsa, uni do‘stlaringiz bilan ulashing! @bilol_tec

11❤‍🔥1🥰1

24 Jan 2025, 17:44 UTC337 views6 reactionsread 11 August 2026

iOS va Android uchun vidjetlarni yaratish bo‘yicha oson tushuntiruvchi maqola yozdim. Unda home_widget kutubxonasidan qanday foydalanishni ko‘rsatdim. Maqola ingliz tilida yozilgan. Bu yerda o'qishingiz mumkin: Building Home Screen Widgets in Flutter for iOS and Android using home_widget PS. Agar siz ushbu maqolani foydali deb topsangiz, uni do’stlaringiz bilan ulashing. @bilol_tech

🏆211❤‍🔥1🔥1

8 Nov 2024, 16:43 UTCviews —

bilol_tech pinned «Hammaga salom 👋 Medium platformasida maqolalar yozishni boshladim. Boshlashdan maqsadim fikrlarimni yozma shaklda erkin bayon qilishni o’rganish va o’z tajribalarimni boshqalar bilan ulashishdir. Ushbu maqolada quyidagilar haqida o'rganishingiz mumkin: 💭…»

5 Jun 2024, 11:36 UTC828 views15 reactionsread 11 August 2026

Hammaga salom 👋 Medium platformasida maqolalar yozishni boshladim. Boshlashdan maqsadim fikrlarimni yozma shaklda erkin bayon qilishni o’rganish va o’z tajribalarimni boshqalar bilan ulashishdir. Ushbu maqolada quyidagilar haqida o'rganishingiz mumkin: 💭 Xakatonlar nima va ular nima uchun muhim 💡"Hacknovation 2024" xakatonidagi tajribam 🖼️ Xakatonlarda muvaffaqiyatga erishish uchun maslahatlar Maqola o'zbek tilida

❤‍🔥4👏4🔥3🏆211

28 Apr 2024, 01:33 UTC729 views8 reactionsread 11 August 2026
Photo

Dynamic Links is no longer supported on Firebase, and will stop working on August 25, 2025. 😐

❤‍🔥5👀3

17 Apr 2024, 12:26 UTC692 views15 reactionsread 11 August 2026
Video

🆕 Had an incredible time at "Build with AI" event! 🌟 👤 Speaker: Sasha, Chief Software Engineer @ EPAM Systems 🗣 Sasha delved into: 1️⃣ Connecting ChatGPT via Rest API 2️⃣ Utilizing Gemini with google_generative_ai plugin 3️⃣ Integrating Gemma with flutter_gemma plugin 4️⃣ Leveraging Vertex AI API for Gemini 5️⃣ Exploring Gemini with google_generative_ai plugin using Vertex AI API 6️⃣ Integrating Gemma with Vertex

❤‍🔥43🔥3👍21🎉1🤩1

16 Apr 2024, 15:51 UTC482 views5 reactionsread 11 August 2026
Forwarded from @gdgtashkentPhoto

GenAI workshop was great! Thanks for coming! Please claim your attendee badge from Google Dev Profile: https://docs.google.com/forms/d/e/1FAIpQLSd5yoE7GEC7srAqXH6GwxUrwyjAxaW2pOwUo0nw0-EdvqA_5Q/ @gdgtashkent

❤‍🔥2👍2🔥1

Showing the 12 most recent of 18 posts we hold for @bilol_tech. 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“bilol_tech” (@bilol_tech), 25 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/bilol_tech.

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.