— Напоминаем что уже завтра наша сходка 🎂🎂 Будем всех вас ждать! 👻👻👻👻👻👻👻👻
custom 52086385235565235905custom 52087822804068878485

Channel
@RLmeetings
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
89subscribers
+3 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003999130534 |
|---|---|
| Type | Channel |
| Username | @RLmeetings |
| Created | 5 June 2026 — measured — dated from the channel’s first post |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 11 September 2026 |
| On Telegram | t.me/RLmeetings |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 22:28 | 89 | +2 |
| 25 Aug 2026, 00:34 | 87 | +2 |
| 17 Aug 2026, 14:24 | 85 | -1 |
| 10 Aug 2026, 09:15 | 86 | no change |
| 10 Aug 2026, 09:02 | 86 | first reading |
16 posts held, back to 5 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 16 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
141 reactions across 13 posts, in 19 distinct kinds. The most used accounts for 19.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5208782280406887848 | 27 | 19.1% | |
| custom 5208638523556523590 | 23 | 16.3% | |
| ❤🔥 | 15 | 10.6% | |
| ❤ | 14 | 9.93% | |
| ⚡ | 11 | 7.80% | |
| 🍓 | 10 | 7.09% | |
| 👍 | 8 | 5.67% | |
| 👏 | 7 | 4.96% | |
| 😇 | 6 | 4.26% | |
| 🍌 | 5 | 3.55% | |
| 🤩 | 4 | 2.84% | |
| custom 5357098766836980741 | 2 | 1.42% | |
| 🆒 | 2 | 1.42% | |
| 💘 | 2 | 1.42% | |
| custom 5355246914377899482 | 1 | 0.709% | |
| 🎉 | 1 | 0.709% | |
| 💋 | 1 | 0.709% | |
| 🔥 | 1 | 0.709% | |
| 🥰 | 1 | 0.709% |
Custom emoji. 4 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 13 of the 16 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 141 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 5 June 2026 to 1 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 52086385235565235905custom 52087822804068878485
Хотел бы видеть то нас меняльники на наших сходках?🎶🎶
Shares as published. No per-option vote count is published by Telegram, so none is shown.
🌟🌟🌟🌟🌟🌟🌟🌟🌟 🎂🎂— Ребята всем привет! В связи с обстоятельствами мы перенесём сходку на 2 августа! 💛 На улице жара да и многие наверняка устали после Кагаяки Феста. 🧽 Давайте отдохнём и все вместе встретимся 2 августа, в городе Нижнекамск, парк Лемаева на круглой сцене! 🌷 Надеюсь никто из вас не будет зол на то что мы переносим сходку, простите🤩🤩
😇4🤩3custom 52087822804068878482custom 52086385235565235901
🤩🙂🙂🙂🙂🙂🙂🙂🙂🤩 —И так вот и программа нашей сходки! 💛 12:00-13:00 —Все вместе собираемся!💛 13:00-14:00 —Общаемся и играем в игры 🌟 14:00-14:30 —Перерыв!🧽 14:30-15:30 —Рандом денс🌷 15:30-16:00 —Конец сходки!💛 —Будем вас всех ждать завтра!
custom 52086385235565235905
💛💛💛💛💛💛💛 🌟— На нашей сходке вы сможете ! 🎂 1. Порисовать на нашем плакате. 🌟 2. Поиграть в карточные игры .(уно, мафия) 🎂 3. Потанцевать на рандом денсе. 🧽 4. И самое главное получить хорошее настроение! 💛💛💛💛💛💛💛💛 Г. Нижнекамск , парк Лемаева на круглой сцене Число: 26 июля в 13:00
custom 52087822804068878486⚡1😇1custom 52086385235565235901
🌟🔤🔤🔤🔤🔤🧽 🎂—Привет! Это анонс еще одной сходки, которая пройдёт уже в это воскресенье, а именно 26-ого июля. 🎂 Пройдёт сходка как и обычно в городе Нижнекамск, в парке Лемаева на круглой белой сцене, в 13:00.💛 📎Следите за выходами новых постов, там будет больше информации о сходке!📎 🌷🌷🌷🌷🌷🌷🌷🌷🌷🌷🌷 Г. Нижнекамск, парк Лемаева на круглой белой сцене 26 июля 13:00
👍4👏2🆒1custom 52086385235565235901custom 52087822804068878481
🤩— Так же есть и потеряшки! Прошу отпишитесь чьи они ! 🤩 ЮЗ: @MM_1505
🐱 — Наша первая сходка прошла и мы благодарны вам за то что пришли! 🎂🎂 — Надеемся ,что с каждой сходкой к нам будут прибавляются новые ребята! ✨✨
⚡7👏3custom 52087822804068878483🆒1custom 52086385235565235901
💛🙂🙂🙂🙂🙂🙂🙂🙂🙂 🎂🎂 — Всем привет! Сегодня мы с вами встретимся на нашей сходке! 🌟 13:00-14:00 — Собираемся все вместе!🎂 14:00-16:00 —Слушаем песенки, играем в игры! 🤩🤩 16:00-16:30 —Небольшой перерыв 🤘 16:30-17:30 —Рандом Денс✨✨ 17:30-18:00 —Потихоньку заканчиваем нашу сходку! 🤩 🎂— Вот такой насыщенный день ждёт вас сегодня! Адрес:г. Нижнекамск Парк Лемаева на круглой сцене🎶🎶
custom 52086385235565235906⚡1👏1🤩1custom 52087822804068878481
🌷🙂🙂🙂🙂🙂🙂🙂🌷 🤩🤩 — Всем доброе утро! И хотим сказать , что под этот пост вы можете скинуть свои песни! 🧽Которые хотели бы услышать у нас на сходке. 🤩 🤩🤩 —А ,так же скинуть песни под которые вы хотели бы потанцевать на рандом денсе ! 🤩 🎶🎶— Перед тем как скинуть песню просим вас прочитать правила!! Г. Нижнекамск Парк Лемаева на круглой сцене 12 июля
custom 52087822804068878483
У нас есть буст и мы будем рады новым реакциям благодаря вам! 🎂🎂 https://t.me/boost/RLmeetings
custom 52087822804068878484⚡2custom 52086385235565235901custom 53570987668369807411
📎🙂🙂🙂🙂🙂🙂🙂📎 Небольшие и самые основные правила наших сходок/пати/фестов. Ребята, просим всех следовать правилам и жить дружно. Если кто-то наблюдает за тем, что кто-либо нарушает правила, то просим сообщить организаторам. 🙂🙂🙂🙂🙂🙂🙂🤩 🙂🙂🙂🙂🙂🙂🙂🙂🙂🤩 👀Не устраивать конфликты. Не ссориться, не кричите на территории мероприятия. Если у вас какие-то разногласия, то просим решать их вне сходки. 👍 👀Не оскорбляем никого. Есл…
❤🔥1custom 52086385235565235901custom 52087822804068878481custom 53552469143778994821custom 53570987668369807411
Showing the 12 most recent of 16 posts we hold for @RLmeetings. 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 poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Хотел бы видеть то нас меняльники на наших сходках?🎶🎶
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 16 most recent posts we hold, published 5 June 2026 to 1 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“🎼RL: сходки✨” (@RLmeetings), 89 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/RLmeetings.
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.