Telegram RegisterThe public register of Telegram
Telegram profile photo for Usmanovfck

Channel

Usmanovfck

@usmanovfck1

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

37,306subscribers

+1,651 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001586179039
TypeChannel
Username@usmanovfck1
Created16 September 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live6 November 2026
Measurements held57
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/usmanovfck1

Topic

Ecommerce storefront — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Growth

35,10037,53736,318.56 August 2026 — 35,655 subscribers7 August 2026 — 35,650 subscribers8 August 2026 — 35,627 subscribers9 August 2026 — 35,608 subscribers9 August 2026 — 35,598 subscribers10 August 2026 — 35,583 subscribers11 August 2026 — 35,571 subscribers13 August 2026 — 35,555 subscribers14 August 2026 — 35,539 subscribers15 August 2026 — 35,520 subscribers17 August 2026 — 35,493 subscribers18 August 2026 — 35,449 subscribers19 August 2026 — 35,451 subscribers20 August 2026 — 35,361 subscribers21 August 2026 — 35,333 subscribers22 August 2026 — 35,298 subscribers24 August 2026 — 35,267 subscribers25 August 2026 — 35,251 subscribers26 August 2026 — 35,242 subscribers27 August 2026 — 35,228 subscribers28 August 2026 — 35,218 subscribers29 August 2026 — 35,209 subscribers30 August 2026 — 35,206 subscribers31 August 2026 — 35,195 subscribers1 September 2026 — 35,190 subscribers2 September 2026 — 35,175 subscribers4 September 2026 — 35,169 subscribers6 September 2026 — 35,133 subscribers9 September 2026 — 35,100 subscribers12 September 2026 — 36,501 subscribers14 September 2026 — 37,036 subscribers15 September 2026 — 37,180 subscribers17 September 2026 — 37,537 subscribers27 September 2026 — 37,171 subscribers5 October 2026 — 37,170 subscribers9 October 2026 — 37,132 subscribers13 October 2026 — 37,075 subscribers14 October 2026 — 37,067 subscribers16 October 2026 — 37,072 subscribers17 October 2026 — 37,073 subscribers19 October 2026 — 37,070 subscribers20 October 2026 — 37,071 subscribers21 October 2026 — 37,056 subscribers22 October 2026 — 37,148 subscribers23 October 2026 — 37,171 subscribers24 October 2026 — 37,188 subscribers25 October 2026 — 37,187 subscribers28 October 2026 — 37,205 subscribers29 October 2026 — 37,203 subscribers30 October 2026 — 37,207 subscribers31 October 2026 — 37,206 subscribers1 November 2026 — 37,222 subscribers2 November 2026 — 37,224 subscribers3 November 2026 — 37,258 subscribers4 November 2026 — 37,271 subscribers5 November 2026 — 37,282 subscribers6 November 2026 — 37,306 subscribers37,3066 August 20266 November 2026
57 measurements spanning 93 days, net +1,651. 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 34,734–37,903 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 57
Measured (UTC)SubscribersChange
6 Nov 2026, 23:5637,306+24
5 Nov 2026, 22:5037,282+11
4 Nov 2026, 22:3837,271+13
3 Nov 2026, 21:5437,258+34
2 Nov 2026, 19:1837,224+2
1 Nov 2026, 20:5737,222+16
31 Oct 2026, 21:5837,206-1
30 Oct 2026, 19:1837,207+4
29 Oct 2026, 16:4437,203-2
28 Oct 2026, 18:5837,205+18
25 Oct 2026, 15:1637,187-1
24 Oct 2026, 18:5037,188+17
23 Oct 2026, 17:3037,171+23
22 Oct 2026, 16:5737,148+92
21 Oct 2026, 09:4637,056-15
20 Oct 2026, 06:3837,071+1
19 Oct 2026, 03:0437,070-3
17 Oct 2026, 23:5037,073+1
16 Oct 2026, 20:4637,072+5
14 Oct 2026, 22:2737,067first reading

Engagement

144 posts held, back to 24 July 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 184 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
10.6%
avg views ÷ 37,306 subscribers
Avg views / post
3,960
37 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
37
of 144 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 held144 (24 July 2026 – 5 November 2026)
Views total146,490
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 23:23 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

Video runtime
4m 45s
Average length
22s

Measured directly from 13 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Recent posts

Telegram’s own ‘edited’ marker: 6 of 37 posts held from the last 30 days (16.2%) 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, 15:20 UTC≈1,910 viewsread 6 November 2026

ОТПРАВКИ 🔪 Пуховики. Отправки намечены с 10 по 15 чисел ноября, у нас произошли задержки с утеплителем так как заказывали с другой страны, все пуховики мы отшиваем в РФ, так что больше задержек с ними быть не может, за ожиданием положим кое-что приятное Новая коллекция. Мы активно ждем вещи, большую часть производили в Китае и она уже едет к нам, то что отшиваем в РФ в процессе производства Остальные вещи. Доступн…

3 Nov 2026, 14:04 UTC≈3,300 viewsread 6 November 2026

⚫ Скидки заканчиваются сегодня в 23:59

31 Oct 2026, 12:58 UTC≈4,830 viewsread 6 November 2026
Photo

SALE 50% [USMANOVFCK] ДОСТУПНО ДЛЯ ЗАКАЗА PROMO CODE: AUTUMN *50%-30% 31.10-01.11* *30%-20% 02.11-03.11* ⚫Моментальная отправка⚫ FUCKCLOTHING.RU

30 Oct 2026, 19:38 UTC≈4,180 viewsread 6 November 2026

AUTUMN SALE 50% ⚫ [USMANOVFCK FW26] SALE 50% Свитера, Кепки, Боксеры, Перчатки SALE 40% Джинсы, Шортты SALE 30% Худи, Тишки, Лонги, Штаны, Бомбера, Пуховики, Куртки ОТПРАВКА 2-4 РАБОЧИХ ДНЯ USMANOVFCK…AUTUMN SALE 50% • FW26 NO FUTURE • 31.10 • 16:00

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

Posts edited after publishing

@usmanovfck1 edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
10 September 2026
Most recent edit
5 October 2026

Posts recorded as deleted after publishing

We recorded 20 posts on @usmanovfck1 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
17 August 2026
Most recent seen missing
26 October 2026
Median time before seen missing
26 hours
Seen missing in the last 30 days
4

Mentions

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

“Usmanovfck” (@usmanovfck1), 37,306 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/usmanovfck1.

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.