Channel
@breathofwind1
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,036subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001852732373 |
|---|---|
| Type | Channel |
| Username | @breathofwind1 |
| Created | 27 February 2023 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/breathofwind1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 05:17 | 3,036 | +2 |
| 10 Aug 2026, 15:03 | 3,034 | +1 |
| 7 Aug 2026, 15:58 | 3,033 | no change |
| 7 Aug 2026, 15:17 | 3,033 | first reading |
19 posts held, back to 21 June 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 2 pagesof 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 3 August 2026 |
|---|---|
| Posts held | 19 (21 June 2026 – 3 August 2026) |
| Views total | 9,519 |
| Reactions total | 835 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 00:10 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.
Measured directly from 3 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.
2,443 reactions across 19 posts, in 2 distinct kinds. The most used accounts for 53.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5463391966098109689 | 1,316 | 53.9% | |
| 🕊 | 1,127 | 46.1% |
Custom emoji. One row above is a 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 count beside it isTelegram’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 19 of the 19 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 2,443reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 21 June 2026 to 3 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.
Вчера прошло наше чтение в женском кругу 🫂 Очень радостно видеть девочек, которые искренне хотят изучить свою веру, приходят в новый для себя круг, задают вопросы, преодолевая стеснение, это очень ценно, ведь их присутствие здесь — уже шаг на пути познания Бога🤍 Слава Господу нашему Иисусу Христу!
🕊66
Дорогие девушки, давно мы с вами не собирались на чтения 📚 В это воскресенье вместе с сестрами во Христе проведем чтение и разберем тему «Характер Христа: каким Он был?» Дата: 02.08 Время: 13:30 Локация: Москва, Антикафе Jamanc🤍 Для уточнения деталей, пишите🫂 @tateviikkk
🕊56
Самый явный признак высокого эмоционального интеллекта — практически полное отсутствие осуждения. Нам нужно научиться искать десятки возможных причин чужого поступка. Понимать, что за одним и тем же поведением могут стоять страх, усталость, травма, воспитание, обстоятельства или просто плохой день. ибо каким судом судите, таким будете судимы; и какою мерою мерите, такою и вам будут мерить (от Матфея 7:2)🕯️
🕊105
Не празднуй грехом то, что получил благодаря молитве
🕊121
Чтобы любовь возрастала, нужно ее отдавать. Человек, который не отдает даже ту немногую любовь, что у него есть, словно держит в руке горсть семян и не хочет их посеять.
🕊110
если на их зло я отвечу злом, тогда в чем разница между нами?
🕊107
ибо семь раз упадет праведник, и встанет; а нечестивые впадут в погибель. Притчи 24:16 🕊️ снова и снова бегите к Господу
custom 546339196609810968989🕊52
Если ты хочешь помочь Церкви, то первоначально старайся лучше исправить себя самого, а не других. Если ты исправишь самого себя, то сразу же исправится частичка Церкви.
custom 546339196609810968981🕊48
Господь – твердыня моя и прибежище мое, Избавитель мой, Бог мой, – скала моя; на Него я уповаю; щит мой, рог спасения моего и убежище мое. Псалтирь 17:3
custom 5463391966098109689108🕊39
Ты знал, что Я – Творец, но Мне не покорился Ты знал, что Я есть Свет, но ты Меня не зрил Ты знал, что Я есть Путь, но ты с дороги сбился. Ты знал, что Я есть Жизнь, но Мною ты не жил. Ты знал, что Мудрость Я – не чтил Моих законов Ты знал, что Я всеблаг, но не любил Меня Ты знал, что Я богат, но не просил с поклоном Ты знал, что вечен Я, но не искал ни дня. Я милостив – ты знал, но Мне судьбу не вверил Ты знал, что…
custom 546339196609810968975🕊42
Не живи будущим, которого нет. Живи сегодня. В этом дне — твоя встреча с Богом. Завтра Он тоже будет с тобой! Главное и ты будь с Ним.
custom 5463391966098109689133🕊39
Video message, posted without a caption
custom 546339196609810968991🕊29
Showing the 12 most recent of 19 posts we hold for @breathofwind1. 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 — 122,202 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.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“breath of wind ♱” (@breathofwind1), 3,036 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/breathofwind1.
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.