Telegram RegisterThe public register of Telegram

Channel

Umid Gafurov's Blog

@gafurovumid

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

4,789subscribers

-15 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001128536643
TypeChannel
Username@gafurovumid
Created13 August 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/gafurovumid

Topic

Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 88% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@gafurovumid/1074 · this entry29 Jul 2023, 19:12 UTC@trolluz/1146930 Jul 2023, 07:27 UTC1.0012 hours
@gafurovumid/1079 · this entry5 Aug 2023, 13:15 UTC@trolluz/114965 Aug 2023, 13:16 UTC1.00under a minute
@gafurovumid/1085 · this entry19 Mar 2024, 07:19 UTC@trolluz/1213319 Mar 2024, 17:47 UTC1.0010 hours
@gafurovumid/1092 · this entry26 Feb 2026, 18:52 UTC@trolluz/1357726 Feb 2026, 18:54 UTC1.002 minutes
@gafurovumid/1096 · this entry8 May 2026, 17:43 UTC@trolluz/136808 May 2026, 17:50 UTC1.008 minutes
@gafurovumid/1099 · this entry8 May 2026, 17:49 UTC@trolluz/136838 May 2026, 17:51 UTC1.0072 seconds
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@trolluz6 (6/6 hand-verifiable sample passed)1.005 minutesthis entry (60)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 11 comparable posts for this entry, running 29 July 2023 to 22 June 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 3, the earliest publisher we hold is @fuqarolar_uz. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

4,7894,8044,796.55 August 2026 — 4,804 subscribers6 August 2026 — 4,804 subscribers9 August 2026 — 4,800 subscribers12 August 2026 — 4,789 subscribers5 August 202612 August 2026
4 measurements spanning 6 days, net -15. 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 4,787–4,806 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 05:564,789-11
9 Aug 2026, 00:554,800-4
6 Aug 2026, 03:504,804no change
5 Aug 2026, 22:004,804first reading

Engagement

17 posts held, back to 29 July 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof 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 17 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

3,086 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 72.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁2,24072.6%
👍76024.6%
🤬622.01%
👎240.778%

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

Measured over the 17 most recent posts we hold, published 29 July 2023 to 29 June 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

29 Jun 2026, 09:18 UTC≈1,860 views72 reactionsread 12 August 2026
Photo

Startaper hayotini tasvirlashga harakat qildim. - Попробовал изобразить жизнь стартапера.

😁64👍8

22 Jun 2026, 07:03 UTC≈2,700 views9 reactionsread 12 August 2026
Forwarded from @UzGeeksCommunityPhoto

Assalom alaykum!!! UzGeeks'da Startup kuni! 📆 27-iyun, shanba kuni Toshkent shahri Raqamli texnologiyalar vazirligi binosida "UzGeeks June2026 Startup Day Meetup" bo'lib o'tadi. Ushbu tadbirda birinchi speakerimiz: 1️⃣ Startaper bo'la ko'rmang! - Umid Gafurov (Founder @ tirikchilik.uz, troll.uz) 🕰 Meetup odatiy ravishda bepul bo'lib, soat 14:00 da boshlanadi, unda qatnashish uchun UzGeeks saytida ro'yxatdan o'tish

👍8👎1

8 May 2026, 17:49 UTC≈65,500 views31 reactionsread 12 August 2026

«Faqat ikki narsadan qochib qutulib bo'lmaydi — o'lim va soliqlardan» (Franklin) Soliq qoʻmitasi (Davlat) tomonidan kutilgan qadam. Bu vaqt kelishi va blogerlar (ijodkorlar) bozori tizimlashtirilishi haqida bir necha bor aytilgan edi. Bir narsani tushunish muhim: aksariyat blogerlar soliq toʻlashga va qonuniy ishlashga mutlaqo qarshi emas. Muammo amaldagi mexanizmlar va reglamentlarda. Ular kreativ soha vakillari u

👍24😁4🤬2👎1

8 May 2026, 17:43 UTC≈2,120 views16 reactionsread 12 August 2026
Forwarded from @soliqnews

#uchrashuv Soliq qoʻmitasida blogerlar bilan uchrashuv boʻlib oʻtdi Blogerlar faoliyatini oʻrganish doirasida mazkur sohaning eng faol 110 nafar vakillari roʻyxati shakllantirildi. Tahlil natijalariga koʻra, ulardan 55 nafari oʻzini oʻzi band qilgan shaxs sifatida, 33 nafari yakka tartibdagi tadbirkor sifatida roʻyxatdan oʻtgan, qolgan 22 nafari esa jismoniy shaxs maqomida faoliyat yuritmoqda. Bunday holat blogerl

😁9👍5👎1🤬1

7 May 2026, 16:00 UTC≈2,940 views59 reactionsread 12 August 2026
Video

Tadbirkorlikni qiyin deb yurganlar... startup qilib ko'ringlar :) — Те, кто думал, что бизнесом заниматься сложно... попробуйте пойти в стартап (:

😁53👍6

10 Mar 2026, 20:43 UTC≈47,800 views85 reactionsread 12 August 2026
Video message

Video message, posted without a caption

😁55👍30

26 Feb 2026, 18:58 UTC≈9,970 views72 reactionsread 12 August 2026

Meni vzlom qilishmadi :) - Меня не взломали :)

😁57👍12🤬3

26 Feb 2026, 18:52 UTC≈65,400 views86 reactionsread 12 August 2026

namespace Opportunity.Startup.Core; using System; using System.Collections.Generic; using System.Linq; using System.Threading.Tasks; /* * Hiring: Interesting Startup (Fintech Experience ++ ) * Role: Middle C# Developer (Full-time) * Location: Tashkent Center (Office Preferred) */ public class CareerPath : IStartupVibe { private const string TargetEmail = "umidgafurov@gmail.com"; public async Task Initi

😁54👍24🤬7👎1

20 Mar 2024, 02:40 UTC≈20,500 views351 reactionsread 12 August 2026
Photo

Ilgari men ham vatanparvarlik bu - bayroq bilan rasmga tushish deb o’ylar edim. Yosh edim :) 9 yil oldingi rasmlar. - Раньше я тоже думал, что патриотизм это фотографироваться с флагом. Молодой был совсем :) Фото 9 летней давности. @gafurovumid

😁284👍60🤬7

19 Mar 2024, 07:19 UTC≈81,500 views524 reactionsread 12 August 2026

O’g’limga pultda yuradigan mashina olib berdim. 360 gradusga aylanadi, tokdan quvvat oladi. Juda yoqdi. O’g’lim hali o’ynab ko’rmadi. Endi unga vertolyot olib bermoqchiman. - Купил сыну радиоуправляемую машину. Вращается на 360 градусов, заряжается от розетки. Очень доволен. Сын еще не играл. Теперь хочу купить ему вертолет. @gafurovumid

😁493👍31

8 Feb 2024, 12:11 UTC≈19,100 views138 reactionsread 12 August 2026
Video message

Video message, posted without a caption

😁101👍37

31 Jan 2024, 19:10 UTC≈83,800 views175 reactionsread 12 August 2026
Video message

Video message, posted without a caption

😁148👍15🤬10👎2

Showing the 12 most recent of 17 posts we hold for @gafurovumid. 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.

Citation-graph rank

Citation-graph rank — 1,090,267 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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

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

“Umid Gafurov's Blog” (@gafurovumid), 4,789 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/gafurovumid.

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.