Channel
@MORMTO1
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
18,365subscribers
+212 since we began measuring on 6 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001676535420 |
|---|---|
| Type | Channel |
| Username | @MORMTO1 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 21 October 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 21 October 2026 |
| On Telegram | t.me/MORMTO1 |
National news — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 |
|---|---|---|
| 21 Oct 2026, 15:46 | 18,365 | +38 |
| 20 Oct 2026, 10:57 | 18,327 | +33 |
| 19 Oct 2026, 08:19 | 18,294 | -1 |
| 18 Oct 2026, 11:16 | 18,295 | -2 |
| 16 Oct 2026, 14:31 | 18,297 | +3 |
| 14 Oct 2026, 18:00 | 18,294 | +4 |
| 13 Oct 2026, 09:30 | 18,290 | +10 |
| 9 Oct 2026, 02:59 | 18,280 | +141 |
| 4 Oct 2026, 15:36 | 18,139 | -11 |
| 26 Sept 2026, 15:20 | 18,150 | +82 |
| 19 Sept 2026, 17:38 | 18,068 | -21 |
| 17 Sept 2026, 03:38 | 18,089 | +30 |
| 15 Sept 2026, 04:39 | 18,059 | -13 |
| 13 Sept 2026, 10:39 | 18,072 | -1 |
| 11 Sept 2026, 11:18 | 18,073 | -24 |
| 8 Sept 2026, 18:14 | 18,097 | -56 |
| 6 Sept 2026, 08:22 | 18,153 | no change |
| 6 Sept 2026, 07:47 | 18,153 | first reading |
14 posts held, back to 3 September 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 14 posts for this entry, the most recent from 6 September 2026. An engagement rate over an empty window would be a number about nothing.
የጠቅላይ ሚኒስትር ዐቢይ አሕመድ (ዶ/ር) የእመርታ ቀን መልዕክት ******* ጠቅላይ ሚኒስትር ዐቢይ አሕመድ (ዶ/ር) ጳጉሜን 1 ቀን የእመርታ ቀንን በማስመልከት ባስተላለፉት መልዕክት አባቶቻችን የኢትዮጵያን ዳር ድንበር በደምና በአጥንታቸው አስከብረው ታላቅ ሀገር አውርሰውናል ብለዋል። ዛሬ ደግሞ እውነተኛ ሉዓላዊነትን እያረጋገጥን ያለነው ከልመናና ከጥገኝነት በተላቀቀው አዲሱና ታሪካዊው መንገዳችን ነው ሲሉ ገልጸዋል። በሚሊዮን በሚቆጠር ዶላር ስንዴ ከማስገባት ተነስተን ዛሬ የአፍሪካ ቀዳሚ ስንዴ አምራች በመሆን የሚሊዮን ዶላሮችን ወጪ ማስቀረት ችለናል ያሉት ጠቅላይ ሚኒስትሩ በ«ሌማት ትሩፋት» የምግብ ዋስትናን በተግባር እያረጋገጥን፣ በ«ኢትዮጵያ ታ…
File, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
የጳጉሜን ወር አምስቱ ቀናት ስያሜዎች
Photo, posted without a caption
File, posted without a caption
File, posted without a caption
Photo, posted without a caption
የታክስ ውሳኔ ማስታወቂያን ለማስተካከል የሚያስችሉ ምክንያቶች፦ በተሻሻለው የፌዴራል ታክስ አስተዳደር አዋጅ ቁጥር 1434/2018 አንቀጽ 96 መሰረት በታክስ ውሳኔ ማስታወቂያ ላይ ማስተካከያ ሊደረግ የሚችለው፦ 👉 የስሌት ወይም የሂሳብ ስህተት ያለ ከሆነ፤ 👉 በታክስ አወሳሰን ወቅት ያልታየ አግባብነት ያለው ማስረጃ ወይም በዚህ አዋጅ መሰረት የቀረበ አዲስ ማስረጃ ያለ እንደሆነ፤ 👉 የታክስ ውሳኔው አስገዳጅ ከሆነው የታክስ ህጎች ትርጉም ጋር የማይጣጣም ከሆነ፤ ወይም 👉 ታክስ የመክፈል ግዴታን በመወሰን ረገድ የተሳሳተ ውጤት የሚያስከትል ሌላ ስህተት ካለ ነው፤
በተሻሻለው የገቢ ግብር አዋጅ እና በአዲሱ የተጨማሪ እሴት ታክስ መመሪያ ላይ ስልጠና ተሰጠ። ነሀሴ 28/2018 ዓ/ም በገቢዎች ሚኒስቴር የመካከለኛ ቁ-1 ግብር ከፋዮች ቅርንጫፍ ጽ/ቤት በአዲሱ የገቢ ግብር ማሻሻያ አዋጅ1395/2017 እና ማሻሻያዎቹን ተከትሎ በተሰጡ ማብራሪያዎች እንዲሁም በአዲሱ የተጨማሪ እሴት ታክስ መመሪያ 1104/2017 ላይ ለቅርንጫፉ ግብር ከፋዮች በዛሬው ዕለት የአንድ ጊዜ ስልጠና ተሰጥቷል፡፡ ሥልጠናውን በይፋ ያስጀመሩት የቅርንጫፍ ጽ/ቤቱ የታክስ ከፋዮች ትምህርትና መረጃ አቅርቦት የሥራ ሂደት አስተባባሪ የሆኑት አቶ ተግባሩ ታምሩ እንዳሉት ቅርንጫፍ ጽ/ በአገልግሎት አሰጣጡም ሆነ በገቢ አሰባሰብ አፈፃፀም ሂደቱ በሁለንተናው የ…
የታክስ አለመግባባትን በመስማማት ስለመፍታት በተሻሻለው የፌዴራል ታክስ አስተዳደር አዋጅ ቁጥር 1434/2018 አንቀጽ 61 የታክሱ ባለስልጣን የታክስ አለመግባባትን በመስማማት ለመፍታት ያለውን ስልጣን በተመለከተ የሚከተለውን ይላል፡- 👉 የታክሱ ባልስልጣን የታክስ አለመግባባቶችን በመስማማት የመፍታት ስልጣን ተሰጥቶታል። 👉 ማናቸውም በስምምነት የሚፈታ የታክስ ያለመግባባት በጽሁፍ የሚደረግ እና የተስማሚ ወገኖች ፊርማ ያረፈበት ሊሆን ይገባል። 👉 የታክስ አለመግባባቶችን በመስማማት የመፍታት ስልጣን የሰጠው ድንጋጌ ቢኖርም የሚከተሉት ሁኔታዎች ሲኖሩ ጉዳዩ በማስማማት ሊታይ አይችልም፦ 1. የታክስ ማጭበርበር ወይም ሆን ተብሎ የተደረገ ታክስን የመሰወር ድርጊት …
Showing the 12 most recent of 14 posts we hold for @MORMTO1. 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.
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 21 October 2026 — this entry's latest reading, not the date you are reading this.
“M.O.R. Medium Tax Payers No 1 Branch Office” (@MORMTO1), 18,365 subscribers as measured 21 October 2026. Telegram Register, tgregister.com/channel/MORMTO1.
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.