ROOSIMAA AS
Date of report 05.04.2025
ROOSIMAA AS
Former names
- AS Roosimaa
start | end |
---|---|
01.11.1996 | 31.03.2002 |
keywords
ROOSIMAA AS
Scores and ratings
Reputation score
Credit Score
Open the reports you want to print
Employees and salaries
Deciders and beneficiaries
ROOSIMAA AS
Former decision-makers......
Credit Score: Trustworthy
Reputation score: 3330
Date of birth: ......
Active relations 4
7 followers
......
Credit Score: Trustworthy
Reputation score: 38430
Date of birth: ......
Active relations 15
52 followers
ROOSIMAA AS
History of right of representationROOSIMAA AS
OwnersFormer owners
Former owners
Name | Credit Score | Payment | Beginning | Ending |
---|---|---|---|---|
...... | ...... | ...... |
ROOSIMAA AS
Other related partiesFormer other persons
Finances and assets
ROOSIMAA AS
Taxes paid and estimated average salariesROOSIMAA AS
Financial raiting: "UNSATISFACTORY" ()ROOSIMAA AS
Annual reportsLiabilities and debts
ROOSIMAA AS
Reports and assets-liabilities overview 07.02.2008ROOSIMAA AS
Claims historyTotal debt claims: ...... €
...... | ...... |
ROOSIMAA AS
Bailiff's enforcement proceedings as of 07.02.2008Bailiff's enforcement proceedings MISSING
ROOSIMAA AS
Regulations of the Payment Order Department as of 07.02.2008Regulations of the Payment Order Department MISSING
ROOSIMAA AS
Court orders in the register as of 07.02.2008Court order MISSING
ROOSIMAA AS
Decisions of the Consumer Disputes Committee as of 07.02.2008Consumer disputes MISSING
ROOSIMAA AS
Court hearings as of 07.02.2008Court hearings MISSING
ROOSIMAA AS
Rulings as of 07.02.2008Court settlemets MISSING
ROOSIMAA AS
Notices and announcements as of 07.02.2008Announcements MISSING
Marketing
Business network
ROOSIMAA AS
Business networkSign in
To expand your connections, log in to the "Networks" environment
Beneficiaries network
ROOSIMAA AS
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.