😁 Курьеры - самые благородные люди! 👑 БОГАТЫЙ КУРЬЕР
🤣14❤8🔥2🏆1

Channel
@BogatiyKurier
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry
11,653subscribers
+1,265 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001863675913 |
|---|---|
| Type | Channel |
| Username | @BogatiyKurier |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/BogatiyKurier |
Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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, 04:56 | 11,653 | +61 |
| 16 Sept 2026, 01:18 | 11,592 | +68 |
| 14 Sept 2026, 07:38 | 11,524 | +44 |
| 12 Sept 2026, 15:20 | 11,480 | +59 |
| 10 Sept 2026, 15:36 | 11,421 | +98 |
| 7 Sept 2026, 12:19 | 11,323 | +129 |
| 4 Sept 2026, 16:17 | 11,194 | +43 |
| 2 Sept 2026, 23:56 | 11,151 | +38 |
| 1 Sept 2026, 19:25 | 11,113 | +24 |
| 31 Aug 2026, 16:47 | 11,089 | +25 |
| 30 Aug 2026, 18:54 | 11,064 | +35 |
| 29 Aug 2026, 19:36 | 11,029 | +27 |
| 28 Aug 2026, 19:23 | 11,002 | +25 |
| 27 Aug 2026, 19:14 | 10,977 | +22 |
| 26 Aug 2026, 21:45 | 10,955 | +26 |
| 25 Aug 2026, 23:34 | 10,929 | +23 |
| 24 Aug 2026, 23:33 | 10,906 | +45 |
| 23 Aug 2026, 12:05 | 10,861 | +47 |
| 21 Aug 2026, 19:25 | 10,814 | +38 |
| 20 Aug 2026, 14:25 | 10,776 | first reading |
60 posts held, back to 31 July 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 39 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 2 September 2026 |
|---|---|
| Posts held | 60 (31 July 2026 – 2 September 2026) |
| Views total | 43,742 |
| Reactions total | 508 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 01:57 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.
Measured directly from 20 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.
1,252 reactions across 60 posts, in 13 distinct kinds. The most used accounts for 36.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 453 | 36.2% | |
| 🤣 | 243 | 19.4% | |
| 🔥 | 160 | 12.8% | |
| 🗿 | 85 | 6.79% | |
| 🤬 | 78 | 6.23% | |
| 🤯 | 75 | 5.99% | |
| ⚡ | 65 | 5.19% | |
| 🤔 | 31 | 2.48% | |
| 🏆 | 29 | 2.32% | |
| 💯 | 9 | 0.719% | |
| 😭 | 9 | 0.719% | |
| 👏 | 8 | 0.639% | |
| 👍 | 7 | 0.559% |
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 60 of the 60 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 1,252 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 60 most recent posts we hold, published 31 July 2026 to 2 September 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.
😁 Курьеры - самые благородные люди! 👑 БОГАТЫЙ КУРЬЕР
🤣14❤8🔥2🏆1
🔥 Кейс: возврат заказа по регламенту → корректировка 3000 ₽ + блокировка 👤 Герой: Устаев Сухроб — курьер из Ростова-на-Дону @soxra03, тариф Экспресс 📌 Суть проблемы: • Курьер выполнял заказ из магазина «Пятёрочка». • Получатель не выходил на связь. • Действуя по регламенту: — попытался связаться с клиентом — оформил возврат через сервис — вернул заказ обратно в магазин • Несмотря на корректные действия: • Прилетела…
🔥10⚡6❤3
🌐 ФИШКА в Яндекс Грузовом, о которой почти никто не знает! Речь про предзаказы — функцию, которую многие игнорируют, а зря 👀 🚚Мы сделали полный разбор: — как это работает — какие плюсы даёт — где есть подводные камни Если хотите выжимать максимум из заказов — обязательно посмотрите👇 Приятного просмотра! Ролик уже на YouTube канале 👑 БОГАТЫЙ КУРЬЕР⬇️ https://www.youtube.com/results?search_query=БОГАТЫЙ+КУРЬЕР или…
⚡6❤4🔥3🗿2😭1
🤯 Роботов-курьеров выгнали с улиц Шеффилда! ❌ Компания Starship Technologies заявила, что её парк роботов-доставщиков больше не будет работать в британском Шеффилде В марте компания запустила в городе пилотный проект, в рамках которого роботы использовались для доставки еды через Uber Eats 🤬 Решение было принято после того, как несколько роботов были повреждены вандалами. На их крышах написали «Вон с нашей улицы»,…
🏆8❤2🤣1
🎓 С 1 СЕНТЯБРЯ, СТУДЕНТЫ! Сегодня отдельное поздравление всем, кто умудряется совмещать пары, зачёты и дедлайны с выполнением заказов 😅 Желаем, чтобы в новом учебном году преподаватели были понимающими, экзамены сдавались с первого раза, а после пар оставались силы и время выйти на линию! С Днём знаний! Успехов в учёбе и хорошего дохода ❤️ 👑 БОГАТЫЙ КУРЬЕР
❤19🔥6⚡5
📦 Тяжелый заказ на 18-й этаж без лифта! 😮💨 Недавно нам в предложку написал курьер и рассказал историю, прочитав которую уже хочется отдохнуть и перевести дыхание… Не могу не поделиться этой историей. Попался сегодня тяжелый заказ и все бы ничего, да только лифт в доме не работал, а получатель был на 18-м этаже. Тащил, чуть не помер по дороге. На последнем этаже в глазах аж темнеть начало. В итоге, дотащил, отдал з…
🤬17❤11🔥3🗿3
🍕 300 пицц на чужой адрес: в Польше задержали необычного «заказчика» В польском Щецине задержали молодого человека, который оформлял крупные заказы пиццы на чужие имена и адреса, выбирая оплату при получении. В качестве получателей он чаще всего указывал известных политиков и СМИ. Масштабы заказов впечатляют: стоимость одного из них превышала 37 000 злотых (около 8 500 евро), а в другой раз мужчина попытался заказ…
🤣13🗿6❤3
😳 В Москве девушка поделилась неожиданной встречей в парке с робопсом-курьером! 👑 БОГАТЫЙ КУРЬЕР
❤10🤔8🤯4🤬2🔥1
😐 Какие последние чаевые вы получали? 👑 БОГАТЫЙ КУРЬЕР
🤣18❤5😭5⚡1
🌐Топ-5 способов привлечь рефералов Приводи друзей и зарабатывай БОЛЬШЕ в Яндекс Доставке! В Парке Богатый Курьер ты можешь получать доход не только с заказов: — 🎯 выполнение еженедельных целей — 🎁 участие в еженедельных розыгрышах — 👥 доход на реферальной программе Используй все возможности уже сейчас!💸 Ролик уже на YouTube канале 👑 БОГАТЫЙ КУРЬЕР⬇️ https://www.youtube.com/results?search_query=БОГАТЫЙ+КУРЬЕР или…
❤7🔥4⚡2
🤯 Курьеры на автомобилях премиум-класса перестали удивлять россиян! ⚡️ Больше половины (58%) клиентов спокойно относятся к курьерам доставки, которые доставляют заказы на машинах люксового сегмента Респонденты объясняют это пониманием того, что жизненные обстоятельства бывают разными, это показало исследование DPD Делитесь в комментариях, на чем вы выполняете заказы!👇 👑 БОГАТЫЙ КУРЬЕР
❤9🗿4🤔3
😅 Вкусно и бесплатно 👑 БОГАТЫЙ КУРЬЕР
🤣19🔥3❤1🗿1
Showing the 12 most recent of 60 posts we hold for @BogatiyKurier. 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.
💰 Получалось ли у вас зарабатывать больше 100 000 ₽ в месяц на доставке?
Shares as published, totalling 101%. 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 60 most recent posts we hold, published 31 July 2026 to 2 September 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“БОГАТЫЙ КУРЬЕР” (@BogatiyKurier), 11,653 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/BogatiyKurier.
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.