Продолжаем готовить реквизит для выставки детекторов радиации в поисках новых образов. Волшебная палочка. Вот, что не хватало на стенде КБ Радар вместо вот этих скучных ручных досмотровых детекторов.
👍4🔥1

Channel
@atomtoday
On this record: Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
672subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001488251351 |
|---|---|
| Type | Channel |
| Username | @atomtoday |
| Description | Оперативно о радиационной обстановке и ядерных инцидентах. Донаты 💳 5213 2438 2315 0832 (Тинькофф) каналу и системе чатов Проекта Атом Вход в другие чаты и каналы Проекта Атом через @AtomToday_bot |
| Created | 23 November 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/atomtoday |
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 02:16 | 672 | no change |
| 7 Aug 2026, 02:03 | 672 | first reading |
20 posts held, back to 14 April 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 pageof 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 31 July 2026 |
|---|---|
| Posts held | 20 (14 April 2026 – 31 July 2026) |
| Views total | 164 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 02:16 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 7 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.
96 reactions across 13 posts, in 9 distinct kinds. The most used accounts for 42.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 41 | 42.7% | |
| 👍 | 30 | 31.3% | |
| ❤ | 7 | 7.29% | |
| 😭 | 5 | 5.21% | |
| ⚡ | 3 | 3.13% | |
| 😨 | 3 | 3.13% | |
| 😱 | 3 | 3.13% | |
| 🤔 | 3 | 3.13% | |
| 💘 | 1 | 1.04% |
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 13 of the 20 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 96reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 14 April 2026 to 31 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.
Продолжаем готовить реквизит для выставки детекторов радиации в поисках новых образов. Волшебная палочка. Вот, что не хватало на стенде КБ Радар вместо вот этих скучных ручных досмотровых детекторов.
👍4🔥1
Всем привет! накидал небольшую статью по добавлению снимков в подложку atom swift и картописец. Готов ответить на вопросы https://telegra.ph/Dobavlyaem-spektralnuyu-sputnikovuyu-podlozhku-dlya-kartirovaniya-07-08
🔥3❤1
КБ Радар на Урале, север Челябинской области. со 2 по 16 июля. Буду условно доступен по ситуации. Можно планировать личные встречи. Программа минимум: Повторить без фанатизма подход к краям оси ВУРСа, где поток бета частиц с грунта становится заметным на низкой высоте от грунта. Будет использована пара детекторов: газоразрядный детектор Atom Tag с датчиком сбм-20 в новой редакции и слюдяной детектор Atom Pro (не се…
❤5🔥4⚡3
Обновляем реквизит для выставочного стенда "Погладь кота" У этого экземпляра спинка длиннее. А ещё есть хвост. Скоро отправится в ателье вставлять в пузо молнию и немного поменяем набивку. А как прощались в магазине с этим последним экземпляром!
🔥5👍3
Atom.Today ☢️ pinned a video
В темно-синем лесу, где-то рядом с Троицком. Группа Чартер. Физик-ядерщик. Более менее студийный вариант выложен здесь: https://youtu.be/6JISiK1a5g8?is=Rl0GbdHiEHZtInU-
👍3❤1
Atom.Today ☢️ pinned «Про пожары в "Чернобыльской зоне". 1. Локация - около села Тарасовщина Киевской области. Это дальше, чем 50 км от чернобыльской АЭС примерно на юг (направление примерно на Киев). Формально это не 30 км зона отчуждения как все подумали. Но мы же понимаем, что…»
Про пожары в "Чернобыльской зоне". 1. Локация - около села Тарасовщина Киевской области. Это дальше, чем 50 км от чернобыльской АЭС примерно на юг (направление примерно на Киев). Формально это не 30 км зона отчуждения как все подумали. Но мы же понимаем, что 30 км ничего не ограничивается. 2. Цезий-137. Примем радиотоксичность цезия-137 за единицу. Плотность площадного радиоактивного загрязнения по цезию-137 в этом …
🤔3😱3
А есть у нас кто в Болгарии? Если есть желание найти что-нибудь интересное за пределами огороженной территории, пишите. Если там есть миграция радионуклидов за забор, это не сложно подтвердить. Но не прямыми измерениями. Надо искать пятнистость. Пишите, научу плохому https://dariknews.bg/novini/bylgariia/sled-signal-za-radiaciia-speshna-proverka-v-malinova-dolina-ima-li-opasnost-za-horata-2453597
😨3👍1
Сообщение для жителей Перми. Пермь сейчас находится примерно на границе циклона и антициклона. Вполне возможно, что в целом могут быть антициклонные проявления. Это означает, что атмосферные загрязнения "закачиваются" в нижнюю часть приземного слоя. Поэтому атмосферные загрязнения могут увеличивать свою концентрацию в нижней части приземного слоя. Не пренебрегайте любыми примитивными средствами защиты респираторного …
👍6
Atom.Today ☢️ pinned a photo
Выпадения чернобыльского цезия-137 из стратосферы заметно снизили свою интенсивность примерно к 1999 году, через 13 лет после аварии. Процесс продолжается. График взят из годового отчёта НПО Тайфун за 2019 год #чернобыльскаяавария
😭5👍3
Showing the 12 most recent of 20 posts we hold for @atomtoday. 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 — 252,171 of 1,350,102entries 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.
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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Atom.Today ☢️” (@atomtoday), 672 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/atomtoday.
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.