Channel
@Offshore_Fresh
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
607subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001797320531 |
|---|---|
| Type | Channel |
| Username | @Offshore_Fresh |
| Description | Пространство лёгкости🍃 РЕЖИМ РАБОТЫ👇🏻 ПН-ЧТ - с 8:00 до 21:00 ПТ - с 8:00 до 23:00 СБ - с 10:00 до 23:00 ВС - с 10:00 до 21:00 +7 (8332) 22-01-11 Ленина, 84 (Киров) Inst: https://www.instagram.com/offshore.fresh ВК: https://vk.ru/offshore.fresh |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/Offshore_Fresh |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 03:05 | 607 | no change |
| 7 Aug 2026, 18:23 | 607 | first reading |
12 posts held, back to 28 April 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 12 posts for this entry, the most recent from 15 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 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 6 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.
117 reactions across 12 posts, in 15 distinct kinds. The most used accounts for 42.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 50 | 42.7% | |
| ❤🔥 | 28 | 23.9% | |
| 🍓 | 8 | 6.84% | |
| 🌭 | 6 | 5.13% | |
| 🦄 | 5 | 4.27% | |
| ⚡ | 3 | 2.56% | |
| 👍 | 3 | 2.56% | |
| 💘 | 3 | 2.56% | |
| 🏆 | 2 | 1.71% | |
| 🐳 | 2 | 1.71% | |
| 👀 | 2 | 1.71% | |
| 💊 | 2 | 1.71% | |
| 🍾 | 1 | 0.855% | |
| 😁 | 1 | 0.855% | |
| 🤝 | 1 | 0.855% |
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 117reactions 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 28 April 2026 to 15 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.
Друзья, важная новость для наших постоянных гостей!🌿 Offshore Fresh трансформировался в новый проект, но главное осталось неизменным - наша связь с вами. Ваша бонусная карта Offshore Fresh никуда не сгорела! Мы бережно её сохранили и обновили, чтобы копить баллы на любимые завтраки и напитки стало еще приятнее. Забегайте в гости к Филу (теперь мы Feel Bloom🌸) - за классным вайбом, свежими боулами, фрешами и эстети…
❤4❤🔥4🍓2
Подписывайтесь на наш проект FEEL BLOOM
❤2👀2❤🔥1👍1
Я верю, что забота о себе начинается с простых вещей - например, с того, что мы выбираем каждый день. В Feel Bloom я собрал блюда, которые помогают поддерживать баланс, дарят энергию и при этом остаются по-настоящему гастрономичными. В основе моего подхода - качественные ингредиенты, продуманные сочетания и внимание к деталям. Особое место здесь занимают смузи. Каждый из них можно сделать еще более функциональным, …
❤4❤🔥1👍1
P.S. Новое место встречи - FEEL BLOOM. Присоединяйтесь к нам!
🍓3🍾1🤝1
Чувствовать себя хорошо. Чувствовать лёгкость и тишину внутри. Чувствовать, как ты расцветаешь изнутри. В этом - FEEL BLOOM.
❤7❤🔥4💊2💘2😁1
А что, если мы скажем, что обновление уже завтра?🤫
❤🔥10🦄3🌭2
За каждым идеальным блюдом и напитком стоит тихое мастерство. Наша команда. Искусство. Момент.🫰🏼
❤12🏆2❤🔥1🦄1
Photo, posted without a caption
❤🔥3🍓1🐳1
Завтрак, обед или ужин в #офшорфреш - это всегда маленький перерыв на себя.
❤2🍓2👍1💘1
Основа хорошего приёма пищи - баланс и простота⚖️ Мы нашли этот баланс в «Деревенском» салате: свежие овощи, зелень и масло авокадо создают лёгкое, но насыщенное дополнение к любому блюду. Пекинская капуста, огурец, петрушка, укроп - знакомый вкус, который работает каждый раз. Ничего лишнего, только то, что действительно нужно🌿
❤7⚡3❤🔥2
Long weekend mood: ON👌🏼 Offshore Fresh - твоё место силы на майские. Бронирование: +7 (8332) 22-01-11
❤4❤🔥1🐳1
Наш пушистый гость🐾 Мы не готовы ограничивать вас и всегда рады видеть ваших хвостатых друзей. Каждому нальём водички, накормим огурчиками и задарим любовью!
❤8🌭4❤🔥1🦄1
Showing the 12 most recent of 12 posts we hold for @Offshore_Fresh. 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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Offshore Fresh” (@Offshore_Fresh), 607 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Offshore_Fresh.
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.