Telegram RegisterThe public register of Telegram
Telegram profile photo for махххик💊

Channel

махххик💊

@huyaksik

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

116subscribers

+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-1001532327589
TypeChannel
Username@huyaksik
Created6 September 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded9 August 2026
Last confirmed live9 October 2026
Measurements held4
Confirmed unchanged4 times, most recently 9 October 2026
On Telegramt.me/huyaksik

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 26 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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

115116115.57 August 2026 — 116 subscribers9 August 2026 — 116 subscribers15 August 2026 — 115 subscribers6 September 2026 — 116 subscribers7 August 20266 September 2026
4 measurements spanning 30 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 115–116 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 23:18116+1
15 Aug 2026, 17:15115-1
9 Aug 2026, 05:31116no change
7 Aug 2026, 19:51116first reading

Engagement

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

Reaction mix

72 reactions across 3 posts, in 7 distinct kinds. The most used accounts for 25.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52652476356268095931825.0%
💘1825.0%
💋1520.8%
🌭1013.9%
custom 521112277559018930368.33%
👀45.56%
☃11.39%

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

Measured over the 3 most recent posts we hold, published 9 June 2026 to 7 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.

Recent posts

7 Jul 2026, 00:56 UTC72 views27 reactionsread 9 August 2026
Photo

заметив что посты выходят раз в месяц почемуто мысленно придерживаюсь данной установки🐵

custom 526524763562680959315custom 52111227755901893036🌭4💘2

9 Jun 2026, 09:59 UTC134 views25 reactionsread 9 August 2026
Video

я ебу и плачу

💘15🌭5💋4☃1

9 Jun 2026, 09:56 UTC125 views20 reactionsread 9 August 2026
Photo

ну шо вы маленькие кормёжка приехала😁

💋11👀4custom 52652476356268095933🌭1💘1

Showing the 3 most recent of 3 posts we hold for @huyaksik. 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“махххик💊” (@huyaksik), 116 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/huyaksik.

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.