BIZTRAC BETA
Construction of residential and non-residential buildings

ERTEKA AS

Org. no. 915282237 Limited company (AS) Asker Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 73,000
Operating profit NOK 52,000
Equity NOK 243,000
Incorporated 2015
Share capital NOK 30,000

ERTEKA AS is registered as a limited company in Asker, Akershus with organisation number 915282237. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Oppføring av bygninger, utvikling og salg av fast eiendom og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 73,000 in revenue and NOK 52,000 in operating profit.

Key figures · 2024

Revenue
NOK 73,000
Operating profit
NOK 52,000
Equity
NOK 243,000
Est. value
NOK 255,000

Financial health · 2024

Liquidity
0.27
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.7%
Weak
Equity as a share of total capital

Who owns ERTEKA AS?

SAULIUS BALSEVICIUS
ERTEKA AS
NOK 73,000 rev. · NOK 52,000 profit

ERTEKA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERTEKA AS own?

ERTEKA AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

ERTEKA AS er morselskap for 1 datterselskap:

Frequently asked questions about ERTEKA AS

Who owns ERTEKA AS?

SAULIUS BALSEVICIUS is the largest registered owner, with 100.0%.

What is the revenue of ERTEKA AS?

ERTEKA AS had revenue of NOK 73,000 in 2024.

Who is the general manager of ERTEKA AS?

Saulius Balsevicius is registered as general manager of ERTEKA AS.

Where is ERTEKA AS based?

ERTEKA AS has its business address in Asker.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.