Telegram RegisterThe public register of Telegram
Telegram profile photo for Afina

Channel

Afina

@afina_io

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

1,398subscribers

+43 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002176730413
TypeChannel
Username@afina_io
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/afina_io

Growth

1,3551,3981,376.57 August 2026 — 1,355 subscribers7 August 2026 — 1,355 subscribers8 August 2026 — 1,356 subscribers11 August 2026 — 1,357 subscribers14 August 2026 — 1,378 subscribers18 August 2026 — 1,381 subscribers21 August 2026 — 1,397 subscribers24 August 2026 — 1,396 subscribers27 August 2026 — 1,394 subscribers29 August 2026 — 1,396 subscribers2 September 2026 — 1,394 subscribers6 September 2026 — 1,398 subscribers7 August 20266 September 2026
12 measurements spanning 29 days, net +43. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,349–1,404 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 00:361,398+4
2 Sept 2026, 04:131,394-2
29 Aug 2026, 21:451,396+2
27 Aug 2026, 07:181,394-2
24 Aug 2026, 14:431,396-1
21 Aug 2026, 02:071,397+16
18 Aug 2026, 05:121,381+3
14 Aug 2026, 22:061,378+21
11 Aug 2026, 18:181,357+1
8 Aug 2026, 08:051,356+1
7 Aug 2026, 22:201,355no change
7 Aug 2026, 14:001,355first reading

Engagement

20 posts held, back to 26 May 2026the 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

32 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 43.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🐳1443.8%
🕊1031.3%
🦄515.6%
🍓39.38%

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 14 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 32 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 26 May 2026 to 7 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.

Recent posts

7 Aug 2026, 11:50 UTC131 views3 reactionsread 7 August 2026
Photo

❗️ Worked in Indigo? Move to Afina on special terms We know how much time it takes to build a working setup: profiles, accounts, proxies, cookies, team workflows and automation That’s why we prepared a special offer for Indigo users to help them move to Afina without extra losses or a long restart 🎁 What Indigo users get: 🔜 Compensation for unused days, up to 90 days 🔜 20% off Base and Standard plans 🔜 30% off th

🍓1🕊1🦄1

6 Aug 2026, 09:29 UTC207 views1 reactionsread 7 August 2026
Photo

🎁 AFINA2BDAY: Afina is turning 2! For 2 days only, get a special discount on Base, Standard and Max plans Only 50 promo codes are available, so grab yours while they are still here The code can be used once, so choosing a longer subscription period gives you the best value 👉 Promo code: AFINA2BDAY Renew your plan or buy a new one on the official website https://my.afina.io/

🐳1

5 Aug 2026, 14:20 UTC270 views2 reactionsread 7 August 2026
Photo

🎂 Afina birthday special offer Until 07.08.2026, Unlimited plan owners can renew their plan at a special price 💎 Unlimited renewal prices • $252 for 1 year • $499 for 2 years Unlimited is mostly available to our early users, so this is a special bonus for those who have been with Afina for a long time 🔗 How to renew You can renew your plan in your personal account on the website https://my.afina.io/ Or through

🐳1🦄1

30 Jul 2026, 13:45 UTC377 views1 reactionsread 7 August 2026
Photo

❗️ Important notice regarding support for older versions Please migrate to the new version of Afina as soon as possible. ⏳ On August 1st, we will completely stop supporting previous versions. After that, only Afina 2.0.0 and higher will be officially supported and functional. Please do not delay the update to ensure your work remains stable and secure

🐳1

22 Jul 2026, 11:47 UTC499 views1 reactionsread 7 August 2026
Photo

❗️ Important notice regarding support for older versions Please migrate to the new version of Afina as soon as possible. ⏳ On August 1st, we will completely stop supporting previous versions. After that, only Afina 2.0.0 and higher will be officially supported and functional. Please do not delay the update to ensure your work remains stable and secure

🐳1

14 Jul 2026, 13:21 UTC499 views0 reactionsread 7 August 2026
Photo

🤝 Afina 2.0.19 is live This update adds more control over work data, faster login options, better proxy checks, referral analytics and smoother work with large profile bases 🗂 Work data and login • You can now choose the main project folder on the login screen • Profiles, cache and work data can be stored on another drive, including a faster SSD • This helps keep the system drive cleaner and makes it easier to swit

11 Jul 2026, 12:52 UTC440 views3 reactionsread 7 August 2026
Photo

❗️ Important notice regarding support for older versions Please migrate to the new version of Afina as soon as possible. ⏳ On August 1st, we will completely stop supporting previous versions. After that, only Afina 2.0.0 and higher will be officially supported and functional. Please do not delay the update to ensure your work remains stable and secure

🕊3

30 Jun 2026, 09:20 UTC640 viewsread 7 August 2026
Photo

❗️ Important notice regarding support for older versions Please migrate to the new version of Afina as soon as possible. ⏳ On August 1st, we will completely stop supporting previous versions. After that, only Afina 2.0.0 and higher will be officially supported and functional. Please do not delay the update to ensure your work remains stable and secure

29 Jun 2026, 16:39 UTC511 views1 reactionsread 7 August 2026
Photo

🤝 Afina 2.0.18 is live This update improves stability, proxy checks, profile performance and everyday account management 🧩 Accounts and groups • Improved stability when working with account groups • Added account name copying, making large account lists easier to manage ⚙️ Scripts and database • Variables created in scripts now display correctly in the “Database” element 🌐 Proxy • Improved Afina interaction with

🐳1

26 Jun 2026, 12:01 UTC510 viewsread 7 August 2026
Photo

🤝 Afina 2.0.17 is live This update focuses on account filtering, Active Tasks, MCP server improvements and browser optimization for OKX Boost workflows • Improved account filtering The account list now shows only the accounts that match the selected filters • Task groups now display correctly in the “Active Tasks” section • Improved MCP server performance It now handles tasks more accurately and interacts with A

24 Jun 2026, 08:17 UTC480 viewsread 7 August 2026
Photo

❗️ Important notice regarding support for older versions Please migrate to the new version of Afina as soon as possible. ⏳ On August 1st, we will completely stop supporting previous versions. After that, only Afina 2.0.0 and higher will be officially supported and functional. Please do not delay the update to ensure your work remains stable and secure

23 Jun 2026, 16:40 UTC423 views1 reactionsread 7 August 2026
Photo

🔒 Secure sync in Afina We added fast sync for personal and team accounts, but security stays on your side Your accounts, proxies, cookies and fingerprints are encrypted on your device before they are uploaded What this means: • Afina servers only store unreadable encrypted data • Personal synced accounts can be decrypted only by you • Team accounts can be decrypted only by your team members • Keys are never sent to

🐳1

Showing the 12 most recent of 20 posts we hold for @afina_io. 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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.

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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“Afina” (@afina_io), 1,398 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/afina_io.

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.