Channel
@LEBIZUCon
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
527subscribers
-2 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001777074603 |
|---|---|
| Type | Channel |
| Username | @LEBIZUCon |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 27 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 19 September 2026 |
| On Telegram | t.me/LEBIZUCon |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 82% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 08:01 | 527 | -1 |
| 3 Sept 2026, 09:36 | 528 | -1 |
| 27 Aug 2026, 10:05 | 529 | no change |
| 27 Aug 2026, 00:02 | 529 | first reading |
17 posts held, back to 5 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 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 17 posts for this entry, the most recent from 24 August 2026. An engagement rate over an empty window would be a number about nothing.
76 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 52.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 40 | 52.6% | |
| 🎉 | 14 | 18.4% | |
| 👏 | 10 | 13.2% | |
| ❤ | 9 | 11.8% | |
| 🥰 | 3 | 3.95% |
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 13 of the 17 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 76 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 5 June 2026 to 24 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.
Project milestone update ------- We are pleased to share the successful presentation of LEBIZU's hydrogeological investigation project for Abyssinia Flowers. 💧🌍 The presentation received very positive feedback, and the report was well received by the client team. We are grateful for the constructive discussions and valuable feedback, which will help further strengthen the work. It was a great opportunity to demonst…
🎉4👏3
#GIS and #AI are two digital frontiers that are increasingly converging, with each strengthening the capabilities of the other. ----- Picture from ESRI Eastern Africa presentation slide deck.
👍5
Posted without readable text
Photo, posted without a caption
👍6
QField Training manual ----- A nice application with multiple advantages: - Offline field data collection - Direct integration with QGIS - Easy data and photo capture - Real-time map visualization - Data synchronization - Open-source and cost-effective - Suitable for remote fieldwork - Improves data accuracy and consistency Check the resources
❤3👍2
New project announcement ------- LEBIZU is pleased to partner with DH Consult to deliver a groundwater mapping project for UNICEF across 20 woredas in Ethiopia’s Somali Region. The project will generate critical scientific evidence to improve understanding of groundwater resources and support more resilient water supply planning in one of Ethiopia’s most drought-prone regions. Through integrated hydrogeological ana…
🎉5👏4❤1
LEBIZU embraces the digital frontier, working at the intersection of data and technology. Data quality is at the core of everything we do. We understand how to manage, process, and safeguard data while maintaining the highest standards of quality and integrity. Are you concerned that poor data quality could compromise your project? Partner with LEBIZU. We provide reliable, high-quality data solutions tailored to yo…
👍2🥰1
Know GeoLibre ----- A lightweight, free & open-source cloud-native GIS platform for visualizing, exploring, and analyzing geospatial data across desktop and web ... read more
..... loading :) LEBIZU is close to kickstarting a new and big project. Announcement coming soon. Stay tuned.
👏3❤2🎉2
LEBIZU Contacts We put all our communication channels in one place. Connect with us here
#Webinar: A Synthesis of the Latest WHO and UN Drinking Water Reports for Government Decision Makers ----- Translating global drinking water recommendations to national and local actions. Register
Follow LEBIZU on LinkedIn
👍3❤1
Showing the 12 most recent of 17 posts we hold for @LEBIZUCon. 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“LEBIZU - ONE TO MANY” (@LEBIZUCon), 527 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/LEBIZUCon.
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.