biztrac. BETA
COMPANY REGISTER PROFILE
921399243 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

ØSTRE AKER VEI 206 AS

Org. no. 921399243 Limited company (AS) Oslo Incorporated 1977 Active
Ownership graph ↗
Revenue 2025 NOK 14.8m
Operating profit NOK 6.6m
Equity NOK 22.9m
Incorporated 1977
Share capital NOK 5.5m

ØSTRE AKER VEI 206 AS is registered as a limited company in Oslo, Oslo with organisation number 921399243. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1977. Registered share capital is NOK 5.5m, divided into 5000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.8m in revenue and NOK 6.6m in operating profit.

Former names: STANSEVEIEN 2 AS

Key figures · 2025

Revenue
NOK 14.8m
▲ +34 %
Operating profit
NOK 6.6m
▲ +8 %
Equity
NOK 22.9m
▲ +309 %
Est. value
NOK 32.3m

Financial health · 2025

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
12.8%
Good
Return on total assets
Solidity
84.4%
Very good
Equity as a share of total capital

Who owns ØSTRE AKER VEI 206 AS?

ØSTRE AKER VEI 206 AS
NOK 14.8m rev. · NOK 6.6m profit

ØSTRE AKER VEI 206 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ØSTRE AKER VEI 206 AS er morselskap for 1 datterselskap:

Frequently asked questions about ØSTRE AKER VEI 206 AS

Who owns ØSTRE AKER VEI 206 AS?

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

What is the revenue of ØSTRE AKER VEI 206 AS?

ØSTRE AKER VEI 206 AS had revenue of NOK 14.8m in 2025.

Where is ØSTRE AKER VEI 206 AS based?

ØSTRE AKER VEI 206 AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.