Telegram RegisterThe public register of Telegram
Telegram profile photo for SUDLARDA RAQAMLASHTIRISH

Channel

SUDLARDA RAQAMLASHTIRISH

@raqamli_sud

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

1,307subscribers

+234 since we began measuring on 26 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1004320505815
TypeChannel
Username@raqamli_sud
Created26 August 2026 — measured — dated from the channel’s first post
First recorded26 August 2026
Last confirmed live23 October 2026
Measurements held13
Confirmed unchanged1 time, most recently 23 October 2026
On Telegramt.me/raqamli_sud

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 18 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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

1,0731,3151,19426 August 2026 — 1,073 subscribers27 August 2026 — 1,123 subscribers29 August 2026 — 1,295 subscribers2 September 2026 — 1,300 subscribers5 September 2026 — 1,304 subscribers10 September 2026 — 1,310 subscribers14 September 2026 — 1,309 subscribers18 September 2026 — 1,313 subscribers27 September 2026 — 1,311 subscribers5 October 2026 — 1,315 subscribers12 October 2026 — 1,311 subscribers20 October 2026 — 1,309 subscribers23 October 2026 — 1,307 subscribers1,30726 August 202623 October 2026
13 measurements spanning 58 days, net +234. 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 1,037–1,351 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Oct 2026, 22:271,307-2
20 Oct 2026, 17:461,309-2
12 Oct 2026, 04:021,311-4
5 Oct 2026, 12:561,315+4
27 Sept 2026, 14:551,311-2
18 Sept 2026, 04:591,313+4
14 Sept 2026, 00:381,309-1
10 Sept 2026, 17:391,310+6
5 Sept 2026, 23:161,304+4
2 Sept 2026, 05:421,300+5
29 Aug 2026, 21:561,295+172
27 Aug 2026, 02:431,123+50
26 Aug 2026, 22:151,073first reading

Engagement

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

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.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 2 of the 3 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 3 most recent posts we hold, published 26 August 2026 to 26 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

26 Aug 2026, 11:41 UTC≈1,570 views1 reactionsread 26 August 2026
Photo

⚡️ YANGI INTERAKTIV XIZMAT Oliy sudning interaktiv xizmatlari portalida sun’iy intellekt texnologiyalariga asoslangan “Sud muhokamasining taxminiy natijasi hamda sarflanadigan xarajatlarni hisoblash” yangi interaktiv xizmati ishga tushirildi. Yangi xizmat orqali foydalanuvchilar sudga murojaat qilishdan oldin ish holatiga oid zarur ma’lumotlarni kiritgan holda, sun’iy intellekt yordamida nizoning huquqiy jihatlarin…

❤1

26 Aug 2026, 11:22 UTC≈1,320 views1 reactionsread 26 August 2026
Photo

O‘ZBEKISTON RESPUBLIKASI OLIY SUDI RAQAMLI TEXNOLOGIYALAR VA SUN’IY INTELLEKT DEPARTAMENTI KANALIGA XUSH KELIBSIZ! Bu yerda siz sud tizimini raqamlashtirish bo‘yicha amalga oshirilayotgan ishlar haqida birlamchi manbadan xabardor bo‘lib borasiz. Kanal orqali biz: 🔹 yangi interaktiv xizmatlar 🔹 “Raqamli sud” konsepsiyasi doirasidagi loyihalar 🔹 sudlarda sun’iy intellekt texnologiyalarini joriy etish 🔹 eng muhimi, bu…

❤1

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 4 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.

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

“SUDLARDA RAQAMLASHTIRISH” (@raqamli_sud), 1,307 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/raqamli_sud.

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.