BIZTRAC BETA
Buying and selling of own real estate

INDUSTRIVEIEN 4 C AS

Org. no. 923562362 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 8.2m
Operating profit NOK 3.0m
Equity NOK 19.9m
Incorporated 2019
Share capital NOK 60,000

INDUSTRIVEIEN 4 C AS is registered as a limited company in Oslo, Oslo with organisation number 923562362. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 1 shares. The company's stated purpose is: “Kjøp, salg, utvikling, utleie og drift av næringseiendommer og det som naturlig hører inn under dette, herunder deltakelse i andre selskaper med lignende formål..”. The most recent filed accounts, for the 2025 financial year, show NOK 8.2m in revenue and NOK 3.0m in operating profit.

Key figures · 2025

Revenue
NOK 8.2m
Operating profit
NOK 3.0m
Equity
NOK 19.9m
Est. value
NOK 22.4m

Financial health · 2025

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

Who owns INDUSTRIVEIEN 4 C AS?

SKEDSMOKORSET EIENDOMSUTVIKLING AS
INDUSTRIVEIEN 4 C AS
NOK 8.2m rev. · NOK 3.0m profit

INDUSTRIVEIEN 4 C AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INDUSTRIVEIEN 4 C AS

Who owns INDUSTRIVEIEN 4 C AS?

SKEDSMOKORSET EIENDOMSUTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of INDUSTRIVEIEN 4 C AS?

INDUSTRIVEIEN 4 C AS had revenue of NOK 8.2m in 2025.

Who is the general manager of INDUSTRIVEIEN 4 C AS?

Dag William Bastiansen is registered as general manager of INDUSTRIVEIEN 4 C AS.

Where is INDUSTRIVEIEN 4 C AS based?

INDUSTRIVEIEN 4 C 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.