Официальный канал хакерспейса CADR.
Группа для общения: @cadr_hackerspace
Сайт: https://cadrspace.ru
Для связи: @a_v_p
Рекламу не размещаем и не продаём.
Поддержите нас! → https://sobe.ru/na/cadr
Created
17 January 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
2 measurements taken within a single day. 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 196–198 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
8 Aug 2026, 11:35
197
no change
7 Aug 2026, 17:31
197
first reading
Engagement
15 posts held, back to 10 November 2025 — 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 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
91.1%
avg views ÷ 197 subscribers
Avg views / post
180
2 posts measured
Reaction rate
1.39%
reactions ÷ views · ER floor
Posts in window
2
of 15 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 26 July 2026
Posts held
15 (10 November 2025 – 26 July 2026)
Views total
359
Reactions total
5
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 11:35 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.
What this channel posts
Photos
253
Videos
41
Links
129
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
1m 54s
Average length
23s
Measured directly from 5 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
75 reactions across 14 posts, in 10 distinct kinds. The most used accounts for 34.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
26
34.7%
🔥
21
28.0%
🎉
8
10.7%
👏
7
9.33%
🤮
4
5.33%
🍾
3
4.00%
😱
3
4.00%
❤
1
1.33%
😁
1
1.33%
🤩
1
1.33%
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 14 of the 15 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 75reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 10 November 2025 to 26 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.
Выражаем 3D-благодарность @MityaR за донат фотополимерного принтера в CADR. Мы уже успели сделать принтеру шапочку из фольги и напечатать на нём губку Серпинского (не для мытья посуды, а просто для украшения и тестирования.) С новым принтером нам открываются новые возможности, которые мы будем использовать.
Поздравляем всех причастных с днём радио Теслы-Эдисона-Герца-Попова-Брандли-Лоджа-Боше-Де Муро-Маркони и желаем хорошего прохождения, приемлемого КСВ и скидок на оборудование!
И на всякий случай не повторяйте изображённое на фото. А если повторили, то не включайте и вообще чтите и соблюдайте технику безопасности. 73!
Прогресс по большому принтеру REPLICADR-L:
- Поставил сопло 0.8мм.
- Настроил смещение BLTouch сенсора относительно сопла в Klipper.
- Заново настроил Z offset для BLTouch.
- Сделал больше точек на карте высот, провёл калибровку.
- Заказал DIN 912 винты 50мм для крепления частей экструдера. Старые винты, которые под крест, уже с почти "слизанной" шляпкой, всё равно их менять надо. Да и удобнее будет всё шестигранни…
Откалибровал PID нагревателя стола и экструдера REPLICADR-L, построил заново меш стола. Ещё требуется перенастроить pressure advance и возможно подкрутить коэффициент экструзии, ну и поддержки пока адовые, надо сделать их легко отделяемыми (чего нам удалось сделать на меньшем принтере REPLICADR-M.) Но результат уже гораздо лучше, чем был. Печать идёт стабильно, скорость можно сделать ещё выше.
На видео показана н…
При работе с нашим большим самодельным большим 3D-принтером REPLICADR-L мы столкнулись с проблемой неравномерной высоты слоя.
Благодаря наводке участника Demson dms из кадрогруппы мы выяснили, что проблема была в нагреве стола. Провели замеры индикатором и заметили, что при включении нагрева (в режиме watermark) стол уводило на 0.1мм. Суть режима управления watermark — греет до уставки, ждёт падения температуры на…
Hack New Year, кадровчане🎄
Этот год для хакерспейса CADR получился не столь насыщенным на события, но значимость этих событий оказала большое влияние на нас.
Мы переехали в новое помещение, приобрели новое оборудование, пересобрали и оживили REPLICADR, открыли для себя Meshtastic, а также получили в донат 3D-принтер Flying Bear Ghost 5.
Спасибо всем, кто в этом году помогал нам, посещал новое помещение и участвова…
🎉8🍾3👍3❤1
Showing the 12 most recent of 15 posts we hold for @cadr_space. 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.
Citation-graph rank
Citation-graph rank — 497,057 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 August 2026 — this
entry's latest reading, not the date you are reading this.
“CADR SPACE” (@cadr_space), 197 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/cadr_space.
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.