BIZTRAC BETA
Rental and operating of own or leased real estate

BØLEVEIEN EIENDOM AS

Org. no. 992756640 Limited company (AS) Skien Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 582,000
Equity NOK 3.1m
Incorporated 2008
Share capital NOK 1.2m

BØLEVEIEN EIENDOM AS is registered as a limited company in Skien, Telemark with organisation number 992756640. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 1.2m, divided into 2001 shares. The company's stated purpose is: “Investering og utvikling av fast eiendom, deltakelse i samme, eie og forvalte verdipapirer og andre formuesgjenstander og annen økonomisk virksomhet i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 582,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 582,000
Equity
NOK 3.1m
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns BØLEVEIEN EIENDOM AS?

WITH HOLDING AS
BØLEVEIEN EIENDOM AS
NOK 1.0m rev. · NOK 582,000 profit

BØLEVEIEN EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BØLEVEIEN EIENDOM AS

Who owns BØLEVEIEN EIENDOM AS?

WITH HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of BØLEVEIEN EIENDOM AS?

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

Who is the general manager of BØLEVEIEN EIENDOM AS?

Joakim Nielsen With is registered as general manager of BØLEVEIEN EIENDOM AS.

Where is BØLEVEIEN EIENDOM AS based?

BØLEVEIEN EIENDOM AS has its business address in Skien.

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.