Регламент проверки контрагента в компании
Рассказываем, по каким причинам важно разработать внутренний документ проверки контрагента.
Details
LLC "Avangard"
Omsk Region
OGRN: 1075530000281
TIN: 5530005074
Activity ceased on March 23, 2020
Profile views
62
+1 last week
Subscribers
0
+0 last week
OKVED2 42.21 Total: 19
Construction of utility projects for fluids
Monitoring Notes Reports Contact information
Competitive managing director
Yeshchenko Vyacheslav Anatolievich
12
years
Established
September 3, 2007
workers settlement Poltavka
6,76
mln ₽, 2016
Revenue
+₽5mln
18
Connections
+0 last week
Employees
No data

SRO membership

Member of 0 self-regulatory organizations

Was member of 1 self-regulated organization

SRO membership information

General information

SRO member status:
▒▒▒▒▒▒▒▒
Information on the compliance of the SRO member with the membership terms:
▒▒▒▒▒▒▒▒▒▒▒▒▒
SRO Register member registration number:
▒▒▒▒
Date of registration in the SRO Register:
▒▒.▒▒.2010
Membership termination date:
▒▒.▒▒.2017
Grounds for termination of membership:
▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒ ▒▒ ▒▒▒▒▒▒▒ ▒▒▒ ▒▒ ▒▒ ▒▒▒▒▒▒▒▒▒▒

Compensation Fund information

Size of contribution to the Compensation Fund for harm:
▒▒▒ ₽
Harm compensation responsibility level:
▒▒▒▒▒
Size of contribution to the Compensation Fund for securing contractual obligations:
▒▒▒▒▒
Securing contractual obligations responsibility level:
▒▒▒▒▒
Compensation fund collection:
▒▒▒▒▒

Information on eligibility

Date of decision on admission to membership:
▒▒▒▒▒
Membership decision number:
▒▒▒▒▒
Date of entry into force of the decision on admission to membership:
▒▒▒▒▒
Availability of rights to perform work on capital construction objects:
▒▒▒
Availability of rights to perform work on especially dangerous, technically complex and unique capital construction objects:
▒▒▒
Availability of rights to perform work on nuclear facilities:
▒▒▒
Status of the right to perform work under a construction contract:
▒▒▒▒▒
Ensuring contractual obligations:
▒▒▒

Insurance information (5)
Contract number: ▒▒▒▒▒
Subject matter of insurance: ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Sum insured: ▒▒▒ ₽
Contract start date: ▒▒.▒▒.2015
Contract expiration date: ▒▒.▒▒.2016
License: ▒ ▒▒▒▒▒▒
Contract number: ▒▒▒▒▒
Subject matter of insurance: ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Sum insured: ▒▒▒ ₽
Contract start date: ▒▒.▒▒.2014
Contract expiration date: ▒▒.▒▒.2015
License: ▒ ▒▒▒▒▒▒
Contract number: ▒▒▒▒▒
Subject matter of insurance: ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Sum insured: ▒▒▒ ₽
Contract start date: ▒▒.▒▒.2013
Contract expiration date: ▒▒.▒▒.2014
License: ▒ ▒ ▒▒▒▒ ▒▒
Contract number: ▒▒▒▒▒
Subject matter of insurance: ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Sum insured: ▒▒▒ ₽
Contract start date: ▒▒.▒▒.2012
Contract expiration date: ▒▒.▒▒.2013
License: ▒ ▒ ▒▒▒▒ ▒▒
Contract number: ▒▒▒▒▒
Subject matter of insurance: ▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Sum insured: ▒▒▒ ₽
Contract start date: ▒▒.▒▒.2010
Contract expiration date: ▒▒.▒▒.2011
License: ▒ ▒ ▒▒▒▒ ▒▒

Information about inspections (14)
SRO member verification type: ▒▒▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2017
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2016
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2016
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2015
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2015
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2015
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2014
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2014
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2014
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2014
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2013
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2013
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2012
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒
SRO member verification type: ▒▒▒▒▒▒▒
SRO member verification date: ▒▒.▒▒.2011
SRO member verification result: ▒▒▒▒▒▒▒▒▒▒ ▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒▒▒
Disciplinary action: ▒▒▒▒ ▒▒▒ ▒▒▒▒▒▒▒

Data sources SRO affiliation information is collected from public sources.

Accurate binding to a company can be created only if the information source contains its TIN and OGRN values. If identification details are not specified, the binding is created by using linguistic algorithms. Although these algorithms are being constantly improved, some information may be absent.

If you have noticed an error or lack of information, please let us know about it. Let's improve Seldon.Basis together!

Data sources SRO affiliation information is collected from public sources.

Accurate binding to a company can be created only if the information source contains its TIN and OGRN values. If identification details are not specified, the binding is created by using linguistic algorithms. Although these algorithms are being constantly improved, some information may be absent.

If you have noticed an error or lack of information, please let us know about it. Let's improve Seldon.Basis together!