Telegram RegisterThe public register of Telegram
Telegram profile photo for м

Channel

м

@umirlarku

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

12subscribers

+0 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-1001236909974
TypeChannel
Username@umirlarku
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live3 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/umirlarku

Topic

Other / unclassifiable — 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 2 October 2026 and assigned it the closest of 31 fixed categories, at 63% 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

1214137 August 2026 — 12 subscribers8 August 2026 — 13 subscribers12 August 2026 — 13 subscribers1 September 2026 — 14 subscribers3 October 2026 — 12 subscribers7 August 20263 October 2026
5 measurements spanning 57 days. 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 12–14 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 05:4112-2
1 Sept 2026, 02:4514+1
12 Aug 2026, 04:0013no change
8 Aug 2026, 16:3313+1
7 Aug 2026, 17:4012first reading

Engagement

20 posts held, back to 12 March 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 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
44m 08s
Average length
4m 54s

Measured directly from 9 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

173 reactions across 18 posts, in 19 distinct kinds. The most used accounts for 24.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4224.3%
custom 53575799534979838892514.5%
custom 52041940312690757302011.6%
custom 5202215752152659066126.94%
custom 5408943295592171413126.94%
❤‍🔥126.94%
custom 5462902520215002477105.78%
👍95.20%
custom 540899447012750696474.05%
💯52.89%
🔥31.73%
😍31.73%
😘31.73%
🌚21.16%
🤩21.16%
🥰21.16%
🫡21.16%
🕊10.578%
🤗10.578%

Custom emoji. 6 of the rows above are 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 18 of the 20 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 173 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 12 March 2026 to 9 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

26 Jun 2026, 08:26 UTC77 views9 reactionsread 12 August 2026
Voice message

Voice message, posted without a caption

❤3❤‍🔥2🤩2custom 52022157521526590661custom 54089944701275069641

20 Jun 2026, 23:43 UTC87 views8 reactionsread 12 August 2026
Video

Video, posted without a caption

❤3custom 52022157521526590662custom 52041940312690757302custom 53575799534979838891

19 Jun 2026, 14:24 UTC84 views9 reactionsread 12 August 2026
Photo

Photo, posted without a caption

❤2🥰2custom 52022157521526590662custom 52041940312690757301custom 53575799534979838891custom 54629025202150024771

19 Jun 2026, 14:24 UTC75 views9 reactionsread 12 August 2026
Photo

Photo, posted without a caption

❤2❤‍🔥2custom 52022157521526590662💯1custom 52041940312690757301custom 53575799534979838891

12 Jun 2026, 14:08 UTC91 views9 reactionsread 12 August 2026
Video

Video, posted without a caption

❤3custom 53575799534979838892❤‍🔥1custom 52041940312690757301custom 54089944701275069641custom 54629025202150024771

12 Jun 2026, 14:08 UTC80 views9 reactionsread 12 August 2026
Video

Video, posted without a caption

❤4👍3custom 52041940312690757302

9 Jun 2026, 11:13 UTC79 views8 reactionsread 12 August 2026
Video

Video, posted without a caption

😍3❤2👍2custom 54629025202150024771

9 Jun 2026, 11:12 UTC65 views8 reactionsread 12 August 2026
Video

Video, posted without a caption

custom 54089432955921714133❤2👍2custom 53575799534979838891

12 May 2026, 13:31 UTC119 views11 reactionsread 12 August 2026
File

File, posted without a caption

custom 54089944701275069644custom 53575799534979838893🫡2🔥1custom 52041940312690757301

2 Apr 2026, 04:05 UTC270 views10 reactionsread 12 August 2026
Video

Video, posted without a caption

custom 52041940312690757305❤2custom 52022157521526590662custom 54089944701275069641

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

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

“м” (@umirlarku), 12 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/umirlarku.

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.