Мы iPhone Duo держим! А вы что делаете сейчас? 🤭 Первый уже уехал к своему владельцу, а завтра вы сможете купить новинку из наличия! Давайте на выставочный стенд его поскорее — «🔥». Голосуйте и… Продолжайте наслаждаться выходными 🤭
❤🔥11🔥9👍3❤2🤩2

Channel
@rebro_store_ru
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
55,033subscribers
+10,722 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001746238425 |
|---|---|
| Type | Channel |
| Username | @rebro_store_ru |
| Description | Магазин техники Apple, Dyson и других брендов с гарантией 2 года. • Двойная выгода по Трейд-ин • Рассрочка без первого взноса • Подарки при покупке Наш сайт: https://rebro-store.ru Трейд-ин устройства с гарантией 1 год: https://t.me/rebrodiscount |
| Created | 11 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 26 October 2026 |
| Measurements held | 50 |
| Confirmed unchanged | 1 time, most recently 26 October 2026 |
| On Telegram | t.me/rebro_store_ru |
Ecommerce storefront — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 26 Oct 2026, 00:19 | 55,033 | -56 |
| 24 Oct 2026, 23:15 | 55,089 | -58 |
| 23 Oct 2026, 21:10 | 55,147 | -149 |
| 22 Oct 2026, 20:36 | 55,296 | -76 |
| 21 Oct 2026, 15:39 | 55,372 | -51 |
| 20 Oct 2026, 14:48 | 55,423 | -68 |
| 19 Oct 2026, 17:29 | 55,491 | -65 |
| 18 Oct 2026, 16:28 | 55,556 | -89 |
| 17 Oct 2026, 13:56 | 55,645 | -19 |
| 16 Oct 2026, 12:31 | 55,664 | -63 |
| 15 Oct 2026, 14:10 | 55,727 | -31 |
| 14 Oct 2026, 13:15 | 55,758 | -133 |
| 13 Oct 2026, 00:12 | 55,891 | -379 |
| 8 Oct 2026, 16:16 | 56,270 | -4,125 |
| 4 Oct 2026, 08:19 | 60,395 | +7,185 |
| 25 Sept 2026, 18:17 | 53,210 | +1,980 |
| 19 Sept 2026, 04:18 | 51,230 | +3,669 |
| 16 Sept 2026, 20:18 | 47,561 | +120 |
| 15 Sept 2026, 00:58 | 47,441 | +150 |
| 13 Sept 2026, 12:19 | 47,291 | first reading |
171 posts held, back to 2 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 177 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 25 October 2026 |
|---|---|
| Posts held | 171 (2 August 2026 – 25 October 2026) |
| Views total | 132,920 |
| Reactions total | 1,089 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 26 Oct 2026, 05:51 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 26 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 13 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.
5,091 reactions across 168 posts, in 41 distinct kinds. The most used accounts for 24.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 1,239 | 24.3% | |
| ❤ | 836 | 16.4% | |
| ❤🔥 | 578 | 11.4% | |
| 👀 | 352 | 6.91% | |
| 👍 | 351 | 6.89% | |
| 🤩 | 321 | 6.31% | |
| 🤣 | 236 | 4.64% | |
| 💯 | 193 | 3.79% | |
| 🥰 | 136 | 2.67% | |
| 😁 | 123 | 2.42% | |
| custom 5305393940483025545 | 85 | 1.67% | |
| 😱 | 80 | 1.57% | |
| 😭 | 76 | 1.49% | |
| 😍 | 71 | 1.39% | |
| 🍾 | 65 | 1.28% | |
| 🤪 | 45 | 0.884% | |
| 💘 | 44 | 0.864% | |
| 👏 | 32 | 0.629% | |
| 🎉 | 29 | 0.57% | |
| 💔 | 26 | 0.511% | |
| 21 further kinds | 173 | 3.40% |
Custom emoji. One 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 count beside it is 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 168 of the 171 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 5,091 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 171 most recent posts we hold, published 2 August 2026 to 25 October 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.
Мы iPhone Duo держим! А вы что делаете сейчас? 🤭 Первый уже уехал к своему владельцу, а завтра вы сможете купить новинку из наличия! Давайте на выставочный стенд его поскорее — «🔥». Голосуйте и… Продолжайте наслаждаться выходными 🤭
❤🔥11🔥9👍3❤2🤩2
Откуда вы взялись такие?! 😳 ⠀⠀⠀⠀⠀⠀⠀⠀⠀ Красивые, счастливые... Да ещё и с новым iPhone в руках. Пора пополнить их ряды. Модель, цвет, объем памяти — выбирайте то, что подходит именно вам. Выгода гарантирована в любом случае. Проверьте сами → здесь.
🤩6❤🔥3❤2🥰2
Video message, posted without a caption
🤩6❤🔥3🥰3
🤍🤍🤍🤍🤍 iPhone с историей* — это выгодный способ обновиться! → iPhone 17 Pro 256 ГБ | Серебристый — от 84 990 ₽ → iPhone 16 Pro Max 256 ГБ | Чёрный Титан — от 72 990 ₽ → iPhone 16 Pro 512 ГБ | Чёрный Титан — от 72 990 ₽ → iPhone 15 Pro Max 256 ГБ | Синий Титан — от 57 990 ₽ → iPhone 14 Pro 128 ГБ | Тёмно-фиолетовый — от 37 990₽
🔥6🥰2❤🔥1🤩1
Берём верный выгодный курс на эти выходные 🔥 Сохраним низкие цены до понедельника. Поэтому обновиться для вас станет особым удовольствием! 🎨🎨🎨🎨 🎨🎨🎨🎨 🎨🎨🎨🎨 Осталось выбрать 🎨🎨🎨🎨 цвет и объём памяти. ⠀ → Полный прайс на модели.
🔥6🤩3❤🔥1😍1
🤍🤍🤍🤍🤍 iPhone с историей с гарантией 1 год. → iPhone 17 Pro Max 256 ГБ | Космический оранжевый — от 89 990 ₽ → iPhone Air 256 ГБ | Космический чёрный — от 67 990 ₽ → iPhone 16 Pro Max 512 ГБ | Чёрный Титан — от 74 990 ₽ → iPhone 15 128 ГБ | Голубой — от 36 990 ₽ → iPhone 14 Pro 128 ГБ | Тёмно-фиолетовый — от 37 990₽
❤4🤩2❤🔥1😍1
🤍🤍🤍🤍🤍 iPhone с историей с гарантией 1 год. → iPhone 17 Pro Max 256 ГБ | Космический оранжевый — от 89 990 ₽ → iPhone Air 256 ГБ | Небесно-голубой — от 67 990 ₽ → iPhone 16 Pro Max 256 ГБ | Натуральный Титан — от 64 990 ₽ → iPhone 15 Pro Max 256 ГБ | Синий Титан — от 57 990 ₽ → iPhone 13 Pro 128 ГБ | Небесно-голубой — от 33 990₽
🔥6👍3❤2❤🔥1💔1🤩1😍1
Менеджеры перегружены: ведь цены слишком хороши ⚠️ Так что лучше звоните — расскажем о наличии и вашей выгоде быстрее. 8 (843) 500-52-15 📞
🔥7❤🔥1🤩1
«Авито» снова в App Store 🛍 Скачивайте и рассекайте по волнам объявлений, пока его снова не удалили. → Установить на iPhone.
🔥13❤🔥8👍3🤩1🥰1
Сэкономьте десятки тысяч при покупке нового iPhone 🔥 Ваш старый уже обесценивается, но если сдать его нам сейчас, то заберём за дорого очень дорого! И ещё скидку до 5 000 ₽ сверху к этой оценке добавим! Узнаете, во сколько вам обойдётся новый iPhone → в чате с нами 🔗
❤🔥7👍3🤩2😍1
Apple анонсировала релиз новых устройств на следующей неделе ⚡️ Ожидается, что 28 Октября в формате пресс-релизов нам могут показать iMac, MacBook и iPad. Можем лишь гадать, но слоган презентации «Pro and tell» похож на игру слов и отсылку к «Show and Tell» — школьной традиции, когда дети приносят любимую вещь, показывают её и рассказывают о ней. Если переводить более дословно, то получается «Профи рассказывают». …
🔥11🤩2😍1
🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨 Поделили iPhone 18 Pro на много мелких частей… 🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨 Чтобы напомнить, что с оплатой можно поступить точно также. 🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨 Пользуйтесь уже сегодня, а заплатите как-нибудь потом благодаря рассрочке. 🎨🎨🎨🎨🎨 🎨🎨🎨🎨🎨
🤩9😍8❤🔥4custom 59969078858696658084❤3🔥3
Showing the 12 most recent of 171 posts we hold for @rebro_store_ru. 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.
@rebro_store_ru edited 11 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The 6 most recent of 8 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Что хотите узнать больше всего?
The shares total 174%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Финал: кто угадает?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Здесь уже посложнее…
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Тут всё очевидно! Или нет? 🤔
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Ну и напоследок! Заабузить — это…
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Тапать — это…
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 171 most recent posts we hold, published 2 August 2026 to 25 October 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.
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 7 registered channels — 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 26 October 2026 — this entry's latest reading, not the date you are reading this.
“rebro” (@rebro_store_ru), 55,033 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/rebro_store_ru.
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.