Telegram RegisterThe public register of Telegram
Telegram profile photo for Узбекский ФинТех

Channel

Узбекский ФинТех

@uzbekfintech

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

6,637subscribers

+288 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001698528627
TypeChannel
Username@uzbekfintech
DescriptionАналитика, экспертные материалы и новости финансовых технологий, банков, электронных платежных систем. По всем вопросам сотрудничества обращайтесь к @tezchoparCEO
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 live5 November 2026
Measurements held24
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/uzbekfintech

Topic

Technology — 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 75% 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 the other topics.

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 2 other registered channels. They sit inside a group of 4 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 (4 of the pairs behind the counts below)
Posted firstThenOverlapGap
@uzbekretail/181344 Aug 2026, 04:31 UTC@uzbekfintech/4164 · this entry4 Aug 2026, 04:31 UTC1.00under a minute
@uzbekfintech/4169 · this entry5 Aug 2026, 04:35 UTC@uzbekretail/181415 Aug 2026, 04:35 UTC1.00under a minute
@uzbekfintech/4173 · this entry6 Aug 2026, 05:27 UTC@uzbekretail/181496 Aug 2026, 05:31 UTC1.005 minutes
@uzbekfintech/4157 · this entry3 Aug 2026, 05:30 UTC@UzbBanking/9513 Aug 2026, 06:26 UTC1.0056 minutes
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@uzbekretail11 (8/8 hand-verifiable sample passed)1.002 minutesthis entry (8–3)
@UzbBanking5 (5/5 hand-verifiable sample passed)1.002 minutesthis entry (3–2)

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. 1 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 29 comparable posts for this entry, running 2 August 2026 to 7 August 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 4, the earliest publisher we hold is @uzbekfintech — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · 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 3 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

6,3496,6376,4936 August 2026 — 6,349 subscribers7 August 2026 — 6,350 subscribers10 August 2026 — 6,356 subscribers12 August 2026 — 6,369 subscribers16 August 2026 — 6,372 subscribers20 August 2026 — 6,389 subscribers23 August 2026 — 6,398 subscribers26 August 2026 — 6,410 subscribers29 August 2026 — 6,420 subscribers1 September 2026 — 6,429 subscribers6 September 2026 — 6,449 subscribers11 September 2026 — 6,469 subscribers15 September 2026 — 6,466 subscribers26 September 2026 — 6,505 subscribers5 October 2026 — 6,515 subscribers11 October 2026 — 6,535 subscribers14 October 2026 — 6,548 subscribers18 October 2026 — 6,553 subscribers21 October 2026 — 6,564 subscribers24 October 2026 — 6,570 subscribers27 October 2026 — 6,574 subscribers29 October 2026 — 6,626 subscribers2 November 2026 — 6,625 subscribers5 November 2026 — 6,637 subscribers6 August 20265 November 2026
24 measurements spanning 91 days, net +288. 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 6,306–6,680 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 24
Measured (UTC)SubscribersChange
5 Nov 2026, 07:316,637+12
2 Nov 2026, 05:286,625-1
29 Oct 2026, 23:166,626+52
27 Oct 2026, 03:216,574+4
24 Oct 2026, 00:166,570+6
21 Oct 2026, 04:316,564+11
18 Oct 2026, 03:266,553+5
14 Oct 2026, 19:096,548+13
11 Oct 2026, 13:206,535+20
5 Oct 2026, 03:376,515+10
26 Sept 2026, 13:596,505+39
15 Sept 2026, 03:016,466-3
11 Sept 2026, 07:596,469+20
6 Sept 2026, 18:396,449+20
1 Sept 2026, 23:346,429+9
29 Aug 2026, 15:346,420+10
26 Aug 2026, 16:546,410+12
23 Aug 2026, 10:566,398+9
20 Aug 2026, 04:346,389+17
16 Aug 2026, 19:466,372first reading

Engagement

