Bugun nocga ishga ciqadiganlar nectamiz reaksiya bosinglar shunga qarab ish olaman
❤2🤩2🫡2🙏2🔥1

Channel
@kunlik_ishlar_24
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
5,501subscribers
+22 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002427718035 |
|---|---|
| Type | Channel |
| Username | @kunlik_ishlar_24 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/kunlik_ishlar_24 |
Job listings — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 11:58 | 5,501 | +13 |
| 12 Sept 2026, 00:17 | 5,488 | +54 |
| 7 Sept 2026, 11:36 | 5,434 | -13 |
| 2 Sept 2026, 13:45 | 5,447 | -25 |
| 30 Aug 2026, 15:39 | 5,472 | -3 |
| 27 Aug 2026, 17:04 | 5,475 | +5 |
| 24 Aug 2026, 11:49 | 5,470 | -28 |
| 20 Aug 2026, 10:53 | 5,498 | -25 |
| 17 Aug 2026, 17:35 | 5,523 | +9 |
| 14 Aug 2026, 15:35 | 5,514 | -29 |
| 11 Aug 2026, 02:36 | 5,543 | +46 |
| 7 Aug 2026, 23:25 | 5,497 | +18 |
| 7 Aug 2026, 13:02 | 5,479 | first reading |
106 posts held, back to 6 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 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 106 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
318 reactions across 52 posts, in 10 distinct kinds. The most used accounts for 37.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 119 | 37.4% | |
| ❤ | 71 | 22.3% | |
| 👍 | 54 | 17.0% | |
| 🫡 | 37 | 11.6% | |
| ✍ | 11 | 3.46% | |
| 🤝 | 10 | 3.14% | |
| ❤🔥 | 7 | 2.20% | |
| 🙏 | 5 | 1.57% | |
| ⚡ | 2 | 0.629% | |
| 🤩 | 2 | 0.629% |
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 64 of the 106 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 318 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 106 most recent posts we hold, published 6 August 2026 to 12 August 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.
Bugun nocga ishga ciqadiganlar nectamiz reaksiya bosinglar shunga qarab ish olaman
❤2🤩2🫡2🙏2🔥1
Location, posted without a caption
Signed Admin
#Toldi Srochna 2 kishi kerak Ish haqi: 200.000mingdan kechgacha tugatsa 40 ming qo'shib beriladi ● Qilinadgan ish tuproq bor oshani tepaga tashish kerak ● Ish vaqti: 9 dan 19 gacha ●Tushlik: ovqat beriladi 💳 Balans:10dan ● Aloqa: @Adtmin_571t 🧑💻👈 yozinglar lakatsiya nomer beriladi ✅ 💡Ism va telefon raqam yozish esingizdan chiqmasin!!!
Signed Admin
ISH BOR xozrga 7 kwiga ● Qilinadgan ish: razni rabochi ortacha uborkaham bor ● Ish vaqti: 9dan 18:50gaca ● Ish haqi:200.000mingdan ● Manzil QOYLIQ dehqon bozori ●Tushlik: ovqat beriladi Balans 14min ● Aloqa: @adm1nstrator_24 🧑💻👈 yozinglar lakatsiya nomer beriladi kamplekt bollar bosa yaxwi bolardi
Joy bor
ISH BOR xozrga 12 kiwiga ish joyida 40kiwi boladi ● Ish haqqi:200.000mingdan ● Qilinadgan ish: razni rabochi uborka ishlari ortacha yengil odam kop boladi bilinmaydi ish ● Ish vaqti: 09:00dan 18:50gaca Manzil:yangi ozbekiston yoli avtobus boradi ●Tushlik: ovqat beriladi Balans: 10min ● Aloqa: @adm1nstrator_24 🧑💻👈 yozinglar lakatsiya nomer beriladi
❤1
ISH BOR xozrga 7 kwiga ● Qilinadgan ish: razni rabochi ortacha uborkaham bor ● Ish vaqti:09:00dan 18:50gaca ● Ish haqi:200.000mingdan ● Manzil QOYLIQ dehqon bozori ●Tushlik: ovqat beriladi Balans 17min ● Aloqa: @adm1nstrator_24 🧑💻👈 yozinglar lakatsiya nomer beriladi kamplekt bollar bosa yaxwi bolardi
✍2
ISH BOR xozrga 16 kiwiga ish joyida 40kiwi boladi ● Ish haqqi:200.000mingdan ● Qilinadgan ish: razni rabochi uborka ishlari ortacha yengil odam kop boladi bilinmaydi ish ● Ish vaqti: 09:00dan 18:50gaca Manzil:MASHINASOZLAR bekatidan190nci avtobus oldgaca boradi 20minutlarda ✅ ●Tushlik: ovqat beriladi Balans: joy band qilish ucn 14min ● Aloqa: @adm1nstrator_24 🧑💻👈 yozinglar lakatsiya nomer beriladi Ish joyiga n…
🔥1
Ertaga ish bor 30 kishiga Ish haqi:190.000mingdan ● Qilinadgan ish:razni rabochi ishlar uborkaham bor ● Ish vaqti:08:00dan 17:50gaca 7da amir temur metroda bolish kerak osha yerda toplanib ketiladi 8gada ish boshlanadi ● Manzil AMIR TEMUR METRO OLDI ishga ozlari obketishadi ●Tushlik: ovqat beriladi 💳 Balans:10dan ● Aloqa: @Admin_571t 🧑💻👈 yozinglar lakatsiya nomer beriladi ✅ 💡Ism va telefon raqam yozish esingiz…
❤2
Signed Admin
Joy bor xali
Manzil tinchlik metro
6kwiga joy bor
👍2
Showing the 12 most recent of 106 posts we hold for @kunlik_ishlar_24. 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.
@kunlik_ishlar_24 edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
@kunlik_ishlar_24 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.
References a handle that is not a live channel — we have no record it ever was one.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Kunlik ishlar va Ishchilar bor” (@kunlik_ishlar_24), 5,501 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/kunlik_ishlar_24.
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.