OLEG BELYSHEV FIE
Date of report 03.02.2025
OLEG BELYSHEV FIE
Former names
- OLEG BELÕŠEV
- OLEG BELYSHEV
start | end |
---|---|
15.10.2003 | 30.11.2012 |
start | end |
---|---|
01.01.2002 | 31.08.2003 |
keywords
- kaubavedu maanteel
OLEG BELYSHEV FIE
Scores and ratings
Reputation score
Credit Score
Open the reports you want to print
Employees and salaries
OLEG BELYSHEV FIE
Employee taxes and performance analysisQuarter | Labor taxes paid | Number of employees | Turnover Per Employee | Profit per employee |
---|---|---|---|---|
2021 IV | ...... | ...... | ...... | ...... |
2021 III | ...... | ...... | ...... | ...... |
2021 II | ...... | ...... | ...... | ...... |
2021 I | ...... | ...... | ...... | ...... |
2020 IV | ...... | ...... | ...... | ...... |
2020 III | ...... | ...... | ...... | ...... |
2020 II | ...... | ...... | ...... | ...... |
2020 I | ...... | ...... | ...... | ...... |
2019 IV | ...... | ...... | ...... | ...... |
2019 III | ...... | ...... | ...... | ...... |
2019 II | ...... | ...... | ...... | ...... |
2019 I | ...... | ...... | ...... | ...... |
2018 IV | ...... | ...... | ...... | ...... |
2018 III | ...... | ...... | ...... | ...... |
2018 II | ...... | ...... | ...... | ...... |
2018 I | ...... | ...... | ...... | ...... |
2017 IV | ...... | ...... | ...... | ...... |
2017 III | ...... | ...... | ...... | ...... |
2017 II | ...... | ...... | ...... | ...... |
2017 I | ...... | ...... | ...... | ...... |
2016 IV | ...... | ...... | ...... | ...... |
2016 III | ...... | ...... | ...... | ...... |
2016 II | ...... | ...... | ...... | ...... |
2016 I | ...... | ...... | ...... | ...... |
2015 IV | ...... | ...... | ...... | ...... |
2015 III | ...... | ...... | ...... | ...... |
2015 II | ...... | ...... | ...... | ...... |
2015 I | ...... | ...... | ...... | ...... |
Deciders and beneficiaries
OLEG BELYSHEV FIE
Former decision-makers......
Credit Score: Neutral
Reputation score: 580
Date of birth: ......
Active relations 2
0 followers
OLEG BELYSHEV FIE
History of right of representationOLEG BELYSHEV FIE
OwnersFormer owners
Former owners
Name | Credit Score | Payment | Beginning | Ending |
---|---|---|---|---|
...... | ...... |
Finances and assets
OLEG BELYSHEV FIE
Taxes paid and estimated average salariesOLEG BELYSHEV FIE
Financial indicators and prognosisOLEG BELYSHEV FIE
Financial raiting: "SATISFACTORY" (2021 prognosis)OLEG BELYSHEV FIE
Annual reportsAnnual reports MISSING
Liabilities and debts
OLEG BELYSHEV FIE
Credit score history and prognosis... €
......
Business risk classes:
Trustworthy NeutralOLEG BELYSHEV FIE
Reports and assets-liabilities overview 30.12.2021OLEG BELYSHEV FIE
Claims historyTotal debt claims: ...... €
...... | ...... |
OLEG BELYSHEV FIE
Debt by type 02.02.2025Type of claim | Amount of claims | In repayment schedule | Disputed | Management board during which the debt was incurred | Representative |
---|---|---|---|---|---|
Tax collector 's claims | ...... € | ...... € | ...... € | ||
Social tax | ...... € | ...... € | ...... € | ETCB | |
SUNNIRAHA | ...... € | ...... € | ...... € | ETCB | |
Creditors' claims | ...... € | ...... € | ...... € | ||
Total | ...... € | ...... € | ...... € |
OLEG BELYSHEV FIE
Time-barred and ongoing claims as of 30.12.2021Sum:
...... €
Sum:
...... €
OLEG BELYSHEV FIE
Bailiff's enforcement proceedings as of 30.12.2021Bailiff's enforcement proceedings MISSING
OLEG BELYSHEV FIE
Regulations of the Payment Order Department as of 30.12.2021Regulations of the Payment Order Department MISSING
OLEG BELYSHEV FIE
Court orders in the register as of 30.12.2021Määruse avalik kättetoimetamine AT-s
Regulation number: Ä 40015563 / M2
Regulation status has entered into force: 14.01.2022
Date of enforcement of order or additional period: 14.01.2022
Regulation status: Jõustunud
Kandemäärus ex officio
Regulation number: Ä 40015563 / 8
Regulation status has entered into force: 13.02.2022
Date of enforcement of order or additional period: 17.02.2022
Regulation status: Jõustunud
Korraldav määrus
Regulation number: Ä 40015563 / M1
Regulation status has entered into force: 13.12.2021
Date of enforcement of order or additional period: 13.12.2021
Regulation status: Jõustunud
OLEG BELYSHEV FIE
Decisions of the Consumer Disputes Committee as of 30.12.2021Consumer disputes MISSING
OLEG BELYSHEV FIE
Court hearings as of 30.12.2021Court hearings MISSING
OLEG BELYSHEV FIE
Rulings as of 30.12.2021Court settlemets MISSING
OLEG BELYSHEV FIE
Notices and announcements as of 30.12.2021Notice of service of a decision of the registration department of a court
Avaldamise lõpp: 14.07.2022
Kohus toimetab isikule, OLEG BELYSHEV (registrikood: 10971615), avalikult kätte 30.12.2021 määruse nr Ä 40015563 / 8 väljavõtte:
Tartu Maakohtu registriosakonna 30.12.2021 kandemäärusega Ä 40015563 / 8 on tehtud OLEG BELYSHEV (registrikood 10971615) kohta äriregistri registrikaardile registripidaja algatusel ilma kandeavalduseta alljärgnev kustutamiskanne: Füüsilisest isikust ettevõtja on äriregistrist kustutatud äriseadustiku § 59 lg 3² alusel.
Kandemääruse Ä 40015563 / 8 peale võib esitada määruskaebuse Tartu Ringkonnakohtule Tartu Maakohtu registriosakonna kaudu 15 päeva jooksul alates määruse kättetoimetamisest. Riigilõivuseaduse § 59 lõike 14 kohaselt tasutakse määruskaebuse esitamisel riigilõivu 50 eurot. Riigilõiv tuleb tasuda Rahandusministeeriumi arveldusarvele: Swedbank EE062200221059223099, SEB Pank EE571010220229377229, Luminor Bank EE221700017003510302, LHV Pank EE567700771003819792. Maksekorraldusel tuleb märkida viitenumber 11170024595410.
Dokument loetakse avalikult kättetoimetatuks 15 päeva möödumisel ametlikus väljaandes Ametlikud Teadaanded ilmumise päevast.
Pikk 32, 44307 Rakvere
Telefon: 601 1166
E-post: registriosakond@kohus.ee
Marketing
Business network
OLEG BELYSHEV FIE
Business networkSign in
To expand your connections, log in to the "Networks" environment
Beneficiaries network
OLEG BELYSHEV 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.