BIZTRAC BETA
Rental and operating of own or leased real estate

INDUSTRIVEIEN 35 AS

Org. no. 993420875 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 923,000
Equity NOK 4.6m
Incorporated 2008
Share capital NOK 344,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 35 AS is registered as a limited company in Oslo, Oslo with organisation number 993420875. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 344,000, divided into 34350 shares. The company's stated purpose is: “Erverv, utvikling og utleie av fast eiendom samt det som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 923,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 923,000
Equity
NOK 4.6m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns INDUSTRIVEIEN 35 AS?

FABRITIUS GRUPPEN AS
INDUSTRIVEIEN 35 AS
NOK 1.0m rev. · NOK 923,000 profit

INDUSTRIVEIEN 35 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

INDUSTRIVEIEN 35 AS er morselskap for 33 datterselskaper:

Frequently asked questions about INDUSTRIVEIEN 35 AS

Who owns INDUSTRIVEIEN 35 AS?

FABRITIUS GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of INDUSTRIVEIEN 35 AS?

INDUSTRIVEIEN 35 AS had revenue of NOK 1.0m in 2024.

Where is INDUSTRIVEIEN 35 AS based?

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