Полезный лайфхак 💡 Вполне может случиться так, что этот совет вам пригодится, поэтому запоминайте схему, тем более она очень проста Мудрый Строитель
👀15👏12👍3❤2🤓2😁2

Channel
@mudriystroitel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
404,720subscribers
-3,126 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
| Telegram ID | -1001127375190 |
|---|---|
| Type | Channel |
| Username | @mudriystroitel |
| Description | • Канал о строительстве и ремонте 🛠 @mudriy_admin - писать только по рекламе. @lionsmedia1 @doberman1998 РКН: https://rkn.link/Qxz @Spiral_Miya |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/mudriystroitel |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 83% 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 |
|---|---|---|
| 17 Sept 2026, 16:37 | 404,720 | -153 |
| 15 Sept 2026, 12:40 | 404,873 | -129 |
| 14 Sept 2026, 00:01 | 405,002 | -144 |
| 12 Sept 2026, 06:55 | 405,146 | -183 |
| 10 Sept 2026, 05:02 | 405,329 | -277 |
| 7 Sept 2026, 00:57 | 405,606 | -199 |
| 4 Sept 2026, 09:55 | 405,805 | -95 |
| 2 Sept 2026, 20:53 | 405,900 | -99 |
| 1 Sept 2026, 18:05 | 405,999 | -71 |
| 31 Aug 2026, 19:46 | 406,070 | -52 |
| 30 Aug 2026, 22:23 | 406,122 | -82 |
| 29 Aug 2026, 23:56 | 406,204 | -56 |
| 29 Aug 2026, 02:55 | 406,260 | -79 |
| 28 Aug 2026, 04:24 | 406,339 | -58 |
| 27 Aug 2026, 04:07 | 406,397 | -80 |
| 26 Aug 2026, 01:04 | 406,477 | -81 |
| 24 Aug 2026, 22:16 | 406,558 | -120 |
| 23 Aug 2026, 08:59 | 406,678 | -84 |
| 21 Aug 2026, 23:48 | 406,762 | -107 |
| 20 Aug 2026, 17:02 | 406,869 | first reading |
199 posts held, back to 4 August 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 99 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 22 September 2026 |
|---|---|
| Posts held | 199 (4 August 2026 – 22 September 2026) |
| Views total | 1,716,660 |
| Reactions total | 7,707 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 07:23 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.
Lifetime counters from Telegram’s own channel header, read 22 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 188 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.
12,052 reactions across 199 posts, in 14 distinct kinds. The most used accounts for 54.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6,565 | 54.5% | |
| ❤ | 1,879 | 15.6% | |
| 👀 | 1,052 | 8.73% | |
| 😁 | 966 | 8.02% | |
| 👏 | 883 | 7.33% | |
| 🔥 | 499 | 4.14% | |
| 🤝 | 53 | 0.44% | |
| 🫡 | 43 | 0.357% | |
| 🤓 | 42 | 0.348% | |
| 👌 | 31 | 0.257% | |
| 💯 | 25 | 0.207% | |
| 😍 | 9 | 0.075% | |
| 🤗 | 3 | 0.025% | |
| 🙏 | 2 | 0.017% |
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 199 of the 199 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 12,052 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 199 most recent posts we hold, published 4 August 2026 to 22 September 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.
Полезный лайфхак 💡 Вполне может случиться так, что этот совет вам пригодится, поэтому запоминайте схему, тем более она очень проста Мудрый Строитель
👀15👏12👍3❤2🤓2😁2
На один уровень 😉 Как установить плитку разной толщины на одной линии, без перепадов высот Мудрый Строитель
👍32❤9😁6👀3🔥1
Поддон или плитка? ✏️ Обязательно посмотрите это видео перед тем, как выбрать, что вы будете делать при создании душевой кабины: устанавливать поддон или укладывать плитку Мудрый Строитель
👏11👍5❤3😁2
Оформление стен 🔥 Крутая идея оформления стен в ванной в комбинированной технике, используя плитку различной размерности Мудрый Строитель
👍23❤5👏3
Про теплые полы ☝️ Основные плюсы и минусы, которые стоит учитывать, если вы решили сделать теплые полы у себя дома Мудрый Строитель
👍16👀11😁6👏2💯2🤝2🤓1🤗1
Каркас из арматуры 👌 Как легко и просто закрепить каркас из арматуры в бетонном основании и не ошибиться при просверливании отверстий Мудрый Строитель
😁27👍9❤5👀1
Уличная лестница 👍 Такая уличная лестница станет настоящим украшением для вашего участка, при этом сделать её можно без каких-либо заморочек Мудрый Строитель
👍31😁4❤2👀1
Замечательная дорожка 📝 Как вам моя идея по оформлению дорожек и ступенек на участке? По-моему, очень даже ничего получилось Мудрый Строитель
👍27❤4👀4😁1
Желоб водостока 💧 Монтаж желоба для стока воды во время дождя и таяния снега, надо отметить, что получилось не только надежно, но и красиво Мудрый Строитель
👍45❤10😁5👀1
Из ГРЯЗИ в КНЯЗИ. Как я сделала ремонт за 0 рублей Я живу в небольшой однушке, места хватает с трудом. Давно мечтала обновить интерьер, но сумма на это дело неподъемная 🥲 Думала так и останусь жить в бабушкином ремонте, пока подруга не показала канал Строю в шапке. Там реальный дизайнер показывает, как со вкусом и своими руками дать второе дыхание квартире. Теперь друзья называют меня миллионершой, не верят что с…
❤5👍4😁4👀1👌1
В этом видео вы узнаете, как сделать надежный дверной проем с нуля 🚪 Мудрый Строитель
😁12👏8❤5👀5👍4
Создание армапояса ⚒️ Армапояс — это основа надежности будущей постройки, важно грамотно подходить к его созданию 👉 У этих мастеров получилось отлично! Мудрый Строитель
😁18👍13👀10❤9
Showing the 12 most recent of 199 posts we hold for @mudriystroitel. 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.
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 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Мудрый Строитель” (@mudriystroitel), 404,720 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/mudriystroitel.
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.