Telegram RegisterThe public register of Telegram
Telegram profile photo for Уруз фармит

Channel

Уруз фармит

@uruzfarmit

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

704subscribers

+101 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003042591994
TypeChannel
Username@uruzfarmit
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live31 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/uruzfarmit

Growth

603704653.57 August 2026 — 603 subscribers8 August 2026 — 603 subscribers8 August 2026 — 613 subscribers16 August 2026 — 646 subscribers24 August 2026 — 662 subscribers31 August 2026 — 704 subscribers7 August 202631 August 2026
6 measurements spanning 24 days, net +101. 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 588–719 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 17:13704+42
24 Aug 2026, 03:49662+16
16 Aug 2026, 21:52646+33
8 Aug 2026, 13:46613+10
8 Aug 2026, 03:05603no change
7 Aug 2026, 17:34603first reading

Engagement

16 posts held, back to 21 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.

ERR · 30 days
43.0%
avg views ÷ 704 subscribers
Avg views / post
303
8 posts measured
Reaction rate
2.67%
reactions ÷ views · ER floor
Posts in window
8
of 16 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. It is computed over the 5 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held16 (21 July 20267 August 2026)
Views total2,424
Reactions total46
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:05 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.

Reaction mix

167 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 31.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53845666632428540995331.7%
custom 53777518729940289514627.5%
custom 53844042962991969203319.8%
custom 53841215500121644992313.8%
custom 5384355380916663884127.19%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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

Measured over the 16 most recent posts we hold, published 21 July 2026 to 7 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

7 Aug 2026, 21:37 UTC149 viewsread 8 August 2026
Photo

Получилось, теперь лонгуем? 😁

7 Aug 2026, 21:14 UTC174 views3 reactionsread 8 August 2026
Photo

Как нереализованный пнл реализовать?

custom 53777518729940289513

7 Aug 2026, 16:37 UTC248 viewsread 8 August 2026
Photo

Вышел отсюда +90$ Если на корейской сессии дадут >40% перезайду

7 Aug 2026, 12:59 UTC275 views6 reactionsread 8 August 2026
Photo

Залился сюда под 39% в монетах 1 к 10 Цель флипнуть пару %.

custom 53777518729940289514custom 53841215500121644991custom 53845666632428540991

6 Aug 2026, 07:06 UTC375 views4 reactionsread 8 August 2026
Photo

После делистинга с Бинанса в этом токене нашли новые технологии 😁 Пора на дно

custom 53841215500121644992custom 53845666632428540992

4 Aug 2026, 09:54 UTC445 views16 reactionsread 8 August 2026
Photo

)))

custom 53777518729940289515custom 53845666632428540995custom 53844042962991969204custom 53843553809166638842

3 Aug 2026, 21:15 UTC451 views17 reactionsread 8 August 2026
Photo

НЕ ВИДЕЛ НИ ОДНОГО ИНФЛА КТО КОЛЛИЛ ЭТО 🤓 Вынесли с пацанами в приватке спред 300% на токене $CATE. Ещё и выход был 5-6% в обратную сторону Монетка ДОСТУПНА для СНГ Сам лился под 40%. Всем гн Вступить в приватку

custom 53841215500121644997custom 53777518729940289514custom 53844042962991969204custom 53845666632428540992

29 Jul 2026, 09:40 UTC659 views7 reactionsread 8 August 2026
Photo

Решил закрыть

custom 53844042962991969205custom 53843553809166638841custom 53845666632428540991

26 Jul 2026, 11:51 UTC900 views31 reactionsread 8 August 2026
Photo

Ставьте побольше дизлайков, так коллы лучше залетают 😁

custom 537775187299402895116custom 53845666632428540999custom 53844042962991969203custom 53843553809166638842custom 53841215500121644991

26 Jul 2026, 10:18 UTC654 views20 reactionsread 8 August 2026
Photo

Esports?

custom 53777518729940289519custom 53844042962991969207custom 53845666632428540993custom 53843553809166638841

24 Jul 2026, 19:23 UTC674 views15 reactionsread 8 August 2026
Photo

Послушал Енджоя и сделал наоборот

custom 53845666632428540999custom 53843553809166638844custom 53844042962991969202

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

Mentions

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

“Уруз фармит” (@uruzfarmit), 704 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/uruzfarmit.

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.