Telegram RegisterThe public register of Telegram
Telegram profile photo for uzum em

Channel

uzum em

@uzumemm

On this record: Topic · Growth · Engagement · Stars · Posts · Citations · Telegram's recommendations · Cite this entry

22,825subscribers

+949 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001796196430
TypeChannel
Username@uzumemm
Created28 June 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/uzumemm

Topic

Personal blog — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.

Growth

21,82822,83422,3317 August 2026 — 21,876 subscribers7 August 2026 — 21,876 subscribers8 August 2026 — 21,860 subscribers8 August 2026 — 21,855 subscribers9 August 2026 — 21,837 subscribers10 August 2026 — 21,852 subscribers11 August 2026 — 21,828 subscribers12 August 2026 — 21,890 subscribers14 August 2026 — 21,880 subscribers15 August 2026 — 21,900 subscribers17 August 2026 — 21,930 subscribers18 August 2026 — 21,916 subscribers19 August 2026 — 21,919 subscribers20 August 2026 — 21,987 subscribers21 August 2026 — 22,055 subscribers23 August 2026 — 22,085 subscribers24 August 2026 — 22,076 subscribers25 August 2026 — 22,057 subscribers26 August 2026 — 22,055 subscribers27 August 2026 — 22,050 subscribers28 August 2026 — 22,058 subscribers29 August 2026 — 22,057 subscribers30 August 2026 — 22,081 subscribers31 August 2026 — 22,169 subscribers1 September 2026 — 22,221 subscribers2 September 2026 — 22,381 subscribers4 September 2026 — 22,536 subscribers6 September 2026 — 22,614 subscribers9 September 2026 — 22,664 subscribers12 September 2026 — 22,724 subscribers13 September 2026 — 22,813 subscribers15 September 2026 — 22,834 subscribers17 September 2026 — 22,825 subscribers22,8257 August 202617 September 2026
33 measurements spanning 41 days, net +949. 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 21,677–22,985 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
17 Sept 2026, 07:1522,825-9
15 Sept 2026, 09:4122,834+21
13 Sept 2026, 22:0022,813+89
12 Sept 2026, 02:5622,724+60
9 Sept 2026, 19:5922,664+50
6 Sept 2026, 14:2122,614+78
4 Sept 2026, 01:5922,536+155
2 Sept 2026, 17:5522,381+160
1 Sept 2026, 13:1622,221+52
31 Aug 2026, 11:0222,169+88
30 Aug 2026, 08:3722,081+24
29 Aug 2026, 09:4622,057-1
28 Aug 2026, 12:0822,058+8
27 Aug 2026, 13:5822,050-5
26 Aug 2026, 17:1422,055-2
25 Aug 2026, 17:1122,057-19
24 Aug 2026, 16:5622,076-9
23 Aug 2026, 02:5722,085+30
21 Aug 2026, 11:5422,055+68
20 Aug 2026, 08:5221,987first reading

Engagement

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

ERR · 30 days
50.9%
avg views ÷ 22,825 subscribers
Avg views / post
11,600
33 posts measured
Reaction rate
0%
reactions ÷ views · ER floor
Posts in window
33
of 95 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 21 of 33 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 3 September 2026
Posts held95 (30 July 20263 September 2026)
Views total383,470
Reactions total0
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 12:47 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.

Telegram Stars

Stars received
241
across the posts below
Posts paid on
63
of 95 we hold a reading for · 66%
Most on one post
56
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @uzumemm. 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 95 most recent posts we hold for this entry, published 30 July 2026 to 3 September 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

3 Sept 2026, 11:37 UTC≈1,650 viewsread 3 September 2026

մեր ամենագեղեցիկ երազանքները գտնեն մեզ ճիշտ ժամանակին..)

2 Sept 2026, 18:13 UTC≈5,510 views0 reactions1 Starread 3 September 2026

կյանքումս նենց մեկը հայտնվի, ով սթորիներիս պատասխանելու փոխարեն կստեղծի դրանք

2 Sept 2026, 10:01 UTC≈10,100 views0 reactions56 Starsread 3 September 2026

