Channel
@engineerscetch
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Declared links · Cite this entry
39subscribers
+1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002315479257 |
|---|---|
| Type | Channel |
| Username | @engineerscetch |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 17 September 2026 |
| On Telegram | t.me/engineerscetch |
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 30 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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 |
|---|---|---|
| 9 Sept 2026, 20:18 | 39 | +1 |
| 10 Aug 2026, 21:15 | 38 | no change |
| 8 Aug 2026, 08:33 | 38 | first reading |
17 posts held, back to 21 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 17 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
156 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5458850673837764747 | 89 | 57.1% | |
| custom 5451715229920546594 | 24 | 15.4% | |
| 🔥 | 18 | 11.5% | |
| custom 5375433634331244525 | 13 | 8.33% | |
| custom 5404402909569905089 | 10 | 6.41% | |
| custom 5458582891216790971 | 2 | 1.28% |
Custom emoji. 5 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 17 of the 17 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 156 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 21 July 2026 to 9 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.
#фандомный_движ #фандомнаябитва2026 #неправославный_пейринг Команда ФБ принесла на неформат ✨THE ШТУКУ✨ Круглосименки - канон, и сейчас мы и наши сорок слонов об этом станцуем! И только попробуйте после этого не шиппнуть этих двоих хотя бы на полшишечки 😁
custom 54517152299205465945custom 54588506738377647473
Любимая командочка выдала шедевральный шедевр (сделаем круглосименошные шедевры традицией неформата)
custom 54588506738377647472
Posted without readable text
custom 54588506738377647479
Posted without readable text
custom 54588506738377647477
Posted without readable text
custom 54588506738377647477
Posted without readable text
custom 545885067383776474711custom 54044029095699050891
Так как моя писалка сдохла в муках реала (вместе с the штукой на фб, которую нет сил доделывать), а вот способность рандомно генерировать идеи — нет, давайте интерактив. Вы мне: либо мою аушку, а я вам три факта невошедшие в фики, в стиле "я не договорил!", либо просто рандомную аушку и персонажей, а я вам — три рандомных факта об этих персонажах в этой аушке.
custom 54517152299205465944custom 54588506738377647473custom 53754336343312445251
Мы начинаем записывать альбом «Яги», товарищи! Считаю, что это грандиозное событие🤩
custom 54588506738377647474custom 54517152299205465942custom 53754336343312445251
Где ты будешь об этом орать? Везде! НАС ЖДЕТ АЛЬБОМ ЯГИ ПРЯМ СТУДИЙКИ ПРЯМ КРАСИВЫЕ Ну кайф же! Ну охрененно ж! Определённо лучшая новость среди всей сегодняшней моей поебени с элементами приключений
🔥3custom 54588506738377647473custom 54517152299205465942custom 53754336343312445251
Слушайте, а покидайте, кто может, кукухоподдержательного контента. Ну там песен, коротеньких фичков для перечитывания. Вот что-нибудь такого, чтоб "все точно будет окей, даже если сейчас пиздец и/или заебался". А то чет меня нагнал легкий пиздец, так что остается только ржать, иначе придётся плакать
custom 54588506738377647479custom 53754336343312445251custom 54517152299205465941
И стоило мне сегодня написать про фб, как у нас бахнулся деанон низкорейтинговых мибблов! История на самом деле веселая. Буквально: Я: да не буду я, писать про Круглова. Слишком уважаю, сложно отношусь и вообще. Тоже я: ладно, он мне нужен как офигенный образ, но только дженом. Снова я: а не написать ли мне круглосименок? Сказала бы, что сложнее всего было писать диссы на любимое ПИ, но я слишком хорошо знаю, что и в…
custom 54588506738377647477custom 54517152299205465944custom 53754336343312445251
Эта фандомная битва началась с квеста "сверстай визитку за два часа". Да, я теперь могу смело орать, что визитка любимой команды мюзиклов собрана в авральном режиме прекрасным визуальщиком, а сверстана мной. Учитывая, что последний раз я нормально верстала на ао3 для команды Икара года три назад, с которых там несколько поменялся список тегов, которые ао3 жрет нормально, а времени на эксперименты не было от слова сов…
🔥7custom 54588506738377647473custom 53754336343312445251custom 54517152299205465941
Showing the 12 most recent of 17 posts we hold for @engineerscetch. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 5 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.
One URL this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Зарисовки пишущего инженера” (@engineerscetch), 39 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/engineerscetch.
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.