Channel
@tesfa_ai
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
203subscribers
+0 since we began measuring on 14 September 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003281368221 |
|---|---|
| Type | Channel |
| Username | @tesfa_ai |
| Description | Welcome to Tesfa.AI! This channel will be used to share updates, announcements, and upcoming activities. You’ll also find access to our courses and community spaces. This is the main channel to stay connected with Tesfa AI. 🔗 https://linktr.ee/Tesfa_Ai |
| Created | Between 1 October 2025 and 28 February 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 September 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/tesfa_ai |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 15:22 | 203 | no change |
| 14 Sept 2026, 14:47 | 203 | first reading |
20 posts held, back to 8 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 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 15 June 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 14 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
21 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 38.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 38.1% | |
| 🔥 | 8 | 38.1% | |
| 👍 | 5 | 23.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 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 21 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 8 May 2026 to 15 June 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.
Let’s simplify how an AI agent app works 👇 A basic agent flow looks like this: User → App → Agent → Model → Tools → Response The user asks for something. The app receives the request. The agent decides what needs to happen. The model reasons through the task. The tools help it take action, search, calculate, fetch data, or complete steps. Then the response goes back to the user. This is the basic idea behind many A…
❤3
This Saturday, June 13, Ethio-Claw Meetup continues 🚀 This session is focused on GTM: Go-To-Market strategy, positioning, and growth. We’ll be joined by Monalisa Haile, Founder & Fractional CMO at Pivotedge Consulting, who will share practical insights on how startups can think about market entry, trust, traction, storytelling, and growth. Building the product is one part of the journey. Knowing how to position it, …
Quick challenge for every builder this week 🚀 Some of you have already started posting your projects and sharing your progress publicly, and we love seeing it. Keep going. For those who have been quiet this week, this is your sign to start. This week, we do not want only written updates. We want to see your face, your screen, your progress, and your ideas in motion. Record a short video explaining what you are buil…
🔥3❤1👍1
Saturday was a different kind of experience for our startup community. Our startup community got the chance to sit with experienced business leaders, operators, communication experts, and marketing professionals who shared real lessons from building and scaling businesses. The goal was exposure. Because building a startup is not only about code or ideas. Founders also need business understanding, communication, ma…
❤3
Tomorrow we’re back for another Ethio-Claw coding meetup 🚀 We’ll continue building, discussing ideas, working with AI agents, and helping each other move projects forward. This is not a class where you just sit and listen. It’s a space to build, ask questions, test ideas, code with others, and start thinking about how your project can become something real. The session starts tomorrow, June 5, at 10:00 AM. Bring…
We officially dropped our first Tesfa AI demo 🚀 We’ve been working on this product for the past few months, and we’re genuinely excited to finally start showing it to the world. This is only the beginning, but it’s a big step for us. Go check out the demo on our LinkedIn page, like it, comment your thoughts, and show some support: https://www.linkedin.com/company/tesfa-ai We also want to hear your voice about the …
👍2
We just want to take a moment to say this: We are genuinely proud of the builders who have already started sharing their startup journeys publicly. From AI medical assistants and business operation agents to construction estimation tools, NGO operation systems, interview assistants, and productivity/accountability apps, the ideas coming out of this community are already exciting to see. This is exactly the energy …
🔥2
New week, new focus 🚀 This week, the focus is not only on learning new ideas. It is about building, testing, showing progress, and starting to think more like founders. We want people to move from simply understanding the concept to asking, “How can I build something useful with this?” So as we continue, pay attention to what is being built, ask better questions, test your ideas, and start thinking about how your …
👍1
Tomorrow we’re back for another coding meetup 🚀 We’ll continue from where we left off, work through ideas, discuss AI agents, and spend time building together. If you’ve been experimenting, working on a project, or just starting to think about what you can create with these systems, come through. This is not just about listening. It’s about showing up, asking questions, testing ideas, and building with others. The s…
We’re back again this Saturday 👀 Another session. More building. More questions. More ideas turning into something real. Every week, we’re seeing people move from just learning about AI agents to actually thinking about what they can create with them, for their projects, workflows, startups, and daily work. That’s the part we’re most excited about. So if you’ve been coming, don’t miss this one. If you haven’t joine…
🔥1
Last Saturdays sessions had a lot of good moments. Now we want to hear from you 👀 What was the most interesting thing you learned? Was it something about AI agents, OpenClaw, building workflows, or just the way you started thinking about what you can create? Drop your answer here. We want to know what actually stayed with you after the session. #TesfaAI #AIEngineering #TechEducation #LearnAI
We’re starting to share more of what we’ve been building 👀 The sessions, the ideas, the experiments, the projects, the builder moments, and the bigger vision behind Tesfa AI are going public across our platforms. You can now find us here: X: @Tesfa_Ai LinkedIn: https://www.linkedin.com/company/tesfa-ai Instagram: tesfa.ai TikTok: https://www.tiktok.com/@natnael_debel YouTube: https://www.youtube.com/@Tesfa_Ai Go …
Showing the 12 most recent of 20 posts we hold for @tesfa_ai. 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.
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Tesfa AI” (@tesfa_ai), 203 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/tesfa_ai.
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.