MAARAHWA MTÜ
Date of report 07.04.2025
MAARAHWA MTÜ
Former names
- MaaRahwa MTÜ
keywords
MAARAHWA MTÜ
Scores and ratings
Reputation score
Credit Score
Open the reports you want to print
Employees and salaries
MAARAHWA MTÜ
Employee taxes and performance analysisQuarter | Labor taxes paid | Number of employees | Turnover Per Employee | Profit per employee |
---|---|---|---|---|
2019 IV | ...... | ...... | ...... | ...... |
2019 III | ...... | ...... | ...... | ...... |
2019 II | ...... | ...... | ...... | ...... |
2019 I | ...... | ...... | ...... | ...... |
2018 IV | ...... | ...... | ...... | ...... |
2018 III | ...... | ...... | ...... | ...... |
2018 II | ...... | ...... | ...... | ...... |
2018 I | ...... | ...... | ...... | ...... |
2017 IV | ...... | ...... | ...... | ...... |
2017 III | ...... | ...... | ...... | ...... |
2017 II | ...... | ...... | ...... | ...... |
2017 I | ...... | ...... | ...... | ...... |
2016 IV | ...... | ...... | ...... | ...... |
2016 III | ...... | ...... | ...... | ...... |
2016 II | ...... | ...... | ...... | ...... |
2016 I | ...... | ...... | ...... | ...... |
Deciders and beneficiaries
MAARAHWA MTÜ
Former decision-makers......
Credit Score: Borderline
Reputation score: 240
Date of birth: ......
Active relations 1
2 followers
MAARAHWA MTÜ
History of right of representationFinances and assets
MAARAHWA MTÜ
Taxes paid and estimated average salariesMAARAHWA MTÜ
Financial raiting: "UNSATISFACTORY" ()MAARAHWA MTÜ
Annual reportsAnnual reports MISSING
Liabilities and debts
MAARAHWA MTÜ
Credit score history and prognosis... €
......
Business risk classes:
Trustworthy NeutralMAARAHWA MTÜ
Reports and assets-liabilities overview 23.10.2019MAARAHWA MTÜ
Claims historyTotal debt claims: ...... €
...... | ...... |
MAARAHWA MTÜ
Bailiff's enforcement proceedings as of 23.10.2019Bailiff's enforcement proceedings MISSING
MAARAHWA MTÜ
Regulations of the Payment Order Department as of 23.10.2019Regulations of the Payment Order Department MISSING
MAARAHWA MTÜ
Court orders in the register as of 23.10.2019Court order MISSING
MAARAHWA MTÜ
Decisions of the Consumer Disputes Committee as of 23.10.2019Consumer disputes MISSING
MAARAHWA MTÜ
Court hearings as of 23.10.2019Court hearings MISSING
MAARAHWA MTÜ
Rulings as of 23.10.2019Court settlemets MISSING
MAARAHWA MTÜ
Notices and announcements as of 23.10.2019Notice of service of a decision of the registration department of a court
Avaldamise lõpp: 28.12.2019
Kohus toimetab isikule, MaaRahwa MTÜ (registrikood: 80397106), avalikult kätte 27.05.2019 määruse nr M 50023841 / 3 väljavõtte:
Tartu Maakohtu registriosakonna 27.05.2019 kandemäärusega M 50023841 / 3
Kustutada MaaRahwa MTÜ (registrikood 80397106) mittetulundusühingute ja sihtasutuste registrist ja teha mittetulundusühingute ja sihtasutuste registri registrikaardile kustutamise kanne mittetulundusühingute seaduse § 36.1 lõike 3 alusel.
Käesoleva kandemääruse peale võib esitada määruskaebuse 30 päeva jooksul alates määruse kättetoimetamisest. Mittetulundusühingute ja sihtasutuste registrist kustutamise kannet ei tehta enne, kui on möödunud kandemääruse vaidlustamiseks ettenähtud tähtaeg või vaidlustamise korral on kohtumenetlus lõppenud. Vastavalt riigilõivuseaduse § 59 lõikele 14 tasutakse määruskaebuse esitamisel riigilõivu 50 eurot. Lõiv tuleb tasuda Rahandusministeeriumi arveldusarvele Swedbank a/a EE062200221059223099, AS SEB Pank a/a EE571010220229377229, Luminor Bank AS a/a EE221700017003510302. Maksekorraldusel tuleb kindlasti märkida viitenumber 11170018148158.
Dokument loetakse avalikult kättetoimetatuks 15 päeva möödumisel väljavõtte väljaandes Ametlikud Teadaanded ilmumise päevast.
Pikk 32, 44307 Rakvere
Telefon: 601 1166
E-post: registriosakond@kohus.ee
Marketing
Business network
MAARAHWA MTÜ
Business networkSign in
To expand your connections, log in to the "Networks" environment
Beneficiaries network
MAARAHWA MTÜ
Networks - BeneficiariesSign in
To expand your connections, log in to the "Networks" environment
Monitoring events
Filter
Dropdown
Dropdown
Neutral
Positive
Negative
No monitoring events found.
Failed to load monitoring events.