Еще чучуть отдыхаем и возвращаемся в Хабаровск
👍28❤15🙏11🔥3

Channel
@mrfey888
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
15,656subscribers
-66 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003174220785 |
|---|---|
| Type | Channel |
| Username | @mrfey888 |
| Created | Between 1 September 2025 and 30 November 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/mrfey888 |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 19 Sept 2026, 17:21 | 15,656 | -6 |
| 17 Sept 2026, 07:38 | 15,662 | -7 |
| 15 Sept 2026, 05:57 | 15,669 | -7 |
| 13 Sept 2026, 15:41 | 15,676 | +1 |
| 11 Sept 2026, 18:39 | 15,675 | -10 |
| 9 Sept 2026, 04:00 | 15,685 | -7 |
| 5 Sept 2026, 23:38 | 15,692 | -5 |
| 3 Sept 2026, 17:15 | 15,697 | -2 |
| 2 Sept 2026, 10:44 | 15,699 | -5 |
| 1 Sept 2026, 10:06 | 15,704 | -2 |
| 31 Aug 2026, 11:24 | 15,706 | -7 |
| 30 Aug 2026, 10:33 | 15,713 | +2 |
| 29 Aug 2026, 11:44 | 15,711 | -2 |
| 28 Aug 2026, 14:36 | 15,713 | -2 |
| 27 Aug 2026, 15:59 | 15,715 | -13 |
| 26 Aug 2026, 13:18 | 15,728 | +1 |
| 25 Aug 2026, 10:14 | 15,727 | -1 |
| 22 Aug 2026, 15:34 | 15,728 | +1 |
| 21 Aug 2026, 08:18 | 15,727 | +6 |
| 20 Aug 2026, 10:32 | 15,721 | first reading |
23 posts held, back to 15 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 52 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 27 August 2026 |
|---|---|
| Posts held | 23 (15 June 2026 – 27 August 2026) |
| Views total | 2,400 |
| Reactions total | 57 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:20 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 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.
1,223 reactions across 21 posts, in 10 distinct kinds. The most used accounts for 37.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 458 | 37.4% | |
| 🔥 | 381 | 31.2% | |
| ❤ | 339 | 27.7% | |
| 😁 | 18 | 1.47% | |
| 🙏 | 11 | 0.899% | |
| 🤣 | 5 | 0.409% | |
| 🥰 | 4 | 0.327% | |
| 🥴 | 3 | 0.245% | |
| 👎 | 2 | 0.164% | |
| 🤝 | 2 | 0.164% |
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 22 of the 23 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,223 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 15 June 2026 to 27 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @mrfey888. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 23 most recent posts we hold for this entry, published 15 June 2026 to 27 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Еще чучуть отдыхаем и возвращаемся в Хабаровск
👍28❤15🙏11🔥3
🍜 Фунчоза с морепродуктами в креветочном масле 🦐 Ингредиенты 🥢 Фунчоза — 4 пучка Тигровые креветки — 300 г Креветочные головы — около 100 г Кальмар — 200–300 г Чеснок — 1 головка Имбирь, лук-порей Соевый соус — 3 ст. л. Тёмный соевый — 2 ст. л. Устричный соус — 1 ст. л. Сахар — 3 ч. л. Белый перец — 1 ч. л. Вода — 200 мл Рисовое вино — немного Масло — для жарки Готовим по-китайски 🇨🇳 Фунчозу замочить в воде 40–60 °…
❤46🔥23👍7
ЛИМОНАД ЛАГИДЗЕ Ингредиенты: 4 лимона 120 г сгущённого молока 600 мл газированной воды Лёд Приготовление: Очистить лимоны от кожуры. Добавить сгущёнку и стакан газированной воды. Пробить всё в блендере. Перелить в кувшин и добавить оставшуюся газированную воду. Подать со льдом. Для более сладкого вкуса — 150 г сгущёнки. 🇨🇳В Китае сказали бы: 酸甜爽口 — кисло-сладко и освежающе. Лучше пить сразу. Если оставить в холо…
🔥54❤10
Photo, posted without a caption
👍49❤16
Video message, posted without a caption
🔥33❤8
Video message, posted without a caption
❤25👍21
Video message, posted without a caption
👍49🔥16❤3
🍙 Рисовые котлеты в мраморной говядине — необычный рецепт, который в Китае любят и взрослые, и дети! На первый взгляд кажется, что это обычные рисовые шарики, но стоит сделать первый укус — и вы поймете, почему это блюдо так популярно. Внутри нежная начинка из риса, овощей, грибов, колбасы и нори, а снаружи — тонкий слой мраморной говядины, который после обжарки становится сочным, ароматным и невероятно вкусным. Пол…
❤32🔥24👍7
🥗 Китайский салат из лука-порея по рецепту Мистера Фэя Хрустящий, освежающий и слегка острый салат, который в Китае часто подают как холодную закуску. Минимум ингредиентов, максимум вкуса — благодаря выдержанному уксусу, кунжутному маслу и жареному арахису. ⸻ Ингредиенты * Шкурка (зелёная часть) лука-порея — 1 стебель * Острый зелёный перец — 2 шт. * Кинза — 1 небольшой пучок * Лёд — для охлаждения (по желанию) *…
👍40🔥14❤7
🔥 Куриные бедра по-китайски, которые тают во рту! Если вы думаете, что курицу уже невозможно приготовить по-новому, значит, этот рецепт вас точно удивит. Нежное мясо куриных бедер медленно томится в густом кисло-сладком соусе с чесноком, имбирем и помидорами черри. За это время курица становится настолько мягкой, что буквально распадается на волокна, а соус получается насыщенным, ароматным и идеально обволакивает ка…
👍53❤10🔥9
Карифанки 🫂 Напоминаю что у меня можно приобрести Цай дао 🔪 Цена его 4500₽ Для заказа пишите пожалуйста @elizshaa @elizshaa Отправим по Рф
👍26❤13🔥9
🦪 Мидии в фирменном соусе по рецепту Мистера Фэя Сочные мидии с ароматом имбиря, чеснока, зеленого лука и насыщенным азиатским соусом. Готовятся быстро, а вкус получается ресторанного уровня. ⸻ Ингредиенты * Мидии — 1 кг * Имбирь — 3–4 пластинки * Зеленый лук — небольшой пучок (для варки) * Зеленый лук — 2 пучка (для соуса) * Чеснок — 3 головки * Перец чили — по вкусу * Бадьян — 1 звездочка * Рисовое вино — 4 ст.…
👍47❤20🔥9
Showing the 12 most recent of 23 posts we hold for @mrfey888. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Named by 2 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“MR.FEY🇨🇳” (@mrfey888), 15,656 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/mrfey888.
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.