Telegram RegisterThe public register of Telegram
Telegram profile photo for Макс Асанов

Channel

Макс Асанов

@Maksasanov18rus

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

1,016subscribers

-36 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002348750990
TypeChannel
Username@Maksasanov18rus
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/Maksasanov18rus

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

1,0031,0631,0338 August 2026 — 1,052 subscribers9 August 2026 — 1,050 subscribers12 August 2026 — 1,040 subscribers15 August 2026 — 1,019 subscribers18 August 2026 — 1,008 subscribers26 August 2026 — 1,005 subscribers29 August 2026 — 1,003 subscribers31 August 2026 — 1,038 subscribers3 September 2026 — 1,063 subscribers8 September 2026 — 1,041 subscribers12 September 2026 — 1,029 subscribers16 September 2026 — 1,016 subscribers1,0168 August 202616 September 2026
12 measurements spanning 39 days, net -36. 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 994–1,072 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 10:591,016-13
12 Sept 2026, 14:011,029-12
8 Sept 2026, 13:401,041-22
3 Sept 2026, 17:561,063+25
31 Aug 2026, 19:551,038+35
29 Aug 2026, 00:271,003-2
26 Aug 2026, 01:231,005-3
18 Aug 2026, 23:071,008-11
15 Aug 2026, 20:511,019-21
12 Aug 2026, 06:221,040-10
9 Aug 2026, 03:111,050-2
8 Aug 2026, 09:001,052first reading

Engagement

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

What this channel posts

Video runtime
8s
Average length
8s

Measured directly from 1 video 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

162 reactions across 11 posts, in 5 distinct kinds. The most used accounts for 31.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥5131.5%
❤‍🔥4024.7%
custom 52873846744594731763622.2%
custom 51973888531570591232716.7%
😍84.94%

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

Measured over the 13 most recent posts we hold, published 4 August 2026 to 8 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

8 Aug 2026, 06:01 UTC134 views2 reactionsread 8 August 2026
Video message

Video message, posted without a caption

❤‍🔥2

8 Aug 2026, 03:25 UTC168 views1 reactionsread 8 August 2026
Video message

Video message, posted without a caption

❤‍🔥1

7 Aug 2026, 19:18 UTC262 views7 reactionsread 8 August 2026
Photo

Photo, posted without a caption

🔥5😍1custom 51973888531570591231

7 Aug 2026, 18:49 UTC263 views4 reactionsread 8 August 2026
Video message

Video message, posted without a caption

❤‍🔥4

7 Aug 2026, 16:56 UTC278 views11 reactionsread 8 August 2026
Video message

Video message, posted without a caption

❤‍🔥8custom 51973888531570591232🔥1

6 Aug 2026, 21:26 UTC318 views16 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 52873846744594731765🔥4custom 51973888531570591234❤‍🔥3

6 Aug 2026, 21:20 UTC310 views15 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 51973888531570591235custom 52873846744594731764❤‍🔥3🔥3

6 Aug 2026, 11:49 UTC339 views24 reactionsread 8 August 2026
Video message

Video message, posted without a caption

🔥10custom 51973888531570591237custom 52873846744594731767

6 Aug 2026, 10:37 UTC338 views9 reactionsread 8 August 2026

Есть актив есть контент

🔥8😍1

6 Aug 2026, 10:37 UTC337 views59 reactionsread 8 August 2026
Photo

Photo, posted without a caption

❤‍🔥19custom 528738467445947317616🔥14😍6custom 51973888531570591234

4 Aug 2026, 21:49 UTC370 viewsread 8 August 2026

Эти неимоверные львы ищут себе жинок

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

“Макс Асанов” (@Maksasanov18rus), 1,016 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/Maksasanov18rus.

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.