4 measurements spanning 21 days, net -1. 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 205–207 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
28 Aug 2026, 15:38
205
-2
22 Aug 2026, 07:17
207
+1
8 Aug 2026, 11:16
206
no change
8 Aug 2026, 00:02
206
first reading
Engagement
13 posts held, back to 17 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 1 pageof Telegram’s post history, 20 posts per page.
ERR · 30 days
26.3%
avg views ÷ 205 subscribers
Avg views / post
54.0
2 posts measured
Reaction rate
18.2%
reactions ÷ views · ER floor
Posts in window
2
of 13 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. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 7 August 2026
Posts held
13 (17 June 2026 – 7 August 2026)
Views total
108
Reactions total
12
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
8 Aug 2026, 11:16 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.
Reaction mix
115 reactions across 11 posts, in 3 distinct kinds. The most used accounts for 48.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
56
48.7%
👏
42
36.5%
👍
17
14.8%
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 11 of the 13 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 115reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 17 June 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.
AI can play a role across almost every part of payment operations — but where can it actually make the biggest difference? If you had to prioritize just one, what would you choose? Vote below 👇
Fraud Detection50%
Smart Payment Routing10%
Reconciliation & Back Office40%
Customer Support60%
The shares total 160%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Data tells the story. 📊
Between April and June, Unipesa processed 38.9 million successful transactions across our leading African markets, with Kenya, DR Congo, and Ivory Coast recording the highest transaction volumes.
The snapshot above highlights our top markets and average conversion rates during the reporting period.
Behind every number is infrastructure working exactly as it should!
As our network grows, we…
Kenya has long been a leader in digital payments — but what's next?
As the market evolves, the biggest opportunities are no longer in new payment methods, but in the infrastructure that connects them.
In our latest blog, we explore the trends shaping Kenya's digital payment ecosystem — and what businesses should be paying attention to next.
📖 Read the full article below.
Last week, our Co-Founder & Chief Product Officer, Pavel Laptev, and Arkon Elizarov, Head of Product at POS Platform, joined industry leaders at the MSME Finance Fair 2026 in Lusaka. 🇿🇲
The fair brought together businesses, partners, and innovators working to expand access to financial services for SMEs across Zambia.
For our team, it was a chance to showcase our POS solution to SME owners directly — and the respon…
We've reached 4,000 followers on LinkedIn! 🎉
A huge thank you to everyone who's joined our journey. Whether you've been with us from the beginning or only recently discovered Unipesa, we truly appreciate your support.
We're looking forward to sharing more insights, stories, and ideas about the future of payments across Africa — and to continuing the conversation with all of you.
Thank you for being part of our com…
A payment takes just a few seconds.
But what actually happens between the moment someone taps "Pay" and the moment a merchant receives confirmation?
In our latest article, we follow the journey of a single payment in Lagos and unpack the invisible layers working behind the scenes — from authentication and routing to fraud checks, settlement, and reconciliation.
It's a reminder that every successful transaction rel…
This week, we’re continuing our Expert Insight series with a conversation featuring Evgeny Protopopov, CTO at Unipesa.
We spoke about one of the biggest questions in fintech today: where can AI genuinely improve payment operations, and where should human expertise remain in control?
A big thank you to Evgeny for sharing his thoughts and practical perspective.
Read the full Q&A below 👇
What does it take to build trust in Africa's gaming industry?
As the sector continues to grow, trust is becoming just as important as technology, payments, and regulation.
In our latest expert contribution, Omotayo Okewunmi ANIPR, Chief Operations Officer at Saldrey Communications Limited and Director at AfriplayHub, shares her perspective on why responsible communication, transparent infrastructure, and accountabi…
Every payments team has that one metric they check first. If you had to choose just one, which payment metric would it be? Vote in the poll below 👇
Transaction Success Rate75%
Processing Speed42%
Cost per Transaction17%
Payout Reliability25%
The shares total 159%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
A few weeks after GTSA 2026, we're still reflecting on many of the conversations that took place in Nairobi.
One thing remains clear: the future of African gaming will be built on strong infrastructure, collaboration, and localized payment experiences.
We're proud to have supported the event as an official partner and to have our perspective featured by Business Insider.
📖 Read the article here 👈
Our Co-Founder & Chief Product Officer, Pavel Laptev, recently attended iFX EXPO International 2026 in Cyprus, joining industry leaders from across fintech, payments, trading, and liquidity.
Beyond the meetings and networking, the event was a good reminder of how closely connected today's financial ecosystems have become — and how important infrastructure remains when businesses expand into new markets.
Pavel's tak…
❤7👏6
Showing the 12 most recent of 13 posts we hold for @unipesa. 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.
Polls
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
AI can play a role across almost every part of payment operations — but where can it actually make the biggest difference? If you had to prioritize just one, what would you choose? Vote below 👇
Fraud Detection50%
Smart Payment Routing10%
Reconciliation & Back Office40%
Customer Support60%
The shares total 160%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Every payments team has that one metric they check first. If you had to choose just one, which payment metric would it be? Vote in the poll below 👇
Transaction Success Rate75%
Processing Speed42%
Cost per Transaction17%
Payout Reliability25%
The shares total 159%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 13 most recent posts we hold, published 17 June 2026 to 7 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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 28 August 2026 — this
entry's latest reading, not the date you are reading this.
“Unipesa” (@unipesa), 205 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/unipesa.
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.
