Telegram RegisterThe public register of Telegram
Telegram profile photo for Blaze

Channel

Blaze

@uwualn

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

2subscribers

-2 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-1003894337391
TypeChannel
Username@uwualn
Created25 March 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live16 September 2026
Measurements held7
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/uwualn

Growth

21487 August 2026 — 4 subscribers13 August 2026 — 4 subscribers16 August 2026 — 8 subscribers24 August 2026 — 14 subscribers31 August 2026 — 10 subscribers9 September 2026 — 4 subscribers16 September 2026 — 2 subscribers7 August 202616 September 2026
7 measurements spanning 40 days, net -2. 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 0–16 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 17:582-2
9 Sept 2026, 18:384-6
31 Aug 2026, 16:1710-4
24 Aug 2026, 22:0914+6
16 Aug 2026, 17:278+4
13 Aug 2026, 07:474no change
7 Aug 2026, 21:254first reading

Engagement

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

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

What this channel posts

Video runtime
22s
Average length
11s

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

56 reactions across 6 posts, in 13 distinct kinds. The most used accounts for 12.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5249191432966672355712.5%
custom 5274036624773112943712.5%
custom 5420328785742424365712.5%
custom 5260369506261292759610.7%
custom 5436050075442779624610.7%
custom 520874831580549940058.93%
custom 547219760683263692358.93%
custom 542015694839587819947.14%
custom 524931559188126785823.57%
custom 527421332402263694423.57%
custom 532589157311896087023.57%
custom 542048985560595671323.57%
custom 542010182249063320211.79%

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 7 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 56 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 25 March 2026 to 12 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
14
across the posts below
Posts paid on
5
of 15 we hold a reading for · 33%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @uwualn. 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 16 most recent posts we hold for this entry, published 25 March 2026 to 12 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

12 Aug 2026, 19:45 UTC8 viewsread 13 August 2026
Forwarded from @StrategSh

Лотерея на мишку 🎂 от 1997 и Strateg Условия: Репост и подписка на @DM7XN и @StrategSh Результаты 13.08 вечером.

Signed Buda

12 Aug 2026, 19:36 UTC8 viewsread 13 August 2026

Профессионально отталкиваю людей.

Signed Buda

7 Aug 2026, 14:36 UTC140 viewsread 13 August 2026

Буда мен шаршадым депппа

Signed Buda

27 Jul 2026, 07:35 UTC331 views1 reactionsread 13 August 2026

Некоторые люди сами рушат всё, что им дорого, а потом удивляются, почему остаются одни.

custom 52740366247731129431

Signed Buda

26 Jul 2026, 10:37 UTC325 viewsread 13 August 2026

Того, кто предал однажды, всегда будет преследовать собственная совесть. Даже если он делает вид, что её нет.

Signed Buda

25 Jul 2026, 14:22 UTC315 views3 reactions10 Starsread 13 August 2026
Photo

🔤rash 🔤ist by 🔤amir W:🔤yau,🔤nel. M:🔤lish,🔤rlan,🔤arkhan,,🔤hris,🔤hase,🔤li,🔤angster Порядок не имеет значение,и будет пополняться.

custom 52740366247731129432custom 52742133240226369441

Signed Buda

2 Jul 2026, 04:40 UTC472 views19 reactions1 Starread 13 August 2026
Photo

Photo, posted without a caption

custom 52740366247731129434custom 54201569483958781994custom 54203287857424243654custom 52491914329666723552custom 52493155918812678582custom 54204898556059567132custom 52742133240226369441

Signed Buda

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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“Blaze” (@uwualn), 2 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/uwualn.

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.