Telegram RegisterThe public register of Telegram
Telegram profile photo for #

Channel

#

@qwertzxch

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

148subscribers

-37 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003634778906
TypeChannel
Username@qwertzxch
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live1 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/qwertzxch

Growth

148185166.510 August 2026 — 185 subscribers10 August 2026 — 185 subscribers18 August 2026 — 176 subscribers25 August 2026 — 167 subscribers1 September 2026 — 148 subscribers10 August 20261 September 2026
5 measurements spanning 22 days, net -37. 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 142–191 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Sept 2026, 07:05148-19
25 Aug 2026, 21:05167-9
18 Aug 2026, 05:42176-9
10 Aug 2026, 19:16185no change
10 Aug 2026, 17:46185first reading

Engagement

2 posts held, back to 23 June 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 2 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

196 reactions across 2 posts, in 14 distinct kinds. The most used accounts for 19.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52312618471763774743819.4%
custom 53686452881960766242613.3%
custom 53639064489149356562512.8%
custom 53617143749164651862412.2%
custom 5364245519403083790189.18%
custom 5361905960522640333136.63%
custom 5364332608454946186136.63%
custom 5226782501229311999105.10%
custom 536384944181401529484.08%
custom 536410414625956810663.06%
custom 536862520063402920763.06%
custom 536163002175877473442.04%
custom 536181122213402522331.53%
custom 536433141445403773821.02%

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

Measured over the 2 most recent posts we hold, published 23 June 2026 to 13 July 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
131
across the posts below
Posts paid on
2
of 2 we hold a reading for · 100%
Most on one post
110
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @qwertzxch. 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 2 most recent posts we hold for this entry, published 23 June 2026 to 13 July 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

13 Jul 2026, 12:42 UTC836 views67 reactions21 Starsread 10 August 2026
Photo

Photo, posted without a caption

custom 536171437491646518624custom 536190596052264033313custom 536424551940308379010custom 53641041462595681066custom 53643326084549461865custom 53616300217587747344custom 53618112221340252233custom 53643314144540377382

Signed napoleon

23 Jun 2026, 10:42 UTC≈1,550 views129 reactions110 Starsread 10 August 2026
Photo

Photo, posted without a caption

custom 523126184717637747438custom 536864528819607662426custom 536390644891493565625custom 522678250122931199910custom 53638494418140152948custom 53642455194030837908custom 53643326084549461868custom 53686252006340292076

Showing the 2 most recent of 2 posts we hold for @qwertzxch. 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“#” (@qwertzxch), 148 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/qwertzxch.

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.