Telegram RegisterThe public register of Telegram
Telegram profile photo for P2P UZB

Channel

P2P UZB

@MMakeruzb

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

11,152subscribers

-1,041 since we began measuring on 19 August 2026

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

Register entry

Telegram ID-1002015180604
TypeChannel
Username@MMakeruzb
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live29 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/MMakeruzb

Growth

11,15212,19311,672.519 August 2026 — 12,193 subscribers19 August 2026 — 12,170 subscribers20 August 2026 — 12,065 subscribers22 August 2026 — 11,926 subscribers24 August 2026 — 11,832 subscribers25 August 2026 — 11,616 subscribers26 August 2026 — 11,452 subscribers27 August 2026 — 11,283 subscribers28 August 2026 — 11,187 subscribers29 August 2026 — 11,152 subscribers19 August 202629 August 2026
10 measurements spanning 10 days, net -1,041. 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 10,996–12,349 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 05:2811,152-35
28 Aug 2026, 06:2211,187-96
27 Aug 2026, 09:3511,283-169
26 Aug 2026, 06:4311,452-164
25 Aug 2026, 04:2311,616-216
24 Aug 2026, 00:1811,832-94
22 Aug 2026, 10:1911,926-139
20 Aug 2026, 22:1112,065-105
19 Aug 2026, 21:3912,170-23
19 Aug 2026, 12:4512,193first reading

Engagement

49 posts held, back to 1 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 10 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.65%
avg views ÷ 11,152 subscribers
Avg views / post
853
48 posts measured
Reaction rate
0.627%
reactions ÷ views · ER floor
Posts in window
49
of 49 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 38 of 48 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 23 August 2026
Posts held49 (1 August 202623 August 2026)
Views total40,936
Reactions total218
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken24 Aug 2026, 07:12 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
22s
Average length
7s

Measured directly from 3 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.

Reaction mix

218 reactions across 38 posts, in 6 distinct kinds. The most used accounts for 55.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥12055.0%
4219.3%
👍2712.4%
👏177.80%
🤝94.13%
😁31.38%

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

Measured over the 49 most recent posts we hold, published 1 August 2026 to 23 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 48 we hold a reading for · 2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MMakeruzb. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 49 most recent posts we hold for this entry, published 1 August 2026 to 23 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

23 Aug 2026, 02:43 UTC315 views5 reactionsread 24 August 2026
Video

Barchasiga signal berilgan kirganlar riskizga qarab savdo qiling

🔥5

22 Aug 2026, 10:16 UTC385 views3 reactionsread 24 August 2026
Photo

50 % yopdim riskizni hisobga olib savdolarizni bir qismini yoping

🔥3

22 Aug 2026, 10:16 UTC338 views4 reactionsread 24 August 2026
Photo

All TP Done Savdolarni 100% yopyapman bozor atkat qilishni boshladi

🔥4

22 Aug 2026, 09:49 UTC326 views9 reactionsread 24 August 2026
Photo

🐳 Kecha AQSh fondlari $307,5 millionlik BTC sotib oldi! ETH ETF'da $184 millionlik, SOL ETF'da $10 millionlik kirim qayd etilgan. Fondlar joriy haftada jami $1,92 milliardlik 28690 BTC sotib oldi. @mmaker_uz

🔥5👏21😁1

22 Aug 2026, 09:48 UTC297 views7 reactionsread 24 August 2026
Video

Bazi savdolarni 50% yopdim riskizni hisobga olib savdo qiling !

3👏2🔥1🤝1

22 Aug 2026, 04:45 UTC352 views4 reactionsread 24 August 2026

August, 2026 ------------------------------------- Market Type: Futures Trade Type: Position ------------------------------------- Pair: $FET/USDT Direction: LONG ⭕ Leverage: 5x - 10x ------------------------------------- 📊 Entry: 1) 0.182 (CMP) 2) 0.165 (Limit) 🟢 Take Profit: 1) 0.194 2) 0.211 3) 0.237 4) 0.259 🔴 Stop Limit: 0.1499 -------------------------------------

🔥4

22 Aug 2026, 00:20 UTC366 views5 reactionsread 24 August 2026
Photo

Likvidatsiya yana 24 soat ichida 2 B 🤔

🔥5

21 Aug 2026, 21:46 UTC364 views4 reactionsread 24 August 2026
Photo

📊 $SUI TP 1 TP 2 Done Hammaga omad !

🔥4

21 Aug 2026, 13:02 UTC397 views4 reactionsread 24 August 2026
Photo

📊 #ONDO TP 1 TP 2 TP 3 Done Hammaga omad

🔥31

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

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.

Abdurahmon Crypto
@abdurahmoncrypto · 82,694
Telegram ranks this channel #34 of 64 here — alongside 63 others — read 19 August 2026
Самарканд иш | Samarqand ish elonlar
@Samarqand_ish_bor_elonlar1 · 75,655
Telegram ranks this channel #38 of 43 here — alongside 42 others — read 19 August 2026

This channel appears in 2 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 29 August 2026 — this entry's latest reading, not the date you are reading this.

“P2P UZB” (@MMakeruzb), 11,152 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/MMakeruzb.

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.