[mo_oauth_login]
Summary report
Vladyslav Chornyi
Date of report 19.06.2025
☆☆☆☆
Date of birth: ......
Active relations: 2
Beginning of enterprise experience: 28.04.2025
CONTACT
Harju maakond, Viimsi vald, Pringi küla, Rohuneeme tee 61b
chorny777vladislav@gmail.com
+372 53754623
Reputation score
Credit Score
What is Credit Score?Open the reports you want to print
Board Member CV
?
Aktiivne
Kustutatud
Employees and salaries
Finances
Vladyslav Chornyi
Company economic performance and prognosis?
Company | Turnover | Assets | Liabilities | Equity | Net profit |
---|
Vladyslav Chornyi
Volumes and values of beneficiary assets?
Net asset value of the beneficiary
... €
Value of beneficiary companies using the income method
... €
Analytically identified company holdings and asset volumes
Company name | Retained profits | Fixed assets | Balance sheet total | Holdings |
---|---|---|---|---|
...... | ...... | ...... | ...... |
100%
|
...... | ...... | ...... | ...... |
Liabilities
Vladyslav Chornyi
Debt balance and history graph1 month
6 months
Year
5 years
MAX
1 month
6 months
Year
5 years
MAX
Debt claims as of ......
Total debt claims: ...... €
Vladyslav Chornyi
Compliance with reporting
Filled
Unfilled
Outside the liability period
Companies | Beginning of representation | Ending of representation | Annual reports | Tax declarations |
---|
Total reports | |
---|---|
Submitted | |
Unsubmitted |
Business network
Vladyslav Chornyi
Business networkCREDIT RISK CLASSES
Deleted
Trustworthy
Neutral
Borderline
Problematic
Risky
Historical connection
Active connection
amount of turnover
amount of debt
Extension of networks
The network is visible with reduced links
Expand threads if desired
Sign in
To expand your connections, log in to the "Networks" environment
Beneficiaries Network
Vladyslav Chornyi
Networks - Beneficiaries
The network is visible with reduced links
Expand threads if desired
Sign in
To expand your connections, log in to the "Networks" environment
Monitoring
Filter
Dropdown
Dropdown
Neutral
Positive
Negative
No monitoring events found.
Failed to load monitoring events.