BIZTRAC BETA
Construction of residential and non-residential buildings

KARSTEN EIKELAND BYGG AS

Org. no. 891840942 Limited company (AS) Bergen Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK −151,000
Equity NOK 146,000
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−151k kr).

KARSTEN EIKELAND BYGG AS is registered as a limited company in Bergen, Vestland with organisation number 891840942. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og oppføring av fast eiendom. Herav spesialisering i betong og entreprenørvirksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK −151,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK −151,000
Equity
NOK 146,000
Est. value
NOK 848,000

Financial health · 2025

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.8%
Good
Equity as a share of total capital

Who owns KARSTEN EIKELAND BYGG AS?

KARSTEN EIKELAND
KARSTEN EIKELAND BYGG AS
NOK 2.3m rev. · NOK −151,000 profit

KARSTEN EIKELAND BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KARSTEN EIKELAND BYGG AS

Who owns KARSTEN EIKELAND BYGG AS?

KARSTEN EIKELAND is the largest registered owner, with 100.0%.

What is the revenue of KARSTEN EIKELAND BYGG AS?

KARSTEN EIKELAND BYGG AS had revenue of NOK 2.3m in 2025.

Where is KARSTEN EIKELAND BYGG AS based?

KARSTEN EIKELAND BYGG AS has its business address in Flaktveit.

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.