Posted without readable text

Channel
Дайджесты VIP/VIP+
@fatwallet3
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
256subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001488039423 |
|---|---|
| Type | Channel |
| Username | @fatwallet3 |
| Description | Бот для покупки: @fwpack_bot Контакт со мной: @makintosh_k Паблик сервиса: @fatwallet1 |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/fatwallet3 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 02:02 | 256 | no change |
| 7 Aug 2026, 01:35 | 256 | first reading |
Engagement
20 posts held, back to 19 July 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 · 30 days
- 13.2%
- avg views ÷ 256 subscribers
- Avg views / post
- 33.8
- 13 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 13
- of 20 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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (19 July 2026 – 6 August 2026) |
| Views total | 439 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 02:02 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
- ≈239
- Videos
- ≈14
- Links
- ≈28,000
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. 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.
Recent posts
Posted without readable text
Posted without readable text
Posted without readable text
Posted without readable text
Posted without readable text
Posted without readable text
Posted without readable text
FATWALLET за 29 июля 🚀 Криптовалюта Зафиксировал торговую активность по основным парам. — BTCUSDT: зафиксировал 3 профитных сделки и 1 микростоп источник — DRAM: исполнил второй тейк-профит источник — JUP: закрыл позицию перед выходом макроэкономических данных источник — BTCUSDT: выставил лимитный ордер на покупку по 63980 источник Записал статистику торговой сессии. ⚖️ Арбитражные ситуации Отработал межбиржевые от…
📈 Криптовалюта Торговый деск зафиксировал серию скальп-сделок по BTC и закрытие позиций по альткоинам. — BTCUSDT: закрыли первую сделку по тейку линк — BTCUSDT: провели ручную фиксацию второй сделки линк — BTCUSDT: завершили третий скальп линк — Олег: +37%, закрыли шорт линк — ETHUSDT: −1%, сработал стоп-лосс линк — Ильяс: стоп по фьючерсам, спот удерживаем линк — Volatile Asset: открыли лоу-риск лонг линк — #SNDK: у…
FATWALLET за 27 июля 💰 Криптовалютный деск Рынок исполняет тейки по альткоинам на фоне локальной волатильности. — EULUSDT.P: профит, трейдер закрыл все цели. — BTCUSDT: +2.1%, цена удержалась выше уровня 65.5k. — BTC: -1.0%, трейдер удерживает шорт после слома структуры. — ESPUSDT: лимитка 0.09544, деск выставил отложенный лонг. — BUSDT: лимитка 0.1758, деск выставил отложенный шорт. — LTCUSDT: -0.92%, котировки упа…
FATWALLET за 25–26 июля 📈 Криптовалюта Деск фиксирует результаты и сопровождает открытые сделки. — GWEIUSDT.P: цена достигла цели, закрыта Источник — BANKUSDT.P: средний вход составил 0.23$, в работе Источник — EULUSDT.P: плечо 20x при марже 1%, в работе Источник Риск-параметры соответствуют установленному регламенту. 🛢 Фонда/Форекс Деск удерживает позицию по энергетическому сектору. — BRENT: трейдер набрал 1/4 час…
Showing the 12 most recent of 20 posts we hold for @fatwallet3. 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 — 856,708 of 1,585,237entries 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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“Дайджесты VIP/VIP+” (@fatwallet3), 256 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/fatwallet3.
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.