Telegram RegisterThe public register of Telegram
Telegram profile photo for Shodi Otamurod

Channel

Shodi Otamurod

@Shodi_Otamurod

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

304subscribers

+1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001745929867
TypeChannel
Username@Shodi_Otamurod
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 September 2026
Measurements held4
Confirmed unchanged2 times, most recently 16 September 2026
On Telegramt.me/Shodi_Otamurod

Topic

Literature — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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

3033053046 August 2026 — 303 subscribers6 August 2026 — 303 subscribers14 August 2026 — 305 subscribers8 September 2026 — 304 subscribers6 August 20268 September 2026
4 measurements spanning 33 days, net +1. 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 303–305 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 13:58304-1
14 Aug 2026, 17:08305+2
6 Aug 2026, 22:32303no change
6 Aug 2026, 08:17303first reading

Engagement

9 posts held, back to 29 July 2026the 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 9 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

61 reactions across 9 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍61100.0%

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

Measured over the 9 most recent posts we hold, published 29 July 2026 to 4 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.

Recent posts

4 Aug 2026, 07:42 UTC114 views4 reactionsread 6 August 2026
File

Bilaman, siz... ✍️Shodi OTAMUROD 🎙Muallif o'qigan @Shodi_Otamurod

👍4

Signed Шоди Отамурод

3 Aug 2026, 17:08 UTC129 views13 reactionsread 6 August 2026
Photo

ЁРУҒЛИК туркумидан ТИЛАГИМ Сенинг шодлигингга шерик бу олам, Қувонч кўзёшингга ҳеч бир изоҳ йўқ. Йўлингни ёритиб турибди Эгам, Ҳаёт имлосига биздан ислоҳ йўқ. Қошингдан Худойим бир қалам тортган, Жонинг не аламлар тортган, биламан. Йиғласанг, оҳингдан куяди бўғзим, Сен доим бахтли бўл, кулсанг куламан. Мудом аямасин нурли сўзини, Назарин олмасин сендан Худойим. Қаламингдан ёруғ бўлдим, азизим, Қадамингдан қутлуғ

👍13

Signed Шоди Отамурод

3 Aug 2026, 12:25 UTC78 views8 reactionsread 6 August 2026
Forwarded from @yozuvchilar_uzPhoto

BILAMAN, SIZ... Bog‘laring bor, daraxtlarni quchgim kelsa, Tog‘laring bor, qanot qoqib uchgim kelsa, Buloqlardan bir zilol suv ichgim kelsa, Qo‘llarimga kosa tutib turgaydirsiz, Bilaman, siz Vatanni chin sevgaydirsiz. Bug‘doyzordan xirmonini uydirganlar, Yurtin suyib o‘zini ham suydirganlar, Mehridan bir yuksak Vatan qurdirganlar, “Bu imorat – bizning bino” degaydirsiz, Bilaman, siz Vatanni chin sevgaydirsiz. Qish

👍8

Signed Шоди Отамурод

1 Aug 2026, 06:37 UTC210 views3 reactionsread 6 August 2026
File

#sevimli ✍Shodi Otamurod Bugun shoirning qizi Madinabonu singlimning tavallud kunlari ekan! Qizaloqni tabriklaymiz! BAXTLI BO'L, MADINABONU! @sitorabonu_audiolar

👍3

Signed Шоди Отамурод

1 Aug 2026, 04:06 UTC183 views9 reactionsread 6 August 2026
Photo

ҚИЗИМГА Лоласи сен бўлдинг мендек қоянинг, Боғимнинг хуш насим, шаббодаси – сен. Ожиз қаламимга сочинг соями, Меҳр деган сўзнинг ифодаси – сен. Бошим кўкка етган туғилганингда, Атак-чечак пайтинг суйдим, суядим. Йўлингдан тош тердим йиқилганингда, Кўзлардан, сўзлардан сени аядим. Олис йўлга чиққан катта карвондек Ёруғ манзилларни кўзлаб турибман. Бағримда – палахмон, тошини жондек Ҳозирча қўлимда ушлаб турибман.

👍9

Signed Шоди Отамурод

29 Jul 2026, 11:57 UTC109 views9 reactionsread 6 August 2026
Forwarded from @yozuvchilar_uzVideo

26-iyul kuni Qozog‘iston Respublikasining Olmaota shahrida o‘tkazilgan "Ipak yo‘li" VI Xalqaro sheʼriyat va sanʼat festivalida O‘zbekiston xalq shoirlari - Sirojiddin Sayyid, Usmon Azim, Xurshid Davron, Qoraqalpog‘iston xalq shoiri Rustam Musurmon, ijodkorlar - Qutlibeka Rahimboyeva, Salim Ashur, Sirojiddin Rauf, G‘ayrat Majid, Shodi Otamurod va Nargiza Asadovaning taqdirlanishi quvonarli bo'ldi. Shu munosabat bilan

👍9

Signed Шоди Отамурод

29 Jul 2026, 11:45 UTC89 views4 reactionsread 6 August 2026
Forwarded from @yozuvchilar_uzPhoto

Jarayondan suratlar "Ipak yo‘li" VI Xalqaro sheʼriyat va sanʼat festivali tashabbuskorlari Toshkent shahriga kelib o‘zbekistonlik adiblarga mukofotlarni topshirdi.

👍4

Signed Шоди Отамурод

29 Jul 2026, 11:45 UTC104 views8 reactionsread 6 August 2026
Forwarded from @yozuvchilar_uzPhoto

Jarayondan suratlar

👍8

Signed Шоди Отамурод

29 Jul 2026, 11:45 UTC71 views3 reactionsread 6 August 2026
Forwarded from @yozuvchilar_uz

"Ipak yo‘li" VI Xalqaro sheʼriyat va sanʼat festivali: madaniyatlar muloqoti va sheʼriyat bayrami Shu yilning 26-iyul kuni Qozog‘iston Respublikasining Olmaota shahrida o‘tkazilgan "Ipak yo‘li" VI Xalqaro sheʼriyat va sanʼat festivali jahonning turli mamlakatlaridan shoirlar, yozuvchilar, tarjimonlar, rassomlar, olimlar va madaniyat namoyandalarini birlashtirgan muhim madaniy voqeaga aylandi. Festival Xitoy,

👍3

Signed Шоди Отамурод

Showing the 9 most recent of 9 posts we hold for @Shodi_Otamurod. 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

Named by 3 registered channels — 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.

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

“Shodi Otamurod” (@Shodi_Otamurod), 304 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/Shodi_Otamurod.

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.