Photo, posted without a caption
❤35👎1

Channel
@ruslameuka_a
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
1,318subscribers
-30 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001696524081 |
|---|---|
| Type | Channel |
| Username | @ruslameuka_a |
| Created | 2 February 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/ruslameuka_a |
Marketing & affiliate — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 15:59 | 1,318 | +1 |
| 14 Sept 2026, 05:41 | 1,317 | -4 |
| 10 Sept 2026, 07:01 | 1,321 | -6 |
| 5 Sept 2026, 07:02 | 1,327 | -4 |
| 1 Sept 2026, 13:13 | 1,331 | -2 |
| 29 Aug 2026, 21:55 | 1,333 | -1 |
| 26 Aug 2026, 19:43 | 1,334 | -1 |
| 23 Aug 2026, 22:55 | 1,335 | -1 |
| 17 Aug 2026, 09:33 | 1,336 | -4 |
| 13 Aug 2026, 16:27 | 1,340 | -4 |
| 10 Aug 2026, 17:34 | 1,344 | -4 |
| 7 Aug 2026, 22:21 | 1,348 | no change |
| 7 Aug 2026, 12:14 | 1,348 | first reading |
12 posts held, back to 12 May 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 12 posts for this entry, the most recent from 23 June 2026. An engagement rate over an empty window would be a number about nothing.
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.
369 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 79.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 293 | 79.4% | |
| 👍 | 55 | 14.9% | |
| 👎 | 21 | 5.69% |
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 12 of the 12 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 369 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 12 May 2026 to 23 June 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.
Photo, posted without a caption
❤35👎1
рамочные соглашения дашборды борды комитменты ПОДСВЕТИМ идеи проработаем упакуем ВОЗЬМЕМ В РАБОТУ проекты подсветим коллеги подсветим с вами важное поставим на контроль дожмем СВЕРИМ ЧАСЫ вынесем за скобки ПОДСВЕТИМ риски с вами коллеги посмотрим LTV CAC. всех жду
❤20
"март25" к "март26" рост на 596% "апрель25" к "апрель26" рост на 529% ➡ и абсолютный рекорд "май25" к "май26" рост на 810% 🤩 это была кропотливая работа, которой уже почти год. и сейчас, кажется, готов подвести итоги& всё началось с тестирования новых маркетинговых гипотез. к июню прошлого года увидели рост в 250% - цифры были скромные, но я понял, что направление правильное проблема была в том, что курс не был г…
❤23👍4👎1
Photo, posted without a caption
❤18👍8
немного мыслей про сервис и то, почему одни проекты работают а другие неь сейчас, в кризис, когда все вокруг сжимается, самое глупое, что можно сделать – начать резать качество. экономить на том, что на самом деле важно для людей простой пример из жизни. нужно было сдать анализы. можно пойти в одну лабораторию там мрачные лица на ресепшене, медсестра молча берет кровь, никакой эмпатии. просто механическое выполнени…
👍19❤10👎2
итоги
❤2👎1
а круто что мы живём в прикольном авторитаризме а не как наши бабушки в отстойном можно смотреть тик ток.
❤37👍7
График на июнь 3-5 июня – ПМЭФ, Санкт-Петербург 6 июня – Финал Roland Garros, Париж 8-10 июня – London Tech Week, Лондон 11 июня – Открытие ЧМ-2026 по футболу, Мехико 16-20 июня – скачки Royal Ascot, Беркшир 20-21 июня – ярмарка Art Basel, Базель 22-26 июня – Каннские Львы, Канны 27 июня – Алые Паруса, Санкт-Петербург 29-30 июня – открытие Уимблдона, Лондон
❤23👎1
[00:00] Спикер 1: Добрый день. Так, вроде все в сборе. У нас тут на встрече отдел разработки техядра, БД-разработчик, Девопс, архитектор, ПМ, продуктованер, коллеги из бизнес-анализа, отдел системного анализа, скрам-мастер, вторая линия поддержки портала, тестировщики, UX-дизайнеры, аналитики данных, сервис-менеджеры. [00:25] Спикер 1: и также присоединился начальник управления со стороны бизнеса. Предлагаю сразу по…
❤21👎5
я верю только в ту часть астрологии которая говорит мне что я красивый + смешной + секси + меня ждет удача на всю жизнь
❤43👍5👎3
Video, posted without a caption
❤9👍7
иордания
❤52👎7👍5
Showing the 12 most recent of 12 posts we hold for @ruslameuka_a. 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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Ruslameuka” (@ruslameuka_a), 1,318 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ruslameuka_a.
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.