BIZTRAC BETA
Rental and operating of own or leased real estate

BØLEVEGEN 152 AS

Org. no. 921269951 Limited company (AS) Skien Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 882,000
Operating profit NOK 650,000
Equity NOK 1.1m
Incorporated 2018
Share capital NOK 30,000

BØLEVEGEN 152 AS is registered as a limited company in Skien, Telemark with organisation number 921269951. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleie av eiendom og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 882,000 in revenue and NOK 650,000 in operating profit.

Key figures · 2025

Revenue
NOK 882,000
Operating profit
NOK 650,000
Equity
NOK 1.1m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns BØLEVEGEN 152 AS?

TANGENS EIENDOM AS
BØLEVEGEN 152 AS
NOK 882,000 rev. · NOK 650,000 profit

BØLEVEGEN 152 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BØLEVEGEN 152 AS

Who owns BØLEVEGEN 152 AS?

TANGENS EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BØLEVEGEN 152 AS?

BØLEVEGEN 152 AS had revenue of NOK 882,000 in 2025.

Who is the general manager of BØLEVEGEN 152 AS?

Geir Ståle Tangen is registered as general manager of BØLEVEGEN 152 AS.

Where is BØLEVEGEN 152 AS based?

BØLEVEGEN 152 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.