Telegram RegisterThe public register of Telegram
Telegram profile photo for ESCROW BY VEO²

Channel

ESCROW BY VEO²

@ECVEO

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

497subscribers

-2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002194391143
TypeChannel
Username@ECVEO
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live30 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 30 August 2026
On Telegramt.me/ECVEO

Growth

497500498.57 August 2026 — 499 subscribers8 August 2026 — 499 subscribers16 August 2026 — 500 subscribers23 August 2026 — 497 subscribers7 August 202623 August 2026
4 measurements spanning 15 days, net -2. 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 497–500 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 07:47497-3
16 Aug 2026, 08:04500+1
8 Aug 2026, 04:19499no change
7 Aug 2026, 23:03499first reading

Engagement

20 posts held, back to 29 September 2025the 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.

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 23 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

159 reactions across 15 posts, in 16 distinct kinds. The most used accounts for 15.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2415.1%
custom 60890287582058974412314.5%
💯1610.1%
custom 5253912581277498041159.43%
👍159.43%
👎116.92%
custom 541379446115297828295.66%
👏95.66%
custom 525578547907633071785.03%
custom 535270833959784443185.03%
custom 535299930215731302763.77%
custom 537100787669113846053.14%
custom 608914010523304431053.14%
custom 608673080896861478021.26%
👌21.26%
custom 608910460732834228810.629%

Custom emoji. 10 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 15 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 159reactions 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 29 September 2025 to 23 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

23 Jul 2026, 03:41 UTC234 views5 reactionsread 8 August 2026

We hit 1k! Congratulations to all of us; it's a big amount for the first Ethiopian escrow group. Thanks to all of you guys, especially our admins. We have to thank them, as well as the members who make deals in our groups. We will have giveaways soon, and we'll reach 2k soon.

5

16 Jul 2026, 12:56 UTC368 views6 reactionsread 8 August 2026

Deal Limit Exception If a deal exceeds an admin's assigned limit, the admin may handle a deal worth up to 3× their assigned limit only if both the buyer and the seller explicitly agree before the deal begins. By proceeding, both parties acknowledge and accept the additional risk involved

💯4👏2

12 Jul 2026, 08:26 UTC484 views5 reactionsread 8 August 2026

🆕 Updated Escrow Fee From now on, the following Escrow Fees will apply: ☑️ $1 – $9: No Escrow Fee ☑️ $10 – $29.99: $0.05 Escrow Fee ☑️ $30 and Above: $0.10 Escrow Fee 💡 Note: The escrow fee is charged because our admins invest their time to provide safe and smooth transactions. ⚠️ Escrow fees are non-refundable. — Escrow By Veo (@ecveo)

👍41

11 Jul 2026, 15:58 UTC488 views1 reactionsread 8 August 2026

🎉 3 Million Birr Milestone! We've now handled 3,000,000+ ETB in escrow transactions, including over 15,000 USDT and 233,000+ ETB, across 835+ successful deals. 🤝 Even more exciting—we processed 1,000,000+ ETB worth of deals in less than a month, showing how fast our community is growing. 📈 A big thank you to everyone who trusts Escrow By Veo. Special thanks to @a_d_w_a, @brenworld , @kefafi3, and @mehmetciktopup f

1

21 Jun 2026, 08:44 UTC557 views9 reactionsread 8 August 2026

✨ A Remarkable Milestone for Our Escrow Community! 🎉 We are proud to announce that our community has successfully facilitated 2.08+ million ETB in deals, valued at over $11,200+ 💵. This achievement represents our continued contribution to creating safer and more trusted transactions, helping members complete deals with greater confidence and reducing the risks associated with online exchanges. 🤝 A heartfelt thank

9

26 May 2026, 20:29 UTC584 views6 reactionsread 8 August 2026

عيد مبارك 🌙✨ تقبل الله منا ومنكم صالح الأعمال، وكل عام وأنتم بخير �

3👌2👍1

21 Apr 2026, 14:21 UTC741 views5 reactionsread 8 August 2026

📊 Dva Bot Status Bot Status: 🟢 ONLINE ✅ Completed Deals: 448 💰 ETB: 97 deals, 151526.99 💰 USD: 351 deals, 4627.11 ⏱️ Active Deals: 1 ⏳ USD: 1 deals, 3.50 📋 Active Deal IDs: - #VEO569 👮 Admin Statistics: 👤 @speed_prime (11 deals): 💰 ETB: 455.50 💰 USD: 79.99 👤 @a_d_w_a (163 deals): 💰 ETB: 81336.30 💰 USD: 1632.86 👤 @macron_topup (47 deals): 💰 ETB: 7150.00 💰 USD: 478.50 👤 @brenworld (7

5

14 Feb 2026, 19:13 UTC≈1,230 viewsread 8 August 2026

Hello dear users! 👋 We’ve updated our DVA bot @dvahelperbot with new features! ✨ Use /start to explore the new features and see what’s new. 💡 Check out all useful commands in the Command Center to get the most out of the bot. 🚀

7 Jan 2026, 04:04 UTC≈2,260 views4 reactionsread 8 August 2026

​🎄 Merry Christmas to the ECVEO Family! 🎄 ​እንኳን ለጌታችን ለመድኀኒታችን ለኢየሱስ ክርስቶስ የልደት በዓል በሰላም አደረሳችሁ። ይህ በዓል የሰላምና የፍቅር እንዲሆንላችሁ ECVEO ይመኛል። ​መልካም በዓል! ✨

👍4

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

Citation-graph rank — 1,026,940 of 1,627,068entries 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.

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

“ESCROW BY VEO²” (@ECVEO), 497 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/ECVEO.

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.