BIZTRAC BETA
Rental and operating of own or leased real estate

ALFASET 1. INDUSTRIVEI 5 AS

Org. no. 839105312 Limited company (AS) Oslo Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 5.4m
Operating profit NOK 4.7m
Equity NOK 21.2m
Incorporated 1986
Share capital NOK 100,000

ALFASET 1. INDUSTRIVEI 5 AS is registered as a limited company in Oslo, Oslo with organisation number 839105312. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1986. Registered share capital is NOK 100,000, divided into 10 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 2024 financial year, show NOK 5.4m in revenue and NOK 4.7m in operating profit.

Key figures · 2024

Revenue
NOK 5.4m
Operating profit
NOK 4.7m
Equity
NOK 21.2m
Est. value
NOK 24.9m

Financial health · 2024

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

Who owns ALFASET 1. INDUSTRIVEI 5 AS?

EIENDOMSSPAR AS
ALFASET 1. INDUSTRIVEI 5 AS
NOK 5.4m rev. · NOK 4.7m profit

ALFASET 1. INDUSTRIVEI 5 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALFASET 1. INDUSTRIVEI 5 AS

Who owns ALFASET 1. INDUSTRIVEI 5 AS?

EIENDOMSSPAR AS is the largest registered owner, with 100.0%.

What is the revenue of ALFASET 1. INDUSTRIVEI 5 AS?

ALFASET 1. INDUSTRIVEI 5 AS had revenue of NOK 5.4m in 2024.

Who is the general manager of ALFASET 1. INDUSTRIVEI 5 AS?

Børre Vegard Skjolden is registered as general manager of ALFASET 1. INDUSTRIVEI 5 AS.

Where is ALFASET 1. INDUSTRIVEI 5 AS based?

ALFASET 1. INDUSTRIVEI 5 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.