Telegram RegisterThe public register of Telegram
Telegram profile photo for Suba Software Solutions

Channel

Suba Software Solutions

@Suba_Software

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

103subscribers

+28 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003985644252
TypeChannel
Username@Suba_Software
Created4 May 2026measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live2 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/Suba_Software

Growth

751038911 August 2026 — 75 subscribers11 August 2026 — 75 subscribers18 August 2026 — 89 subscribers25 August 2026 — 96 subscribers2 September 2026 — 103 subscribers11 August 20262 September 2026
5 measurements spanning 22 days, net +28. 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 71–107 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 05:18103+7
25 Aug 2026, 08:2596+7
18 Aug 2026, 06:0289+14
11 Aug 2026, 17:4575no change
11 Aug 2026, 02:4675first reading

Engagement

19 posts held, back to 4 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 19 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

37 reactions across 10 posts, in 7 distinct kinds. The most used accounts for 56.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2156.8%
👏616.2%
410.8%
🎉25.41%
👍25.41%
12.70%
🥰12.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 37 reactions 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.

Recent posts

29 Jul 2026, 11:05 UTC471 views8 reactionsread 11 August 2026
Photo

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

🔥71

20 Jul 2026, 14:04 UTC524 views3 reactionsread 11 August 2026
Photo

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

20 Jul 2026, 13:17 UTC293 views5 reactionsread 11 August 2026
Forwarded from @scholarxivPhoto

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

1 Jul 2026, 13:24 UTC360 views1 reactionsread 11 August 2026
Photo

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

4 Jun 2026, 08:02 UTC297 views4 reactionsread 11 August 2026
Photo

🎁 We came bearing gifts. They let us in. That's all we can say for now. 👀 More details soon. www.subasoftware.com

👏4

4 Jun 2026, 08:01 UTC270 views2 reactionsread 11 August 2026
Photo

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

3 Jun 2026, 09:20 UTC411 views4 reactionsread 11 August 2026
Photo

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/

🔥211

3 Jun 2026, 08:42 UTC385 viewsread 11 August 2026
Photo

🎉 CBE bank verification is back up!! verify any CBE and CBE birr transactions using Verify.ET https://verify.et/verify/cbe

30 May 2026, 12:29 UTC374 viewsread 11 August 2026
Photo

🚀 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

29 May 2026, 11:54 UTC194 views1 reactionsread 11 August 2026
Photo

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

28 May 2026, 12:03 UTC268 views5 reactionsread 11 August 2026
Photo

🚀 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 🇪🇹

🔥32

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.

Forward network

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.

Mentions

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.

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

“Suba Software Solutions” (@Suba_Software), 103 subscribers as measured 2 September 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.