BPMONLINE SOFTWARE OÜ
Date of report 19.04.2025
Open the reports you want to print
Employees and salaries
BPMONLINE SOFTWARE OÜ
Employee taxes and performance analysis?
| Quarter | Labor taxes paid | Number of employees | Turnover Per Employee | Profit per employee |
|---|---|---|---|---|
| 2019 III | ...... | ...... | ...... | ...... |
| 2019 II | ...... | ...... | ...... | ...... |
| 2019 I | ...... | ...... | ...... | ...... |
| 2018 IV | ...... | ...... | ...... | ...... |
| 2018 III | ...... | ...... | ...... | ...... |
| 2018 II | ...... | ...... | ...... | ...... |
| 2018 I | ...... | ...... | ...... | ...... |
Deciders and beneficiaries
BPMONLINE SOFTWARE OÜ
Former decision-makers?
Relations:
Turnover:
Employees:
Oleksandr Popov
★★★★
......
Credit Score: None
Reputation score: None
Date of birth: ......
Active relations 0
Relations:
5
Turnover 2025:
1 267 038 599 €
Employees:
21
Triin Nagel
★★★★
......
Credit Score: Borderline
Reputation score: 4360
Date of birth: ......
Active relations 5
BPMONLINE SOFTWARE OÜ
History of right of representation?
Field
Business age
1y
Beneficial country:
et
Triin Nagel
... - ...
Oleksandr Popov
... - ...
2018
2019
2020
2021
2022
2023
2024
2025
2018
2019
2020
2021
2022
2023
2024
2025
BPMONLINE SOFTWARE OÜ
Owners?
Former owners
Former owners
| Name | Credit Score | Payment | Beginning | Ending |
|---|---|---|---|---|
| ...... | ...... | ...... |
BPMONLINE SOFTWARE OÜ
Other related parties?
Former other persons
Finances and assets
BPMONLINE SOFTWARE OÜ
Taxes paid and estimated average salariesBPMONLINE SOFTWARE OÜ
Financial indicators and prognosisBPMONLINE SOFTWARE OÜ
Financial raiting: "GOOD" (2018)2018
LIQUIDITY
?
Net Working capital
...
Short-term debt coverage ratio
...
USE OF LOAN CAPITAL
?
Turnover ratio of fixed assets (X)
...
EFFECTIVENESS
?
Debt to assets ratio (X)
...
Capitalisation multiplier (X)
...
PROFITABILITY
?
Sales revenues (%)
...
Total asset revenues (%)
...
Equity revenues (%)
...
Unsatisfactory
1
2
3
4
5
Very good
BPMONLINE SOFTWARE OÜ
Annual reports| Year | Period | Submitted | Report PDF |
|---|---|---|---|
| 2018 | 01.01.2018–31.12.2018 | 10.01.2019 | ...... |
Liabilities and debts
BPMONLINE SOFTWARE OÜ
Credit score history and prognosisRecommended credit limit
... €
Recommended payment term
......
Business risk classes:
Trustworthy Neutral
Borderline
Problematic
Risky
BPMONLINE SOFTWARE OÜ
Reports and assets-liabilities overview 10.07.2019?
Annual reports:
......
Annual reports: ......
Tax declarations:......
Assets to cover liabilities (short-term)
Assets: ...... €1 EURO of assets to cover short-term debt obligations: ...... €
Liabilities: ...... €Net Working capital: ...... €
BPMONLINE SOFTWARE OÜ
Claims history?
Debt claims as of ......
Total debt claims: ...... €
Latest events
| ...... | ...... |
BPMONLINE SOFTWARE OÜ
Bailiff's enforcement proceedings as of 10.07.2019?
Bailiff's enforcement proceedings MISSING
BPMONLINE SOFTWARE OÜ
Regulations of the Payment Order Department as of 10.07.2019?
Regulations of the Payment Order Department MISSING
BPMONLINE SOFTWARE OÜ
Court orders in the register as of 10.07.2019?
Court order MISSING
BPMONLINE SOFTWARE OÜ
Decisions of the Consumer Disputes Committee as of 10.07.2019?
Consumer disputes MISSING
BPMONLINE SOFTWARE OÜ
Court hearings as of 10.07.2019?
Court hearings MISSING
BPMONLINE SOFTWARE OÜ
Rulings as of 10.07.2019?
Court settlemets MISSING
BPMONLINE SOFTWARE OÜ
Notices and announcements as of 10.07.2019?
Notice of liquidation proceedings of a private limited company
08.11.2018
Marketing
Business network
BPMONLINE SOFTWARE OÜ
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
Beneficiaries network
BPMONLINE SOFTWARE OÜ
Networks - Beneficiaries
The network is visible with reduced links
Expand threads if desired
Monitoring events
Filter
Dropdown
Dropdown
Neutral
Positive
Negative
No monitoring events found.
Failed to load monitoring events.