BIZTRAC BETA
Rental and operating of own or leased real estate

INDUSTRIVEIEN 26 AS

Org. no. 921675747 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 13.3m
Operating profit NOK 2.4m
Equity NOK 102.5m
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

INDUSTRIVEIEN 26 AS is registered as a limited company in Oslo, Oslo with organisation number 921675747. 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 100,000, divided into 100 shares. The company's stated purpose is: “Å eie og/eller drive fast eiendom og investere i andre selskaper, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.3m in revenue and NOK 2.4m in operating profit.

Key figures · 2024

Revenue
NOK 13.3m
Operating profit
NOK 2.4m
Equity
NOK 102.5m
Est. value
NOK 78.1m

Financial health · 2024

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

Who owns INDUSTRIVEIEN 26 AS?

PEF HOLDING AS
INDUSTRIVEIEN 26 AS
NOK 13.3m rev. · NOK 2.4m profit

INDUSTRIVEIEN 26 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

INDUSTRIVEIEN 26 AS er morselskap for 42 datterselskaper:

Frequently asked questions about INDUSTRIVEIEN 26 AS

Who owns INDUSTRIVEIEN 26 AS?

PEF HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of INDUSTRIVEIEN 26 AS?

INDUSTRIVEIEN 26 AS had revenue of NOK 13.3m in 2024.

Where is INDUSTRIVEIEN 26 AS based?

INDUSTRIVEIEN 26 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.