Channel
@bureauof
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
6,617subscribers
+43 since we began measuring on 26 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001489445025 |
|---|---|
| Type | Channel |
| Username | @bureauof |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 26 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/bureauof |
Local community — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 56% 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 |
|---|---|---|
| 19 Sept 2026, 02:21 | 6,617 | +9 |
| 14 Sept 2026, 18:20 | 6,608 | +1 |
| 10 Sept 2026, 20:20 | 6,607 | +3 |
| 6 Sept 2026, 00:36 | 6,604 | +2 |
| 2 Sept 2026, 06:12 | 6,602 | +3 |
| 29 Aug 2026, 21:26 | 6,599 | +20 |
| 27 Aug 2026, 03:56 | 6,579 | +5 |
| 26 Aug 2026, 04:46 | 6,574 | first reading |
11 posts held, back to 21 August 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 11 posts for this entry, the most recent from 24 August 2026. An engagement rate over an empty window would be a number about nothing.
የጎንደር ከተማ ገቢዎች መምሪያ በ2019 በጀት ዓመት 8.8 ቢሊዮን ብር ለመሰብሰበ ማቀዱን ኣሳወቀ በ17/12/2018 (የጎንደር ከተማ ገቢዎች መምሪያ) ከመምሪያ እና ከክፍለ ከተማ ማኔጅመንት አባላት ጋር የ2019 በጀት ዓመት አጠቃላይ የዕቅድ ትውውቅ መድረክ አካሄዷል። በመድረኩ ላይ የተቋሙ የማኔጅመንት አባላት፣ የክፍለ ከተማ ገቢዎች ጽ/ቤት ኃላፊዎች፣ የክፍለ ከተማ ማኔጅመንት አባላት እና የክልል ደጋፊ ባለሙያዎች ተገኝተዋል። የ2018 በጀት ዓመት እቅድ አፈጻጸም እና የ2019 በጀት ዓመት እቅድ ሰነድ በመምሪያው የእቅድ ዝግጅትና ክትትል ባለሙያ የሆኑት አቶ አየልኝ ዱቤ አቅርበዋል። የመምሪያ ኃላፊ የሆኑት ወ/ሮ ጥሩየ አትክልት እንደገለጹት የጎንደ…
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
ነሐሴ 16 2018 የኦሮሚያ ክልል ያቃረበውን ቅሬታ የተመለከተው የአሸማጋይ ቡድን አዲስ አበባ የኦሮሚያ ክልል ርዕሰ ከተማ መሆኗ በህገ መንግስት ይጻፍ የሚል ምክረ ሃሳብ አቅርቦ፤ የ500 ቡድን አዲስ አበባ የፌደራል መንግስት አካል ናት በሚል የተስማማበት ቀርቶ "ተጠሪ" በሚል እንዲተካ ምክረ ሃሳብ አቅርቦ ምክክሩ ተጠናቋል። ከሐምሌ 8 ቀን 2018 ዓ.ም. ጀምሮ ላለፉት 38 ቀናት ሲካሄድ የቆየው የምክክር ጉባዔ ፕሬዚዳንት ታዬ አጽቀሥላሴ፣ የኢጋድ ዋና ጸሐፊ ወርቅነህ ገበየሁ፣ የቀድሞው የኬንያ ፕሬዚዳንት ኡሁሩ ኬንያታን ጨምሮ ሌሎች የመንግሥት የሥራ ኃላፊዎች በተገኙበት በይፋ ተጠናቋል። አዲስ አበባን በተመለከተ በሁለት ጎራ ከፍሎ ሲያከራክር የቆየው…
Photo, posted without a caption
Photo, posted without a caption
የደሴ ከተማ አስተዳደር ገቢዎች መምሪያ በ2019 በጀት ዓመት 8.2 ቢሊየን ገቢ ለመሰብሰብ ዕቅድ ይዞ እየሰራ መሆኑን አስታወቀ። የደሴ ከተማ አስተዳደር ገቢዎች መምሪያ የ2018 በጀት ዓመት የዕቅድ አፈጻጸም ግምገማና የ2019 በጀት ዓመት ዕቅድ ትውውቅ መድረክ አካሂዷል። የደሴ ከተማ አስተዳደር ምክትል ከንቲባ አቶ ሽመልስ ጌታቸው በመድረኩ እንደገለጹት የከተማዋን ገቢ በአግባቡ ለመሰብሰብ በተቀናጀና በተጠናከረ አሠራር መስራትና የገቢ አሰባሰብ ሥርዓቱን ማሻሻል ይገባል ብለዋል። በገቢ አሰባሰብ ሂደት የሚታዩ ችግሮችን በጋራ በመፍታትና የተጠናከረ ክትትል በማድረግ የከተማዋን የልማት እንቅስቃሴ ማሳካትና ከተማዋን ወደተሻለ የልማት ደረጃ ማሸጋገር እንደሚገባ…
ከአምስት ቢሊዮን 39 ሚሊዮን በላይ ገቢ ለመሰብሰብ እየሰራ መኾኑን የምዕራብ ጎጃም ዞን ገቢዎች መምሪያ አስታወቀ ። የ2018 በጀት ዓመት የአሻጋሪ እድገት እና ዘላቂ የልማት እቅድc አፈፃፀም ግምገማ እና የ2019 እቅድ ትውውቅ መድረክ ከባለድርሻ አካላት ጋር አካሂዷል። አቶ ግዛቶች ካሴ የዞኑ ገቢዎች መምሪያ ኀላፊ በ2019 በጀት ዓመት ከተለያዩ የገቢ አርዕስቶች ከአምስት ቢሊዮን 39 ሚሊዮን ብር በላይ ገቢ ለመሰብሰብ እየተሰራ መኾኑን ገልፀዋል። በ2018 በጀት ዓመት ከታቀደው 3 ነጥብ አንድ ቢሊዮን ብር ገቢ ከ2 ነጥብ ሶስት ቢሊዮን ብር በላይ ገቢ ቢሰበሰብም የፀጥታ ችግሩ የሚጠበቀውን ገቢ ለመሰብሰብ ተግዳሮት መፍጠሩን አስረድተዋል። በተለይ በበጀት…
Photo, posted without a caption
Showing the 11 most recent of 11 posts we hold for @bureauof. 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“Amhara Revenue Bureau” (@bureauof), 6,617 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/bureauof.
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.