5 Aug 2026, 12:59 UTC36 viewsread 9 August 2026
Бугун, ҳозир сен ҳам ер остида бўлишинг мумкин эди, аммо устида юрибсан. Демак, Аллоҳ сенга имкон бермоқда. @qaydburchak
Channel
Қайд burchak
@qaydburchak
On this record: Growth · Engagement · Posts · Citations · Cite this entry
114subscribers
-3 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 | -1001780864088 |
|---|---|
| Type | Channel |
| Username | @qaydburchak |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/qaydburchak |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 05:53 | 114 | -1 |
| 15 Aug 2026, 09:55 | 115 | -2 |
| 9 Aug 2026, 05:02 | 117 | no change |
| 7 Aug 2026, 05:07 | 117 | first reading |
Engagement
20 posts held, back to 4 March 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 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 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
19 Jul 2026, 22:13 UTC92 viewsread 9 August 2026
Мен сезгандим, мен кутгандим!) Ўзимизни қардош, диндош жамоалар чиқиб кетганидан сўнг шартта Испания бўвогандим, билганим билган мениям!)))
19 Jul 2026, 21:39 UTC92 viewsread 9 August 2026
Овора бўлиб тўп тепгунча боксга тушиб қўяверишмабди.)
19 Jul 2026, 20:57 UTC92 viewsread 9 August 2026
Зерикарли. Эээээээээ.
13 Jun 2026, 18:33 UTC156 viewsread 9 August 2026
Баъзи нарсаларнинг ечими жуда ҳам оддий ва соддалигидан ҳатто хаёлимизга ҳам келмайди. Билгандан кейин эса “Наҳотки шунчалик оддий бўлса, шу холосмиди?!” деб ҳайратда қоламиз.
26 May 2026, 13:30 UTC191 viewsread 9 August 2026
Мен фақирни ҳам дуоларингизда эслаб қўйинглар..
22 May 2026, 05:41 UTC211 viewsread 9 August 2026
{إِنَّا لِلّهِ وَإِنَّـا إِلَيْهِ رَاجِعونَ} 2025-йилнинг 22-майида бобомдан айрилиб қолгандик. Бугун эса укалари ҳам вафот этдилар. Субҳаналлоҳ… Аллоҳ уларни раҳматига олсин, барча гуноҳларини афв айласин, Жаннатнинг энг олий табақаларидан жой берсин, қабрларини нурга тўлдирсин. 5-Зулҳижжа, 1447 | 22.05.26
30 Apr 2026, 06:31 UTC231 viewsread 9 August 2026
Бир замонлар сиз буюк зотларга тавсия қилган китобим ваниҳоят ўзбек китобхонларига тақдим қилинибди. https://t.me/+bsNy14E_R78yZjA6
1 Apr 2026, 09:44 UTC232 viewsread 9 August 2026
#nazm Sensin Hiç bitmeyen özlemim, Kalbimdeki sözlerim, Çiçek açan gözlerim… Sensin yârim, hep Sensin. Hiç dinmeyen özlemim, Asi sevdam, öz derin, Aşkla yazılmış yemin… Sensin yârim, tek Sensin. Kucağımın güneşi, Kalbimin ince işi, Ruhumu saran eşi… Sensin yârim, bir Sensin. Varlığına hayranım, Canıma can katanım, “İyi ki” dediğim yârim… Sensin benim, ben Sensin. 01.04.2026 Andijon
1 Apr 2026, 09:41 UTC165 viewsread 9 August 2026
#nazm xoʻrlik qilganimizgayam ancha boʻb ketibdi-ya? Bugun turkchasidan bir olmaymizmi, oʻrtoqlar?)
27 Mar 2026, 16:49 UTC190 viewsread 9 August 2026
#duo Аллоҳим, агар шу ҳаётимдан, шу турмуш тарзимдан ва мана шу барчаси ичидаги мен ожиз қулингдан рози бўлсанг.. Эй Роббим, Сенинг ризонг, муҳаббатинг, Сендан тиланиб сўрайдиганим энг олий Жаннат мана шулар ичида ё шулар орқали бўлса ва мана шулар ичида жоним чиқиб кетса-ю юқоридагиларнинг барчасини насиб қилсанг, ўтинаман Роббим мени ҳам тўлақонли рози қилиб, таслим қилиб қўйгин, жамики қораликларни ичимдан чиқари…
27 Mar 2026, 16:36 UTC143 viewsread 9 August 2026
#duo Аллоҳим, менга Ўзинг кифоя қил, менга Ўзинг вакил бўл, амийн!
Showing the 12 most recent of 20 posts we hold for @qaydburchak. 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Қайд burchak” (@qaydburchak), 114 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/qaydburchak.
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.