LIPULAEV MTÜ
Date of report 15.01.2025
LIPULAEV MTÜ
Former names
- Mittetulundusühing Lipulaev
keywords
LIPULAEV MTÜ
Scores and ratings
Reputation score
Credit Score
Open the reports you want to print
Employees and salaries
Deciders and beneficiaries
LIPULAEV MTÜ
Former decision-makers......
Credit Score: None
Reputation score: None
Date of birth: ......
Active relations 0
0 followers
......
Credit Score: Neutral
Reputation score: 3370
Date of birth: ......
Active relations 5
7 followers
......
Credit Score: Trustworthy
Reputation score: 570
Date of birth: ......
Active relations 1
2 followers
......
Credit Score: None
Reputation score: None
Date of birth: ......
Active relations 0
0 followers
LIPULAEV MTÜ
History of right of representationFinances and assets
LIPULAEV MTÜ
Taxes paid and estimated average salariesLIPULAEV MTÜ
Financial raiting: "UNSATISFACTORY" ()LIPULAEV MTÜ
Annual reportsAnnual reports MISSING
Liabilities and debts
LIPULAEV MTÜ
Reports and assets-liabilities overview 26.06.2013LIPULAEV MTÜ
Claims historyTotal debt claims: ...... €
...... | ...... |
LIPULAEV MTÜ
Bailiff's enforcement proceedings as of 26.06.2013Bailiff's enforcement proceedings MISSING
LIPULAEV MTÜ
Regulations of the Payment Order Department as of 26.06.2013Regulations of the Payment Order Department MISSING
LIPULAEV MTÜ
Court orders in the register as of 26.06.2013Court order MISSING
LIPULAEV MTÜ
Decisions of the Consumer Disputes Committee as of 26.06.2013Consumer disputes MISSING
LIPULAEV MTÜ
Court hearings as of 26.06.2013Court hearings MISSING
LIPULAEV MTÜ
Rulings as of 26.06.2013Court settlemets MISSING
LIPULAEV MTÜ
Notices and announcements as of 26.06.2013Announcements MISSING
Marketing
Business network
LIPULAEV MTÜ
Business networkSign in
To expand your connections, log in to the "Networks" environment
Beneficiaries network
LIPULAEV 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.