BIZTRAC BETA
Development of building projects

BJERLAND EIENDOM AS

Org. no. 914613272 Limited company (AS) Vennesla Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 419,000
Equity NOK 150,000
Incorporated 2014
Share capital NOK 150,000

BJERLAND EIENDOM AS is registered as a limited company in Vennesla, Agder with organisation number 914613272. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 150,000, divided into 150000 shares. The company's stated purpose is: “Eiendomsutvikling, kjøp, salg, utleie og drift av eiendom, investeringer i aksjer, andeler og andre finans- og realobjekter, samt dertil hørende virksomhet, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 419,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 419,000
Equity
NOK 150,000
Est. value
NOK 909,000

Financial health · 2025

Liquidity
1.70
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.7%
Not satisfactory
Equity as a share of total capital

Who owns BJERLAND EIENDOM AS?

BJERLAND HOLDING AS
BJERLAND EIENDOM AS
NOK 3.0m rev. · NOK 419,000 profit

BJERLAND EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BJERLAND EIENDOM AS

Who owns BJERLAND EIENDOM AS?

BJERLAND HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BJERLAND EIENDOM AS?

BJERLAND EIENDOM AS had revenue of NOK 3.0m in 2025.

Who is the general manager of BJERLAND EIENDOM AS?

Sigmund Bjerland is registered as general manager of BJERLAND EIENDOM AS.

Where is BJERLAND EIENDOM AS based?

BJERLAND EIENDOM AS has its business address in Øvrebø.

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.