FERMECOM OÜ
Date of report 28.03.2025
FERMECOM OÜ
Former names
- osaühing FERMECOM VARA
- OÜ FERMECOM
start | end |
---|---|
01.12.1997 | 30.04.2003 |
keywords
FERMECOM OÜ
Scores and ratings
Reputation score
Credit Score
Open the reports you want to print
Employees and salaries
Deciders and beneficiaries
FERMECOM OÜ
Former decision-makers......
Credit Score: Trustworthy
Reputation score: 760
Date of birth: ......
Active relations 2
0 followers
......
Credit Score: Trustworthy
Reputation score: 2200
Date of birth: ......
Active relations 1
7 followers
FERMECOM OÜ
History of right of representationFERMECOM OÜ
OwnersFormer owners
FERMECOM OÜ
Other related partiesFormer other persons
Name | Credit Score | Part | Beginning |
---|---|---|---|
...... | ...... |
Finances and assets
FERMECOM OÜ
Taxes paid and estimated average salariesFERMECOM OÜ
Financial raiting: "UNSATISFACTORY" ()FERMECOM OÜ
Annual reportsAnnual reports MISSING
Liabilities and debts
FERMECOM OÜ
Reports and assets-liabilities overview 27.12.2005FERMECOM OÜ
Claims historyTotal debt claims: ...... €
...... | ...... |
FERMECOM OÜ
Bailiff's enforcement proceedings as of 27.12.2005Bailiff's enforcement proceedings MISSING
FERMECOM OÜ
Regulations of the Payment Order Department as of 27.12.2005Regulations of the Payment Order Department MISSING
FERMECOM OÜ
Court orders in the register as of 27.12.2005Court order MISSING
FERMECOM OÜ
Decisions of the Consumer Disputes Committee as of 27.12.2005Consumer disputes MISSING
FERMECOM OÜ
Court hearings as of 27.12.2005Court hearings MISSING
FERMECOM OÜ
Rulings as of 27.12.2005Court settlemets MISSING
FERMECOM OÜ
Notices and announcements as of 27.12.2005Announcements MISSING
Marketing
Business network
FERMECOM OÜ
Business networkSign in
To expand your connections, log in to the "Networks" environment
Beneficiaries network
FERMECOM 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.