BIZTRAC BETA
Uoppgitt

EIKELAND BYGG OG EIENDOM AS

Org. no. 922096546 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 78,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

EIKELAND BYGG OG EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 922096546. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 78,000
Est. value
NOK 91,000

Financial health · 2025

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

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

Who owns EIKELAND BYGG OG EIENDOM AS?

BJØRNAR EIKELAND
EIKELAND BYGG OG EIENDOM AS
NOK 0 rev. · NOK −5,000 profit

EIKELAND BYGG OG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIKELAND BYGG OG EIENDOM AS own?

EIKELAND BYGG OG EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIKELAND BYGG OG EIENDOM AS

Who owns EIKELAND BYGG OG EIENDOM AS?

BJØRNAR EIKELAND is the largest registered owner, with 100.0%.

What is the revenue of EIKELAND BYGG OG EIENDOM AS?

EIKELAND BYGG OG EIENDOM AS had revenue of NOK 0 in 2025.

Where is EIKELAND BYGG OG EIENDOM AS based?

EIKELAND BYGG OG EIENDOM AS has its business address in Tertnes.

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.