VIPCOM OÜ
Date of report 13.02.2025
VIPCOM OÜ
Former names
- OÜ Vipcom
start | end |
---|---|
07.12.2006 | 31.01.2009 |
keywords
VIPCOM OÜ
Scores and ratings
Reputation score
Credit Score
Open the reports you want to print
Employees and salaries
Deciders and beneficiaries
VIPCOM OÜ
Former decision-makers......
Credit Score: Neutral
Reputation score: 390
Date of birth: ......
Active relations 4
6 followers
......
Credit Score: Problematic
Reputation score: -26670
Date of birth: ......
Active relations 6
2 followers
......
Credit Score: Trustworthy
Reputation score: 80
Date of birth: ......
Active relations 1
0 followers
VIPCOM OÜ
History of right of representationVIPCOM OÜ
OwnersFormer owners
VIPCOM OÜ
Other related partiesFormer other persons
Name | Credit Score | Part | Beginning |
---|---|---|---|
...... | ...... |
Finances and assets
VIPCOM OÜ
Taxes paid and estimated average salariesVIPCOM OÜ
Financial raiting: "UNSATISFACTORY" ()VIPCOM OÜ
Annual reportsYear | Period | Submitted | Report PDF |
---|---|---|---|
2007 | 01.01.2007–31.12.2007 | 01.12.2008 | ...... |
Liabilities and debts
VIPCOM OÜ
Reports and assets-liabilities overview 04.05.2011VIPCOM OÜ
Claims historyTotal debt claims: ...... €
...... | ...... |
VIPCOM OÜ
Bailiff's enforcement proceedings as of 04.05.2011Bailiff's enforcement proceedings MISSING
VIPCOM OÜ
Regulations of the Payment Order Department as of 04.05.2011Regulations of the Payment Order Department MISSING
VIPCOM OÜ
Court orders in the register as of 04.05.2011Court order MISSING
VIPCOM OÜ
Decisions of the Consumer Disputes Committee as of 04.05.2011Consumer disputes MISSING
VIPCOM OÜ
Court hearings as of 04.05.2011Court hearings MISSING
VIPCOM OÜ
Rulings as of 04.05.2011Court settlemets MISSING
VIPCOM OÜ
Notices and announcements as of 04.05.2011Announcements MISSING
Marketing
Business network
VIPCOM OÜ
Business networkSign in
To expand your connections, log in to the "Networks" environment
Beneficiaries network
Monitoring events
Filter
Dropdown
Dropdown
Neutral
Positive
Negative
No monitoring events found.
Failed to load monitoring events.