BIZTRAC BETA
Other technical consultancy

EKRHEIM TRE OG KONSTRUKSJON AS

Org. no. 925324809 Limited company (AS) Sveio Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 14,000
Operating profit NOK −35,000
Equity NOK 51,000
Incorporated 2020
Share capital NOK 140,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−35k kr).

EKRHEIM TRE OG KONSTRUKSJON AS is registered as a limited company in Sveio, Vestland with organisation number 925324809. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 140,000, divided into 1000 shares. The company's stated purpose is: “Håndverkstjenester og prosjektering, samt oppføring og restaurering av bygg.”. The most recent filed accounts, for the 2024 financial year, show NOK 14,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2024

Revenue
NOK 14,000
Operating profit
NOK −35,000
Equity
NOK 51,000
Est. value
NOK 39,000

Financial health · 2024

Liquidity
2.40
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
79.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EKRHEIM TRE OG KONSTRUKSJON AS?

ANDREAS EKRHEIM
EKRHEIM TRE OG KONSTRUKSJON AS
NOK 14,000 rev. · NOK −35,000 profit

EKRHEIM TRE OG KONSTRUKSJON AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about EKRHEIM TRE OG KONSTRUKSJON AS

Who owns EKRHEIM TRE OG KONSTRUKSJON AS?

ANDREAS EKRHEIM is the largest registered owner, with 80.0%.

What is the revenue of EKRHEIM TRE OG KONSTRUKSJON AS?

EKRHEIM TRE OG KONSTRUKSJON AS had revenue of NOK 14,000 in 2024.

Where is EKRHEIM TRE OG KONSTRUKSJON AS based?

EKRHEIM TRE OG KONSTRUKSJON AS has its business address in Auklandshamn.

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.