Channel
@Suba_Software
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
75subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003985644252 |
|---|---|
| Type | Channel |
| Username | @Suba_Software |
| Created | 4 May 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/Suba_Software |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 17:45 | 75 | no change |
| 11 Aug 2026, 02:46 | 75 | first reading |
19 posts held, back to 4 May 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 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 29 July 2026 |
|---|---|
| Posts held | 19 (4 May 2026 – 29 July 2026) |
| Views total | 1,288 |
| Reactions total | 16 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 02:46 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.
37 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 56.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 21 | 56.8% | |
| 👏 | 6 | 16.2% | |
| ❤ | 4 | 10.8% | |
| 🎉 | 2 | 5.41% | |
| 👍 | 2 | 5.41% | |
| ⚡ | 1 | 2.70% | |
| 🥰 | 1 | 2.70% |
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 10 of the 19 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 37reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 4 May 2026 to 29 July 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.
Verify ET App Update! we just revamped and improved the Verify App with alot of great features our customers have been asking for. main part of the revamp focus was Fraud Detection and clearly communicating that to our users with visual cues and easy to understand UX. can't wait for you all to try it. let us know what we should impove. https://verify.et/app
🔥7❤1
Verify.ET X @ScholarXIV Announcing partnership with ScholarXIV, first of its kind research tool as its offical payment verification platform We believe in collaboration and partnership to grow and build together. so we are announcing our partnership to work and collaborate with the team at ScholarXIV to strengthen both of our tech and products, with first part of it being verify.et being an official verification p…
🔥3
ScholarXIV has partnered up with Verify.ET (@Suba_Software) as our official payment verification system for all local payments. We've been using Verify.et for a while now and we've found it to be the most suitable payment verification platform for our product, complete with their extensive dashboard and unified API it makes managing and tracking payments a breeze. On their side they're going to be using our researc…
🎉2👏2🔥1
SEO expertise in action. For the past two months, Passport.et has consistently ranked #1 on Google above the official government website for 60–75% of the time, and #2 for the remainder. For keywords related to passport and passport status in Ethiopia. That visibility has translated into real results: 25,000+ monthly users and growing. This didn't happen by chance. It's the result of continuous SEO optimization, …
👍1
🎁 We came bearing gifts. They let us in. That's all we can say for now. 👀 More details soon. www.subasoftware.com
👏4
we have officially hit 20k+ users per MONTH!! I started this project almost 2 years ago, it was just so I could learn new tech (using Inertia with Laravel and deploying one VPS), now with a lot of work and with collaboration with my co founder, it is actually useful to people. crazy! www.passport.et
🔥2
also, Dashen is up!!! there are some people at these big corporations that make you confident that things can actually get done in this country. so helpful and Ethiopian hospitality. https://verify.et/
🔥2⚡1❤1
🎉 CBE bank verification is back up!! verify any CBE and CBE birr transactions using Verify.ET https://verify.et/verify/cbe
🚀 Shipped in 48 hours from customer request → production. New on Verify.ET: Settlement Account Matching. Now you can verify: ✅ The transaction is real ✅ The money was sent to your registered account More control for developers. More confidence for businesses. or can be extended by passing one 'settlementAccount' to check on, otherwise the default behaviour is it auto checks your account list. read about it here …
Today was doing client branding work and where we print there are alot of shops(around Edna Mall) and was doing footwork for Verify ET, introduced 6 shops about the app while we were printing. One owner told me,with telebirr fake screenshot his friend lost 65k last Thursday. the dude that scammed him, sent like 7 different people with different orders, and he was sending screen shots on telegram. https://verify.et/
👍1
🚀 Verify.ET Agent Skill is here npx skills add NegusNati/verify-et-api Let your AI agent integrate Verify.ET and ship to production automatically. No docs. No manual setup. Just add your API key in your .env and let the agent handle the rest. Works with Codex, Claude Code, Cursor, Gemini, OpenClaw, Hermes, and any Agent Skills compatible agent. Open source • Production ready 🇪🇹
🔥3❤2
We are officially live. www.Verify.et
Showing the 12 most recent of 19 posts we hold for @Suba_Software. 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 — 394,518 of 1,169,250entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Suba Software Solutions” (@Suba_Software), 75 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Suba_Software.
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.