85 posts held, back to 2 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 14 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
25.6%
avg views ÷ 6,637 subscribers
Avg views / post
1,700
36 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
36
of 85 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 5 November 2026
Posts held85 (2 August 2026 – 5 November 2026)
Views total61,224
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 01:07 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
≈4,320
Videos
≈182
Links
≈2,760

Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Recent posts

Telegram’s own ‘edited’ marker: 6 of 36 posts held from the last 30 days (16.7%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

5 Nov 2026, 13:03 UTC834 viewsread 6 November 2026
Photo

В Узбекистане объявили результаты CX Banking Index 2026 — исследования клиентского опыта в 34 банковских приложениях и пяти финтех-сервисах. Аналитики проверили 276 параметров: от регистрации и добавления карты до переводов, платежей и истории операций. Главный вывод — стандарты удобства меняются быстро. То, что год назад выделяло приложение, становится нормой, а привычное решение может превратиться в барьер, если к…

5 Nov 2026, 12:31 UTC≈1,030 viewsread 6 November 2026
Photo

Узбекистанская компания OSON Holding представила платформу OSON X на Dubai Fintech Summit 2026 На международном Dubai Fintech Summit 2026 группа OSON Holding презентовала свой ключевой международный проект — финансовую платформу OSON X для выходцев из Центральной Азии, которые живут и работают в Эмиратах. Dubai FinTech Summit прошел 2–3 ноября в Дубае, его организует Международный финансовый центр Дубая (DIFC). По …

5 Nov 2026, 11:58 UTC≈1,010 viewsread 6 November 2026
Photo

Market Yandex Go прекращает работы моделей FBS и DBS в Узбекистане E-com сервисы в Yandex Go сосредоточатся на экспресс-доставке. Приобретать различные продукты и товары в приложении Yandex Go можно будет только с экспресс-доставкой. Продажа товаров через витрину Market по моделям FBS и DBS будет прекращена c 10 ноября. Служба поддержки при этом и дальше продолжит помогать пользователям и партнёрам по вопросам зак…

5 Nov 2026, 07:21 UTC≈3,430 viewsread 6 November 2026
Photo

⏺ На фоне новостей об утечках данных C7 Cybersecurity (Cerberus) предлагает бизнесу аудит кибербезопасности почти по себестоимости. В последние недели в сети одна за другой появляются новости об утечках и взломах. В открытый доступ попадают ПИНФЛ, паспортные данные, адреса и номера телефонов граждан. Под угрозой не только госсистемы, но и частный бизнес. Любая уязвимость может обернуться потерей данных клиентов, штр…

5 Nov 2026, 06:29 UTC≈1,190 viewsread 6 November 2026
Photo

Yandex Uzbekistan планирует запустить доставку заказов роботами в Ташкенте до конца 2026 года До конца 2026 года в Ташкенте планируется запустить доставку продуктов, готовой еды и повседневных товаров из Yandex Lavka с помощью автономных роботов. Сейчас Yandex Uzbekistan проводит необходимые испытания устройств и готовит их к работе в городской среде. Роботов планируют использовать на маршрутах протяжённостью до дв…

5 Nov 2026, 06:04 UTC≈1,270 viewsread 6 November 2026
Photo

eMaktab при поддержке Uzum Bank запустили сервис школьных платежей В Узбекистане стал доступен сервис eMaktab Платежи для онлайн-оплаты обучения и дополнительных школьных услуг. На первом этапе он доступен частным школам, подключённым к eMaktab. Родители могут оплачивать обучение, питание и дополнительные занятия картой любого банка через сайт или приложение, без наличных и визитов в бухгалтерию. В сервисе можно от…

5 Nov 2026, 04:35 UTC≈1,150 viewsread 6 November 2026
Photo

На Ташкент приходится 45% кредитов и 76% депозитов банков На город Ташкент на 1 октября 2026 года приходилось 297,5 трлн сумов банковских кредитов, или 45,1% их общего объема, и 383 трлн сумов депозитов, или 76,4% всех средств, размещенных в банках страны. Об этом сообщает Центральный банк Узбекистана. Особенно высока концентрация средств компаний. В столице размещено 275,8 трлн сумов депозитов юридических лиц, что…

5 Nov 2026, 04:01 UTC≈1,250 viewsread 6 November 2026
Photo

ЦБП Бизнес от Fido Biznes: онлайн-онбординг юридических лиц без замены АБС Как банку перевести подключение корпоративных клиентов в цифровой формат, сохранив комплаенс-проверки и существующую ИТ-инфраструктуру? ЦБП Бизнес — платформа Fido Biznes для цифрового корпоративного банковского обслуживания. Она позволяет организовать дистанционное подключение юридических лиц и предоставить им доступ к банковским сервисам в…

4 Nov 2026, 14:12 UTC≈2,360 viewsread 6 November 2026
Photo

Какие бонусы и привилегии особенно важны для вас в повседневной жизни? Поделитесь мнением в коротком опросе Скидки на переводы, кешбэк на каждый день или доступ к подпискам и сервисам? Расскажите, какие предложения вы замечаете, чем охотно пользуетесь, а что обычно остаётся без внимания. Ваши ответы помогут лучше понять, какие бонусы, скидки и привилегии действительно нужны в повседневной жизни и как сделать их пол…

4 Nov 2026, 12:50 UTC≈1,060 viewsread 6 November 2026
Forwarded from @uzbekvcPhoto

McKinsey расширяет присутствие в Узбекистане и Центральной Азии Международная консалтинговая компания McKinsey & Company намерена расширить свою деятельность в Центральной Азии, уделив особое внимание развитию бизнеса в Узбекистане. В рамках этого процесса глобальный управляющий партнер компании Боб Стернфелс посетил Ташкент. McKinsey работает с государственными, частными и общественными организациями Центральной …

4 Nov 2026, 11:29 UTC≈1,080 viewsread 6 November 2026
Forwarded from @uzbekretailPhoto

70% онлайн-покупателей в Узбекистане хотя бы раз приобретали товары с рук Большинство жителей Узбекистана, совершающих покупки через интернет, уже имеют опыт приобретения товаров у частных продавцов. Согласно исследованию ресейл-платформы Listee и аналитического агентства ORO, 70% онлайн-покупателей хотя бы один раз приобретали товары с рук. Наиболее востребованными категориями оказались одежда, обувь, сумки и элек…

4 Nov 2026, 10:59 UTC≈1,240 viewsread 6 November 2026
Photo

Каждый месяц банки и телекомы Узбекистана закрывают вакансии по ИБ — и не могут найти людей. Не потому что их нет. Потому что их никто не готовит. Мы обучаем действующих специалистов крупнейших компаний страны. Знаем, каких людей не хватает, и что рынок реально ищет. Вывод один: специалист по информационной безопасности — самая востребованная точка входа в IT для тех, кто начинает с нуля. Порог ниже, чем в разработ…

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

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Spot.uz – бизнес и технологии
@spotuz · 27,449
Telegram ranks this channel #12 of 78 here — alongside 77 others — read 11 September 2026
Kapital.uz
@KPTLUZ · 22,307
Telegram ranks this channel #17 of 85 here — alongside 84 others — read 21 September 2026
The Tech
@thetechkz · 27,338
Telegram ranks this channel #27 of 95 here — alongside 94 others — read 11 September 2026
Kaspi.kz
@kaspikz · 26,756
Telegram ranks this channel #45 of 89 here — alongside 88 others — read 11 September 2026
payme
@payme_uz · 55,063
Telegram ranks this channel #53 of 66 here — alongside 65 others — read 21 August 2026
Финансовый анализ
@fin_analytics · 41,588
Telegram ranks this channel #60 of 87 here — alongside 86 others — read 29 August 2026
Creative Asia
@we_project · 72,664
Telegram ranks this channel #74 of 90 here — alongside 89 others — read 20 August 2026

This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Узбекский ФинТех” (@uzbekfintech), 6,637 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/uzbekfintech.

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.