File, posted without a caption
custom 53191769329175438483custom 54225462515875278502custom 54720306786336845922

Channel
@frsprod
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
167subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002744729794 |
|---|---|
| Type | Channel |
| Username | @frsprod |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 2 times, most recently 12 October 2026 |
| On Telegram | t.me/frsprod |
Personal blog — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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 |
|---|---|---|
| 2 Oct 2026, 05:59 | 167 | -3 |
| 17 Sept 2026, 00:38 | 170 | -2 |
| 8 Sept 2026, 14:39 | 172 | -3 |
| 29 Aug 2026, 15:34 | 175 | +1 |
| 22 Aug 2026, 20:23 | 174 | +1 |
| 15 Aug 2026, 16:49 | 173 | +1 |
| 8 Aug 2026, 14:31 | 172 | no change |
| 8 Aug 2026, 04:16 | 172 | +2 |
| 7 Aug 2026, 16:51 | 170 | first reading |
10 posts held, back to 31 March 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 10 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
291 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 34.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5422546251587527850 | 99 | 34.0% | |
| custom 5319176932917543848 | 93 | 32.0% | |
| custom 5472030678633684592 | 61 | 21.0% | |
| 🔥 | 38 | 13.1% |
Custom emoji. 3 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 10 of the 10 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 291 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 31 March 2026 to 31 July 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.
File, posted without a caption
custom 53191769329175438483custom 54225462515875278502custom 54720306786336845922
Что-то я подпропал в последнее время, не просто так, если что Двигаюсь сейчас сразу в нескольких направлениях: часть под клиентов, часть под себя, ещё пара штук в разработке, о которых пока рано говорить вслух В общем, пока не могу раскрыть все карты, но работа кипит, скучать некогда Расскажу, как только будет что показать. Пока дабы канал не пустовал закину вам своих эстетик фото со старого фотика
custom 542254625158752785011custom 54720306786336845928custom 53191769329175438487
Надеюсь все уже успели чекнуть Гайд По просмотрам все хорошо, вижу сохранения, но мне важен коннект. Накидайте фидбека в комментарии: как вам формат, что оказалось полезным, а где остались вопросы? Все читаю, на интересные вопросы отвечу
custom 542254625158752785013custom 547203067863368459212custom 53191769329175438488
🥵ТОТ САМЫЙ ГАЙД ИЗ ВИДОСА. КАК ЗАКРЫВАТЬ КЛИЕНТОВ ЧЕРЕЗ РАССЫЛКИ⚡ 00:00 - Вступление Почему старые методы поиска клиентов больше не работают. 01:09 - Упаковка Как оформить профиль, чтобы вызывать доверие у дорогих заказчиков. 03:55 - Метод рассылки 5 правил идеального сообщения, на которое захочется ответить. 06:40 - Стратегия поиска Где и как находить платежеспособных клиентов в 2026 году. 11:00 - Итог Главный …
custom 531917693291754384811custom 54225462515875278509custom 54720306786336845928
Набираем 25 реакций и дропаю сам гайд на рассылку
custom 531917693291754384816custom 542254625158752785011custom 54720306786336845929
ТВОИ РАССЫЛКИ = МУСОР🗑 Раскрыл всю правду в новом видео... https://youtu.be/ibbeKzkQni8 https://youtu.be/ibbeKzkQni8 https://youtu.be/ibbeKzkQni8 Показал, как одна грамотная рассылка привела меня к продюсеру на 400к подписоты и чеку в $500 за пак рилсов🤩
custom 531917693291754384813custom 542254625158752785011custom 547203067863368459210
Готовлю для вас что-то действительно важное 👨🦰 На фото - процесс сборки нового ролика, где я решил разобрать тему, которая болит у каждого монтажера
custom 54720306786336845926custom 54225462515875278505custom 53191769329175438482
File, posted without a caption
custom 542254625158752785012🔥9custom 53191769329175438489custom 54720306786336845923
living my best life🤩
🔥23custom 531917693291754384817custom 542254625158752785014custom 54720306786336845922
Оглянись, у тебя спина белая
custom 542254625158752785011custom 53191769329175438487🔥6custom 54720306786336845921
Showing the 10 most recent of 10 posts we hold for @frsprod. 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.
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 2 October 2026 — this entry's latest reading, not the date you are reading this.
“fresko.” (@frsprod), 167 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/frsprod.
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.