делаю для себя цели на возможно самый сложный и в то же время самый интересный год в своей жизни, набираюсь сил и начинаю страшно гриндить хочу чтобы 2026 стал самым продуктивным для меня годом и всем желаю того же!

Channel
saint
@saintAcrypto
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
136subscribers
-14 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 | -1002473989091 |
|---|---|
| Type | Channel |
| Username | @saintAcrypto |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/saintAcrypto |
Topic
Personal blog — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 25 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 15:19 | 136 | -2 |
| 27 Sept 2026, 11:56 | 138 | -4 |
| 13 Sept 2026, 14:18 | 142 | -2 |
| 5 Sept 2026, 07:54 | 144 | -3 |
| 21 Aug 2026, 07:47 | 147 | -1 |
| 14 Aug 2026, 16:14 | 148 | -2 |
| 8 Aug 2026, 20:01 | 150 | no change |
| 7 Aug 2026, 17:53 | 150 | first reading |
Engagement
20 posts held, back to 10 December 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 1 January 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
15 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 46.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 7 | 46.7% | |
| 🍾 | 3 | 20.0% | |
| 👌 | 2 | 13.3% | |
| 👍 | 2 | 13.3% | |
| 🐳 | 1 | 6.67% |
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 6 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 15 reactions 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 10 December 2025 to 1 January 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.
Recent posts
с наступающим кстати всех!! а кого то уже с наступившим
🍾3🐳1
с броколи 800$ нафлипал, но оурбит накинул рк(( если есть эксперты по оурбиту напишите в лс пжж
фул вышел вкусненько
можно в долгую посидеть (пару дней) и подождать пока в стакан полетят остальные токены с тс но мм хитрый и подбрить за это время может
50% срезал
стоп в бу на случай выбривки откинул
пошла возня по найту я уже фул позу добрал, твх вышла 0.09 сама раздача вроде в 12:00
👌2
выскочил в бу в итоге, чето нету желания больше держать тк долго ровняют
залился в спред VOOI гейт/бингх + можно оурбит, он выше на данный момент гейт 0.062 бинг 0.08 оурбит 0.095 но на бинге фандос -3% может подъебать
кто-то может сделать миррор на базу арсена маркаряна?
🤣5
За последнюю неделю въебал неприятную сумму на лудке, поэтому снижаю количество таких фастфлипов до минимума и буду искать только жб-около жб сделки вижу кстати тренчи потихоньку оживают поэтому в планах депнуть на аксиому и пробовать по немногу флипать солана щитки
Showing the 12 most recent of 20 posts we hold for @saintAcrypto. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“saint” (@saintAcrypto), 136 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/saintAcrypto.
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.