Channel
@abuseqr
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
416subscribers
+44 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003212249352 |
|---|---|
| Type | Channel |
| Username | @abuseqr |
| Created | Between 1 October 2025 and 31 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/abuseqr |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 09:49 | 416 | +26 |
| 22 Aug 2026, 12:45 | 390 | +8 |
| 15 Aug 2026, 19:35 | 382 | +10 |
| 8 Aug 2026, 06:19 | 372 | no change |
| 7 Aug 2026, 17:48 | 372 | first reading |
18 posts held, back to 29 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 pageof 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 18 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
66 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 62.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5406828350616405948 | 41 | 62.1% | |
| custom 5407129371989278852 | 10 | 15.2% | |
| custom 5854766299690835045 | 8 | 12.1% | |
| custom 5386399458932038755 | 5 | 7.58% | |
| custom 5249396998691383964 | 2 | 3.03% |
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 areTelegram’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 13 of the 18 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 66reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 29 June 2026 to 26 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.
🎉 Нас уже 1000! Спасибо каждому, кто пользуется Dialogues Save. За короткое время наше сообщество выросло до 1000 пользователей, и это только начало! ❤️ Этой ночью мы выпустили обновление. ✨ Новые команды 💬 /reply Теперь вы можете отвечать пользователям, не открывая чат и не просматривая переписку. Быстро, удобно и с сохранением конфиденциальности. 🗑 /undo Новая команда для управления сообщениями: удалить всю …
🚀 Небольшое обновление бота! Добавили сразу три полезные функции 👇 🔎 /search — поиск по всему архиву Ищите любое сообщение сразу во всех личных чатах и отслеживаемых каналах. А искусственный интеллект выберет самый подходящий результат и объяснит, почему именно он. Больше не нужно листать переписки вручную! 📝 «Что я пропустил» в /ai Не успели прочитать? Бот сделает краткое саммари переписки за 7 дней: главные темы…
Новость Насколько нам стало известно, ничего нового, связанного с турникетами, вуз вводить не собирается; то есть входы и выходы должны быть как раньше. #СКУД
custom 54068283506164059481
🔥 Напоминаем, что серию можно начать только с тем человеком, у которого также стоит наш бот, при этом необязательно иметь подписку 🆓 Также мы готовы дать вам еще один месяц пробной подписки, просто напишите нам свой TG ID(https://t.me/anonaskbot?start=o4fajp3)
🤖 @dialogues_save_bot
custom 54068283506164059481
➡️ @dialogues_save_bot
custom 53863994589320387552
🆓 Мы готовы продлить всем подписку еще на месяц, просто напишите нам об этом анонимно, указав свой Telegram ID(https://t.me/anonaskbot?start=o4fajp3) или в чате канала. @dialogues_save_bot
custom 58547662996908350451
🚀 Dialogues Save — Крупное обновление Мы рады представить одно из самых масштабных обновлений Dialogues Save. ✨ Что нового? 📱 Мини-приложение Теперь пользоваться сервисом стало еще быстрее и удобнее благодаря полноценному Mini App. 📲 Слежка за каналами Получайте информацию об изменениях и новых публикациях в отслеживаемых каналах автоматически. 🧠 ИИ-анализ Искусственный интеллект поможет анализировать сообщен…
custom 58547662996908350451
Video, posted without a caption
custom 58547662996908350456
🚀 Знакомьтесь — FroggyCloud. Мы создаем облачную платформу нового поколения: простую, быструю и удобную для хранения ваших файлов и работы с ними. 🐸 Что доступно уже сейчас? • 100 ГБ S3-хранилища бесплатно каждому пользователю. • Полностью бесплатный доступ к API — интегрируйте FroggyCloud в свои проекты без ограничений базового тарифа. • Надежное облачное хранилище для фотографий, видео, документов и любых других…
custom 54068283506164059484custom 52493969986913839641
🔥 Насчёт «серийчика» — мы решили не добавлять такую версию, потому что буквально у половины людей она либо не загружалась бы до конца, либо сильно лагала. Поэтому мы сильно упростили дизайн, сделав его минималистичным (как в TikTok).
Photo, posted without a caption
custom 54068283506164059481
Showing the 12 most recent of 18 posts we hold for @abuseqr. 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“RoseUp(MIREA)” (@abuseqr), 416 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/abuseqr.
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.