Channel
@mlinast52
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
149subscribers
+57 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003210330287 |
|---|---|
| Type | Channel |
| Username | @mlinast52 |
| Description | эⲇυⲧы υ ⳡⲉⲧⲟ ⲉպⲉ ⳡ ⲡⲟⳡⲧυ ⲏⲉⳡⲉⲅⲟ ⲏⲉ ⲩⲙⲉю инфо: https://t.me/mlinast52/13136 анон: @mlinastbot ⲧⲧ-https://www.tiktok.com/@mlinast1?_r=1&_t=ZS-9AUiUfHSPwK читайте описание тт прошу ⳝⲩⲥⲧ https://t.me/boost/deepklis ⲗⲥ-@plian02 коллабы не делаю |
| Created | Between 1 October 2025 and 31 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 4 |
| On Telegram | t.me/mlinast52 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 11 November 2026 and assigned it the closest of 31 fixed categories, at 86% 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.
@mlinast52 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 03:53 | 149 | no change |
| 11 Nov 2026, 03:47 | 149 | +58 |
| 10 Aug 2026, 22:28 | 91 | -1 |
| 10 Aug 2026, 19:02 | 92 | first reading |
19 posts held, back to 10 August 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 19 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
4 reactions across 4 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5474400259335549174 | 2 | 50.0% | |
| custom 5195190023175053449 | 1 | 25.0% | |
| custom 5462986688689114302 | 1 | 25.0% |
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 4 of the 19 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 10 August 2026 to 10 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.
𐌺𐌏𐋏𐌺УР𑀝 𐋏А 🧸/💖 𐌏Т 𐌑ЯТЫ Уᥴ᧘᧐ʙᥙя: -ρᥰ/ρκ -ᥰ᧐дᥰᥙᥴκᥲ(жᥱ᧘ᥲᴛᥱ᧘ьн᧐ δᥱᤋ дᥲ᧘ьнᥱᥔɯᥱᴦ᧐ ᧐ᴛᥰᥙᥴκᥙ) 𐌵𐍄𐌏𐌲𐌵 𝟷𝟼.𝟶𝟾 ⲡⲣⲩⲫы ⲡⲟⲇ ⲥⲗⲉⲇⲩюⳃυύ ⲡⲟⲥⲧ, ⲩ ⲕⲟⲅⲟ ⲏⲉⲧⲩ ⲕⲁⲏⲁⲗⲁ
custom 51951900231750534491
Signed ⳝⲉⲥⲥⲡⲗυⲁⲏ
Sticker, posted without a caption
Signed ⳝⲉⲥⲥⲡⲗυⲁⲏ
напоминаю про навигацию
Signed ⳝⲉⲥⲥⲡⲗυⲁⲏ
https://www.twitch.tv/anek https://www.twitch.tv/anek Тик токи
Signed ⳝⲉⲥⲥⲡⲗυⲁⲏ
о привет #напамять
Signed ⳝⲉⲥⲥⲡⲗυⲁⲏ
👾 anek завёл стрим ос Играет в: Just Chatting twitch.tv/anek
Signed Etozhebot
anek обновил статус: ос ____ Стрим сейчас оффлайн
custom 54629866886891143021
Signed Etozhebot
)) ссылочка #kwz
Signed ⳝⲉⲥⲥⲡⲗυⲁⲏ
и не могу сказать «люблю» зм/ссылочка #zeinixx рк/рп?
custom 54744002593355491741
Signed ⳝⲉⲥⲥⲡⲗυⲁⲏ
Sticker, posted without a caption
Signed ⳝⲉⲥⲥⲡⲗυⲁⲏ
как трахнуть её арты, это слишком шикарно 🙏🏻💗
custom 54744002593355491741
Signed ⳝⲉⲥⲥⲡⲗυⲁⲏ
☺️
Signed ⳝⲉⲥⲥⲡⲗυⲁⲏ
Showing the 12 most recent of 19 posts we hold for @mlinast52. 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.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“ПЕРЕЕЗД//ጠበሀዘዘዐርፐሪ” (@mlinast52), 149 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/mlinast52.
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.