Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
Growth
26 measurements spanning 97 days, net +133. 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 5,604–5,797 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)
Subscribers
Change
10 Nov 2026, 17:59
5,774
+1
6 Nov 2026, 21:39
5,773
+5
3 Nov 2026, 12:46
5,768
-7
31 Oct 2026, 11:57
5,775
+25
28 Oct 2026, 06:19
5,750
-4
25 Oct 2026, 07:26
5,754
+9
22 Oct 2026, 11:08
5,745
+14
18 Oct 2026, 23:29
5,731
+12
15 Oct 2026, 20:11
5,719
+12
12 Oct 2026, 10:16
5,707
+42
5 Oct 2026, 13:38
5,665
+37
18 Sept 2026, 03:17
5,628
+2
13 Sept 2026, 19:37
5,626
-3
10 Sept 2026, 08:56
5,629
-6
5 Sept 2026, 00:20
5,635
-25
1 Sept 2026, 04:59
5,660
-5
28 Aug 2026, 21:25
5,665
+3
25 Aug 2026, 22:55
5,662
+9
23 Aug 2026, 08:06
5,653
+7
20 Aug 2026, 01:41
5,646
first reading
Engagement
36 posts held, back to 10 June 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 9 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
24.5%
avg views ÷ 5,774 subscribers
Avg views / post
1,420
7 posts measured
Reaction rate
0.767%
reactions ÷ views · ER floor
Posts in window
7
of 36 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 2 November 2026
Posts held
36 (10 June 2026 – 2 November 2026)
Views total
9,913
Reactions total
76
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
4 Nov 2026, 19:05 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
45s
Average length
9s
Measured directly from 5 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
413 reactions across 33 posts, in 9 distinct kinds. The most used accounts for 37.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
153
37.0%
🔥
71
17.2%
🥰
42
10.2%
💯
34
8.23%
⚡
33
7.99%
🏆
26
6.30%
🤩
23
5.57%
🆒
17
4.12%
✍
14
3.39%
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 34 of the 36 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 427 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 10 June 2026 to 2 November 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
6
across the posts below
Posts paid on
4
of 35 we hold a reading for · 11%
Most on one post
3
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @aezahost. 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 36 most recent posts we hold for this entry, published 10 June 2026 to 2 November 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
Telegram’s own ‘edited’ marker: 3 of 7 posts held from the last 30 days (42.9%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🥰 October Updates
October was a busy month! From exciting events and our anniversary celebrations to Halloween and, of course, plenty of updates. Here's what we've improved over the past month:
Customer Support
➡️ Support Tiers. We've organized our support team into dedicated tiers to speed up response times and make sure complex technical issues reach the right specialists.
➡️ Tips via CloudTips. Had a great exp…
🎃Trick or… data center?
Tonight, forget the candy. Dark corridors, suspicious boxes, and someone you really don’t want to meet face-to-face await.
🎃 This Halloween, we’re opening the doors to our virtual data center in DEAD SHIFT:
Your costume tonight? A night-shift engineer’s uniform. Your mission? Explore the facility, collect useful gear, set traps, and avoid Patient Zero at all costs.
There’s just one catch: …
❤️ Aéza Turns 5! Let's Celebrate Together!
It's our 5th birthday, and what better way to celebrate than by giving something back to our amazing community?
Five years of Aéza wouldn't have been possible without you, so we're making this celebration a little more special!
🎁 We're launching a birthday giveaway, and 3 lucky winners will each receive Telegram Premium!
⏺ Click the button below to participate in the gi…
❤️ Aéza's Anniversary: We're 5 Years Old!
They say that when kids turn five, they start asking “Why?” about everything. We reached that stage a long time ago: why is latency increasing, why is this drive running hotter than the one next to it, and why does every release somehow end up happening on a Friday?
Some might say five years isn't that long. But if you count the late-night alerts, new locations, and conver…
🖥 A week of critical vulnerabilities
Over the past few days:
⏺ PHP patched two critical vulnerabilities that allow remote code execution on the server
⏺ GitLab disclosed a flaw rated 10 out of 10 that affects every version released since 2014
⏺ Node.js shipped fixes for 10 vulnerabilities at once
⏺ The popular Python library LiteLLM was compromised with malicious code that steals passwords and keys
⏺ A hosting …
😳 «The password isn't being entered!»
One of the most common things people say when connecting to a server via SSH for the first time. In fact, the password is being entered, but the characters don't appear on the screen. This is intentional for security reasons.
Here are a few other things that often confuse customers:
🤷♂️ They look for the password in their account settings, but it's actually on the service pa…
The shares total 158%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
🖥 What's running on your server?
We're curious what our clients run on their servers. Pick everything that applies, and feel free to share more in the comments 👇
🥰 AUGUST & SEPTEMBER AT AÉZA
A significant part of the internet runs on servers somewhere, and we’re glad that some of them are ours.
And to keep that part running even better, we spent August and September making improvements. Here’s what changed:
⚙️ Launched a custom server configurator
You can now build your own server configuration by choosing the number of CPU cores, RAM, and disk space instead of settling fo…
🥰 You can now order server administration services
Moving a website from another provider usually goes something like this:
… export the files and database
… upload everything to the new server and update the configuration
… realize half the images won’t load
… spend half the night figuring out why
💻 Now you can hand these tasks over to us, right from your account dashboard:
🖥 Website migration – we’ll move your …
😋 It’s the smiley’s birthday, and you’re getting a new sticker pack
On September 19, 1982, computer scientist Scott Fahlman suggested marking jokes in messages with :-). You had to tilt your head to see it.
To celebrate the smiley’s birthday, we’re releasing a new Aéza sticker pack. For your DMs, group chats, and those moments when sending a sticker is easier than explaining.
Add the sticker pack and show us in th…
🥰10💯3❤2🔥2🏆1
Showing the 12 most recent of 36 posts we hold for @aezahost. 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.
Polls
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
The shares total 158%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
The shares total 310%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 36 most recent posts we hold, published 10 June 2026 to 2 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Mentions
Named by 3 registered channels — 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.
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.
Aéza @aezahost_ru · 26,797 Telegram ranks this channel #1 of 81 here — alongside 80 others — read 12 September 2026
Xray UI @XrayUI · 36,573 Telegram ranks this channel #41 of 52 here — alongside 51 others — read 1 September 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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Aéza ENG” (@aezahost), 5,774 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/aezahost.
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.