нарешті виписав
❤1

Channel
@IlFATOO
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
99subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002960456302 |
|---|---|
| Type | Channel |
| Username | @IlFATOO |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 30 August 2026 |
| On Telegram | t.me/IlFATOO |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 08:26 | 99 | +1 |
| 9 Aug 2026, 11:31 | 98 | no change |
| 7 Aug 2026, 19:38 | 98 | first reading |
7 posts held, back to 7 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 1 page 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. It is computed over the 1 of 7 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 7 (7 August 2026 – 8 August 2026) |
| Views total | 153 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 11:31 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 1 of the 7 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 7 August 2026 to 8 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.
нарешті виписав
❤1
05.08.2026-07.08.2026 CAD/USD TAKE (+2.5R) Глобально з місяця закрились шортами , під нами М FVG , відповідно він і є цілю з тижня роботу з зоною FVG після FF якого дали шорти дальше з денки я планував набратись ліміткою зі стопом за FF W FVG (фото6) але трохи не дійшли тому шукав модель локальніше з локальнішим стопом Після з 1,4H дали EQ H в D FVG( на якихось провайдерах був рейд на якихось не було, тому набира…
03.08.2026-04.08.2026 CAD/USD TAKE (+2R) З денки дали рейд після почали формувати поток приказів (ОФ) цілю виступав D FVG Локально НЮ рейдить Лой ЛО + лой Франфурта після формує модель інвертуючи 15м фта і формуєчи 15м на лонги Щодо помилок - вхід раніше інвалідації відповідно був вищий ризик получити ресвіп
28.07.2026 GBP/USD STOP (-1R) шорт контекст ЛО рейдить AH + дає FF 4H + формує модель 5,15m FVG стоп варіативний, просто отримав ресвіп
22.07.2026 EUR/USD STOP (-1R) Контекст Глобально даєм реакцію від W FVG формуючи за собою ОФ. Більш локально, з 4H формуєм FVG - у Франк получаєм його FF, після в ЛО ресвіп та модель 5m bos+5m fvg. (рейд AH не рахую тому що Азія була висхідна і закріпились ми над нею) Ціль просто виставив фікс 2.5р FTA - не було Щодо помилок можливою проблемою є сам факт висхідної азії + конфірм франка закріпленням над нею. …
21.07.2026 GER40/USD STOP (-1R) HTF: Лонговий ОФ приводить ціну до агресивного рейду АТХ , реакція інвертовує(фото(1) розрив такою ж агресією , після тесту цієї інверсії знову реакція яка інвертовує ще одну зону (фото(2) враховуючи ці всі фактори агресії шортів, інвертування всіх POI, наступною цілю виступав відкритий W фрактал Відповідно локально я шукав можливість продовжити шорти, перейшовши на 4H бачимо хорошу…
15.07.2026 EUR/USD TAKE (+2R) Глобально картина така: Дійшли та зняли границю ренжа, який формується вже близько року. Відповідно, хотілося б побачити лонгову реакцію, тим паче зверху була ціль у вигляді W FVG. Більш локально, з D ми отримуємо цю реакцію та формуємо підтверджуючі фактори - ОФ + інвалідація D FVG. Тобто отримуємо підтвердження, що реакція справді є. Відповідно, після цього шукаю точку входу. На 4…
Showing the 7 most recent of 7 posts we hold for @IlFATOO. 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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“marklldy.fx” (@IlFATOO), 99 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/IlFATOO.
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.