BIZTRAC BETA
Rental and operating of own or leased real estate

STRØMSVEIEN 223C-225B AS

Org. no. 830776052 Limited company (AS) Oslo Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 925,000
Equity NOK 756,000
Incorporated 1987
Share capital NOK 500,000

STRØMSVEIEN 223C-225B AS is registered as a limited company in Oslo, Oslo with organisation number 830776052. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 500,000. The company's stated purpose is: “Eie og utvikle fast eiendom samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 925,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 925,000
Equity
NOK 756,000
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns STRØMSVEIEN 223C-225B AS?

ALNA PARK AS
STRØMSVEIEN 223C-225B AS
NOK 1.1m rev. · NOK 925,000 profit

STRØMSVEIEN 223C-225B AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STRØMSVEIEN 223C-225B AS er morselskap for 48 datterselskaper:

Frequently asked questions about STRØMSVEIEN 223C-225B AS

Who owns STRØMSVEIEN 223C-225B AS?

ALNA PARK AS is the largest registered owner, with 100.0%.

What is the revenue of STRØMSVEIEN 223C-225B AS?

STRØMSVEIEN 223C-225B AS had revenue of NOK 1.1m in 2024.

Who is the general manager of STRØMSVEIEN 223C-225B AS?

Børre Vegard Skjolden is registered as general manager of STRØMSVEIEN 223C-225B AS.

Where is STRØMSVEIEN 223C-225B AS based?

STRØMSVEIEN 223C-225B 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 15.06.2026.

Report a problem

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