Telegram RegisterThe public register of Telegram
Telegram profile photo for Всё о корпусах — дизайн, прототипы, производство

Channel

Всё о корпусах — дизайн, прототипы, производство

@edp_day

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,134subscribers

+4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001787563373
TypeChannel
Username@edp_day
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/edp_day

Growth

1,1291,1341,131.57 August 2026 — 1,130 subscribers7 August 2026 — 1,130 subscribers10 August 2026 — 1,132 subscribers14 August 2026 — 1,129 subscribers17 August 2026 — 1,130 subscribers20 August 2026 — 1,132 subscribers27 August 2026 — 1,134 subscribers30 August 2026 — 1,133 subscribers8 September 2026 — 1,134 subscribers7 August 20268 September 2026
9 measurements spanning 32 days, net +4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,128–1,135 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 10:211,134+1
30 Aug 2026, 13:061,133-1
27 Aug 2026, 05:451,134+2
20 Aug 2026, 08:521,132+2
17 Aug 2026, 12:081,130+1
14 Aug 2026, 00:551,129-3
10 Aug 2026, 19:231,132+2
7 Aug 2026, 23:481,130no change
7 Aug 2026, 17:411,130first reading

Engagement

6 posts held, back to 20 July 2026the 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
1m 48s
Average length
54s

Measured directly from 2 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.

Reaction mix

22 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 59.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1359.1%
👍313.6%
💯313.6%
🔥313.6%

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 22 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 20 July 2026 to 7 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.

Recent posts

7 Aug 2026, 05:34 UTC191 views4 reactionsread 7 August 2026
Photo

Дизайн корпуса не всегда начинается с дизайна. В проекте ЭЗС «АТТАР Солана» мы начали с компоновки. У станции четыре зарядных коннектора. Кабели длинные, тяжёлые и жёсткие — их нужно удобно вытянуть к машине, а после зарядки убрать так, чтобы они не болтались и не путались. При этом внутри станции — силовые модули и другая электроника. Нужно организовать вентиляцию, отдельно отводить горячий воздух от силовых моду

👍3🔥1

5 Aug 2026, 05:31 UTC253 views7 reactionsread 7 August 2026
Photo

В техническом задании может быть 50 требований. Но это не значит, что все 50 одинаково важны. У разных участников проекта свои интересы. Пользователю нужно, чтобы устройство было удобным. Производству — чтобы его было проще изготовить. Сборщикам — собрать. Сервису — обслуживать. Бизнесу — чтобы всё это укладывалось в экономику проекта. И довольно быстро требования начинают конфликтовать. Можно сделать корпус деше

6🔥1

4 Aug 2026, 07:11 UTC281 views0 reactionsread 7 August 2026
Photo

Видим сейчас интересный процесс — все больше задач от заказчиков формулируется с помощью нейросетей, но и с нашей стороны происходит тоже самое — все больше таких задач прогоняется через нейронку, а уже потом смотрится живым спецом. И в целом, в этом нет ничего плохого или негативного. Просто та подготовительная работа, которая раньше делалась со стороны клиента (формулирование требований, задач, результатов, вводны

31 Jul 2026, 06:17 UTC415 views1 reactionsread 7 August 2026
Video

Пользователю не нужен ваш продукт. Ему нужно решить свою задачу. Допустим, мы разрабатываем систему охлаждения. Можно сделать ее мощнее всех аналогов. Но клиент будет сравнивать не только цифры в характеристиках, а разные способы решить свою задачу. Иногда выиграет менее мощное устройство. Иногда — вообще другое техническое решение. Поэтому при разработке полезно несколько раз спросить: «Чтобы что?». Зачем нужн

1

27 Jul 2026, 11:31 UTC490 views6 reactionsread 7 August 2026
Video

Почему корпус может месяцами ходить от дизайнера к конструктору и обратно? Потому что одно решение приходится проверять с нескольких сторон: удобно ли пользователю, можно ли это произвести и сколько всё это будет стоить. Дизайн и конструкция редко рождаются последовательно: чаще это несколько итераций туда-обратно. А иногда дизайнер и конструктор ещё и начинают тянуть продукт каждый в свою сторону. Об этом расска

💯32🔥1

20 Jul 2026, 04:54 UTC532 views4 reactionsread 7 August 2026
Photo

Покупной корпус не всегда оказывается лучшим решением. В одном из проектов мы разрабатывали браслет для строителей. Типовой корпус не подошёл сразу по нескольким причинам: в него не помещалась вся электроника, браслет был слишком громоздким и неудобным, а после работы на стройке быстро терял внешний вид. Поэтому корпус решили разрабатывать с нуля. Носимое устройство должно быть эргономичным по умолчанию. Неважно,

4

Showing the 6 most recent of 6 posts we hold for @edp_day. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Named by 1 registered channel — 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.

Cite this entry

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 September 2026 — this entry's latest reading, not the date you are reading this.

“Всё о корпусах — дизайн, прототипы, производство” (@edp_day), 1,134 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/edp_day.

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.