PAVEL KONOVALOV FIE
Date of report 24.05.2025
PAVEL KONOVALOV FIE
Former names
- Pavel Konovalov
start | end |
---|---|
27.06.2007 | 12.04.2011 |
keywords
PAVEL KONOVALOV FIE
Scores and ratings
Reputation score
Credit Score
Open the reports you want to print
Employees and salaries
Deciders and beneficiaries
PAVEL KONOVALOV FIE
Former decision-makers......
Credit Score: Risky
Reputation score: 330
Date of birth: ......
Active relations 1
0 followers
PAVEL KONOVALOV FIE
History of right of representationPAVEL KONOVALOV FIE
OwnersFormer owners
Former owners
Name | Credit Score | Payment | Beginning | Ending |
---|---|---|---|---|
...... | ...... |
Finances and assets
PAVEL KONOVALOV FIE
Taxes paid and estimated average salariesPAVEL KONOVALOV FIE
Financial raiting: "UNSATISFACTORY" ()PAVEL KONOVALOV FIE
Annual reportsAnnual reports MISSING
Liabilities and debts
PAVEL KONOVALOV FIE
Reports and assets-liabilities overview 06.10.2011PAVEL KONOVALOV FIE
Claims historyTotal debt claims: ...... €
...... | ...... |
PAVEL KONOVALOV FIE
Bailiff's enforcement proceedings as of 06.10.2011Bailiff's enforcement proceedings MISSING
PAVEL KONOVALOV FIE
Regulations of the Payment Order Department as of 06.10.2011Regulations of the Payment Order Department MISSING
PAVEL KONOVALOV FIE
Court orders in the register as of 06.10.2011Court order MISSING
PAVEL KONOVALOV FIE
Decisions of the Consumer Disputes Committee as of 06.10.2011Consumer disputes MISSING
PAVEL KONOVALOV FIE
Court hearings as of 06.10.2011Court hearings MISSING
PAVEL KONOVALOV FIE
Rulings as of 06.10.2011Court settlemets MISSING
PAVEL KONOVALOV FIE
Notices and announcements as of 06.10.2011Announcements MISSING
Marketing
Business network
PAVEL KONOVALOV FIE
Business networkSign in
To expand your connections, log in to the "Networks" environment
Beneficiaries network
PAVEL KONOVALOV FIE
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.