BAIERSEE OÜ
Date of report 25.03.2025
BAIERSEE OÜ
Former names
- osaühing Baiersee
start | end |
---|---|
22.07.2010 | 07.08.2012 |
keywords
BAIERSEE OÜ
Scores and ratings
Reputation score
Credit Score
Open the reports you want to print
Employees and salaries
Deciders and beneficiaries
BAIERSEE OÜ
Former decision-makers......
Credit Score: None
Reputation score: None
Date of birth: ......
Active relations 0
0 followers
......
Credit Score: Trustworthy
Reputation score: 1780
Date of birth: ......
Active relations 4
8 followers
BAIERSEE OÜ
History of right of representationBAIERSEE OÜ
OwnersFormer owners
BAIERSEE OÜ
Other related partiesFormer other persons
Name | Credit Score | Part | Beginning |
---|---|---|---|
...... | ...... |
Finances and assets
BAIERSEE OÜ
Taxes paid and estimated average salariesBAIERSEE OÜ
Financial indicators and prognosisBAIERSEE OÜ
Financial raiting: "SATISFACTORY" (2011)BAIERSEE OÜ
Annual reportsLiabilities and debts
BAIERSEE OÜ
Reports and assets-liabilities overview 07.08.2012BAIERSEE OÜ
Claims historyTotal debt claims: ...... €
...... | ...... |
BAIERSEE OÜ
Bailiff's enforcement proceedings as of 07.08.2012Bailiff's enforcement proceedings MISSING
BAIERSEE OÜ
Regulations of the Payment Order Department as of 07.08.2012Regulations of the Payment Order Department MISSING
BAIERSEE OÜ
Court orders in the register as of 07.08.2012Court order MISSING
BAIERSEE OÜ
Decisions of the Consumer Disputes Committee as of 07.08.2012Consumer disputes MISSING
BAIERSEE OÜ
Court hearings as of 07.08.2012Court hearings MISSING
BAIERSEE OÜ
Rulings as of 07.08.2012Court settlemets MISSING
BAIERSEE OÜ
Notices and announcements as of 07.08.2012Announcements MISSING
Marketing
Business network
BAIERSEE OÜ
Business networkSign in
To expand your connections, log in to the "Networks" environment
Beneficiaries network
BAIERSEE OÜ
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.