BALTPOS OÜ
Date of report 08.04.2025
BALTPOS OÜ
Former names
- Osaühing BALTPOS
keywords
BALTPOS OÜ
Scores and ratings
Reputation score
Credit Score
Open the reports you want to print
Employees and salaries
Deciders and beneficiaries
BALTPOS OÜ
Former decision-makers......
Credit Score: Neutral
Reputation score: 690
Date of birth: ......
Active relations 2
0 followers
BALTPOS OÜ
History of right of representationBALTPOS OÜ
OwnersFormer owners
Former owners
Name | Credit Score | Payment | Beginning | Ending |
---|---|---|---|---|
...... | ...... | ...... |
BALTPOS OÜ
Other related partiesFormer other persons
Name | Credit Score | Part | Beginning |
---|---|---|---|
...... | ...... |
Finances and assets
BALTPOS OÜ
Taxes paid and estimated average salariesBALTPOS OÜ
Financial raiting: "UNSATISFACTORY" ()BALTPOS OÜ
Annual reportsYear | Period | Submitted | Report PDF |
---|---|---|---|
2000 | 01.01.2000–31.12.2000 | 02.04.2002 | ...... |
Liabilities and debts
BALTPOS OÜ
Reports and assets-liabilities overview 15.12.2005BALTPOS OÜ
Claims historyTotal debt claims: ...... €
...... | ...... |
BALTPOS OÜ
Bailiff's enforcement proceedings as of 15.12.2005Bailiff's enforcement proceedings MISSING
BALTPOS OÜ
Regulations of the Payment Order Department as of 15.12.2005Regulations of the Payment Order Department MISSING
BALTPOS OÜ
Court orders in the register as of 15.12.2005Court order MISSING
BALTPOS OÜ
Decisions of the Consumer Disputes Committee as of 15.12.2005Consumer disputes MISSING
BALTPOS OÜ
Court hearings as of 15.12.2005Court hearings MISSING
BALTPOS OÜ
Rulings as of 15.12.2005Court settlemets MISSING
BALTPOS OÜ
Notices and announcements as of 15.12.2005Announcements MISSING
Marketing
Business network
BALTPOS OÜ
Business networkSign in
To expand your connections, log in to the "Networks" environment
Beneficiaries network
BALTPOS 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.