BIZTRAC BETA
Rental and operating of own or leased real estate

BØ EIENDOM AS

Org. no. 980680789 Limited company (AS) Midt-Telemark Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 634,000
Equity NOK 4.8m
Incorporated 1999
Share capital NOK 500,000

BØ EIENDOM AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 980680789. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Forvaltning og utleie av fast eiendom og annen virksomhet som naturlig faller inn under dette ved aksjekjøp eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 634,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 634,000
Equity
NOK 4.8m
Est. value
NOK 4.3m

Financial health · 2024

Liquidity
66.92
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.7%
Good
Equity as a share of total capital

Who owns BØ EIENDOM AS?

HANS AARAK
BØ EIENDOM AS
NOK 1.5m rev. · NOK 634,000 profit

BØ EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BØ EIENDOM AS own?

BØ EIENDOM AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about BØ EIENDOM AS

Who owns BØ EIENDOM AS?

HANS AARAK is the largest registered owner, with 51.0%.

What is the revenue of BØ EIENDOM AS?

BØ EIENDOM AS had revenue of NOK 1.5m in 2024.

Who is the general manager of BØ EIENDOM AS?

Hans Aarak is registered as general manager of BØ EIENDOM AS.

Where is BØ EIENDOM AS based?

BØ EIENDOM AS has its business address in Bø I Telemark.

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.