Նուշիկի ամուսնու մահվան լուրը սուտ լինի..

1 Sept 2026, 17:47 UTC≈8,840 views0 reactions6 Starsread 3 September 2026
Photo

մեր պատմությունն այսպիսի ավարտ ունենա…🦴

1 Sept 2026, 14:20 UTC≈9,370 views0 reactions1 Starread 3 September 2026

միշտ գնահատես այն, ինչ ունես. ինչ-որ մեկը տարիներ շարունակ աղոթում է, որպեսզի ունենա այն, ինչը քեզ համար արդեն սովորական է դարձել

31 Aug 2026, 20:00 UTC≈11,300 views0 reactions5 Starsread 3 September 2026

այս աշունը բոլորիս կյանքում ամենաջերմ, լուսավոր ու տաք պահերով լի լինի💗

31 Aug 2026, 14:13 UTC≈10,500 viewsread 3 September 2026

նորից սկսենք հունիս, հուլիս, օգոստոս..

31 Aug 2026, 09:17 UTC≈11,300 views0 reactions1 Starread 3 September 2026

պաշտոնապես հայտարարեմ, որ սա իմ կյանքի ամենաարագ ամառն էր

30 Aug 2026, 17:43 UTC≈11,800 views0 reactions5 Starsread 3 September 2026

ասեմ` էս անձրև չի, ամառը վերջանալու համար մեր արցունքներն են

29 Aug 2026, 15:45 UTC≈12,500 viewsread 3 September 2026

մեկը ինձ սիրի էնքան, ինչքան ես makeup products

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

Քաղաքական հումոր
@khinducicax · 1,477
#1
bahetoo?
@bahetoo · 2,300
#2
Մտ
@mtacumem · 1
#3
A11✞
@aaamore11 · 6,402
#4
aneweraofmee
@ANewEraOfMee · 901
#5
vaxenum em
@vaxenumem · 443
#6
𝐋𝐢𝐢𝐨𝐧
@LlionAA · 1,646
#7
XVII
@withhhhlovee · 1,368 (as read 19 September 2026)
#8
𝐓𝐎𝐆𝐄𝐓𝐇𝐄𝐑
@moonforus · 1,601
#9
abouttuss
@theevibee · 556
#10
NewsArmenia Հայերեն
@newsarmenia_am · 4,355
#11
karoxa?
@karoxa707 · 6,177
#12
tammex ✘
@tammexx · 3,171
#13
luwwiii
@luwwiii · 3,412
#14
Insider
@insider_am · 2,304
#15
Inchka?
@inchkabaa · 931 (as read 19 September 2026)
#16
Մ’
@maryyysss7 · 578 (as read 19 September 2026)
#17
Æ🧿
@amorwithae · 3,120
#18
zmeya
@zzzzzmeyaaa · 1,297
#19
ᴏꜰᴡ
@offfromtheWorld · 1,181
#20
ᴇᴇᴇꜱꜱꜱᴛʀᴇʟʟᴀ.
@eeetttoooilee · 919
#21
Vishe nebes
@viishenebes · 1,173 (as read 19 September 2026)
#22
𝙷𝙰𝚈𝙾𝙲 𝙰𝚂𝙷𝚇𝙰𝚁
@mer_hayreniq · 3,690
#23
Happy end
@Happpyennd · 369 (as read 19 September 2026)
#24
Ann's corner
@yereonelove · 1,444
#25
#221
@Zz221zZ · 1,751
#26
Beyoursèlf
@beyourrseelf · 1,242 (as read 19 September 2026)
#27
.
@seredues · 969 (as read 19 September 2026)
#28
ЭТО БОГ
@eto_bog · 59,034
#29
MANIA
@INMANIA1 · 3,034
#30

Read from Telegram’s recommendation API, most recently 19 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

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.

Radar Armenia
@RadarARM · 79,254
Telegram ranks this channel #79 of 83 here — alongside 82 others — read 18 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“uzum em” (@uzumemm), 22,825 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/uzumemm.

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.