Channel
@krechet_workshop
On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
759subscribers
+31 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003019681636 |
|---|---|
| Type | Channel |
| Username | @krechet_workshop |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/krechet_workshop |
Local community — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 |
|---|---|---|
| 13 Sept 2026, 22:39 | 759 | +5 |
| 6 Sept 2026, 09:57 | 754 | +6 |
| 29 Aug 2026, 09:17 | 748 | +5 |
| 22 Aug 2026, 06:48 | 743 | +2 |
| 14 Aug 2026, 08:16 | 741 | +9 |
| 6 Aug 2026, 16:12 | 732 | no change |
| 6 Aug 2026, 10:50 | 732 | +4 |
| 6 Aug 2026, 02:50 | 728 | first reading |
6 posts held, back to 29 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 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 6 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
679 reactions across 6 posts, in 9 distinct kinds. The most used accounts for 52.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 356 | 52.4% | |
| 🔥 | 172 | 25.3% | |
| custom 5348397248994617112 | 106 | 15.6% | |
| 🤯 | 32 | 4.71% | |
| custom 5359372775926547678 | 4 | 0.589% | |
| 🦄 | 4 | 0.589% | |
| 👀 | 3 | 0.442% | |
| custom 5334987205750302732 | 1 | 0.147% | |
| 🎃 | 1 | 0.147% |
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 6 of the 6 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 679 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 29 July 2026 to 3 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 @krechet_workshop. 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 6 most recent posts we hold for this entry, published 29 July 2026 to 3 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.
Хорошие новости! Очищаем нагар со станка, повесили много освещения. Благодаря вашей помощи заказали и уже установили новый кузнечный молот, лазерный станок по пластику и дереву, вакуумный станок. Организовали рабочие места. #дэйли@krechet_workshop
❤72custom 534839724899461711232🔥28custom 53593727759265476784custom 53349872057503027321
Напутственные слова от нашего директора, Сергея Власова:)⚒️ #дэйли@krechet_workshop
🔥55custom 534839724899461711222❤21
#shit_AD_talks Ну, чтомж, меня можно поздравить с первыми сердечными приступами. Первый - мы уронили стендовый реквизит вчера, разбив часть по стыку печати. Второй (сегодняшний) - мы настолько освоились дома, что решили сыграть в прятки. 30 минут тотального прогрева сердца. В итоге, нашлась под ванной, собрала всю пыль, благополучно была от неё протёрта, получила выговор. Кушаем мы хорошо, иногда всё ещё демонстрир…
❤66🦄2🎃1
Наша киса Колбаса всё ещё оправляется после пожара и находится в добрых руках. С ее здоровьем всё в порядке, о ее буднях можно читать в этой группе🙋👇 #дэйли@krechet_workshop
❤34
Сегодня показываем вам наше новое место! Работа кипит. На деньги со сбора куплен молот, его доставка на последнем фото. Принтеры и вся электрика также куплены на деньги со сборов! Спасибо за донаты, репосты, лайки, подписки! Обязательно будем делиться и дальше нашим прогрессом в восстановлении. #дэйли@krechet_workshop
🔥77❤43custom 534839724899461711226
Друзья, сегодня мы прощались со сгоревшей мастерской. И перевозили то немногое, что выжило. В скором времени порадуем вас полноценным репортажем с нового места! Огромное спасибо за помощь - инструменты, донаты, репосты. Мы безмерно благодарны и всё идёт в дело!
❤120🤯32custom 534839724899461711226🔥12👀3🦄2
Showing the 6 most recent of 6 posts we hold for @krechet_workshop. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 84 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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 14 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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Из Кречи (Мастерская "Кречет")” (@krechet_workshop), 759 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/krechet_workshop.
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.