Posted without readable text

Channel
OTA_DEV
@ota_dev
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
70subscribers
-3 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001459974909 |
|---|---|
| Type | Channel |
| Username | @ota_dev |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 11 October 2026 |
| On Telegram | t.me/ota_dev |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 76% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 18:20 | 70 | -4 |
| 28 Aug 2026, 06:38 | 74 | +1 |
| 13 Aug 2026, 17:54 | 73 | no change |
| 13 Aug 2026, 00:17 | 73 | first reading |
Engagement
20 posts held, back to 14 February 2022 — 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 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 5 August 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
65 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 52.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 34 | 52.3% | |
| 👍 | 22 | 33.8% | |
| custom 5418145782714874107 | 6 | 9.23% | |
| custom 5426953132846365053 | 3 | 4.62% |
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 19 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 65 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 14 February 2022 to 5 August 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
Assalomu alaykum Kanalda aktivlar bormi bo’lsa reaksiya bosilarchi
custom 54181457827148741076👍3custom 54269531328463650532
Signed Otabek
#python def juft_sonlarni_top(royxat): juft_sonlar = [x for x in royxat if x % 2 == 0] return juft_sonlar # funksiyani tekshirish raqamlar = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10] print(juft_sonlarni_top(raqamlar)) # Natija: [2, 4, 6, 8, 10] Bu funksiya juft_sonlarni_top nomli funksiya bo'lib berilgan ro'yxatdan faqat juft sonlarni ajratib oladi va ulardan iborat yangi bir ro'yxat qaytaradi. 🌀 Kanal: @Dasturch…
🔥3custom 54269531328463650531
Signed 🇺🇿 Otabek
#python Bir xil sonlarni qabul qilib, ulardan eng kattasini topib chiqadigan funksiya yozamiz: def eng_katta_top(numbers): max_num = numbers[0] for num in numbers: if num > max_num: max_num = num return max_num # funksiyani tekshirish raqamlar = [12, 45, 23, 67, 89, 34] print(eng_katta_top(raqamlar)) # Natija: 89 Ushbu funksiya eng_katta_top nomi bilan murojaat qilinadi va berilga…
🔥3
Signed 🇺🇿 Otabek
#php function dasturchi_max($x, $y) { $result = ($x * $x) + (2 * $x * $y) + ($y * $y); return $result; } $a = 5; $b = 5; echo dasturchi_max($a, $b); Result: 100 🌀 Kanal: @Dasturchi_Max
🔥2👍1
Signed 🇺🇿 Otabek
#foydali Telegram storieslarni premiumsiz galereyaga saqlash: Faylga kiring "Telegram/Telegram Stories/" ga kiring va kimni storiesini ko'rgan bo'lsangiz xammasi shu yerda chiqib keladi! Bu android uchun! 🌀 Kanal: @Dasturchi_Max
🔥4
Signed 🇺🇿 Otabek
#php // Berilgan telefon raqam $raqam = "+998938566630"; // Faqat raqamni olish $faqatRaqam = preg_replace("/[^0-9]/", "", $raqam); // Shaklga o'tkazish $shakli = "+998(" . substr($faqatRaqam, 3, 2) . ")-" . substr($faqatRaqam, 5, 3) . "-" . substr($faqatRaqam, 8, 2) . "-" . substr($faqatRaqam, 10, 2); // Natijani chiqarish echo "Boshqa shaklda: " . $shakli; ?> Result: Boshqa shaklda: +998(93)-856-66-30 🌀 Kanal:…
🔥3
Signed 🇺🇿 Otabek
🎄 Buyurtmangiz tayyor bo‘ldi. ❄️ Bizning Botdan foydalanganingiz uchun minnatdormiz! • Botni yaqinlaringizga xam ulashing🎁 🔖 Ismingiz: Otabek ⛄️ Yasadi: @YilTabrikBot
🔥1
Signed 🇺🇿 Otabek
if (isset($tx) and is_numeric($tx)) { $text = "Bu foydalanuvchi: $tx\n\n"; foreach ($baza as $key => $value) { $usera = bot('getchat',['chat_id'=>$key]); if($usera->result->username){ $url = '@'.$usera->result->username; }else{ $url = $usera->result->invite_link; } $ex = explode('-', $baza[$key][$tx])[1]; if ($ex == 0) { $text.= $url." - guruhiga odam qo'shmagan.\n\n"; }else{ $text.= $url." - guruhiga ".$ex." ta …
🔥3
Signed 🇺🇿 Otabek
Assalomu aleykum Tez kunda demayman, tez orada! Esingizda bo'lsa bizda createuzrobot bor edi, kutib qoling tez orada o'sha bot yangicha talqinda sizga taqdim etiladi! Xali xam biz bilan birga ekanligingizdan hursandmiz! #bekor_qilindi Hurmat ila @bek_max
🔥4👍1
Signed Otabek
⏱ Profil uchun soat kodi! (rasmli, lekin apini o'ziz qilib olasiz) 🌀 Manba: @UZ_PHP_COD
🔥4
Signed 🇺🇿 Otabek
📝 Kanalingiz biosiga soat, ob-havo va yangi yilga qolgan vaqtni qo'yib beradi! ⏱ Kodni cron qilib qo'yasiz! 🌀 Manba: @UZ_PHP_COD
🔥4
Signed 🇺🇿 Otabek
Showing the 12 most recent of 20 posts we hold for @ota_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.
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.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@ota_dev named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 6 posts, 13 August 2026 – 13 August 2026
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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“OTA_DEV” (@ota_dev), 70 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/ota_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.