BIZTRAC BETA
Rental and operating of own or leased real estate

RAUFOSS INDUSTRIPARK II AS

Org. no. 914219027 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −119,000
Equity NOK 1.2m
Incorporated 2014
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−119k kr).

RAUFOSS INDUSTRIPARK II AS is registered as a limited company in Oslo, Oslo with organisation number 914219027. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Eie 0,1 % av andelene i Raufoss Næringspark ANS som eier eiendommene gnr. 10, bnr. 21, gnr. 12, bnr. 484, gnr. 13, bnr. 1, 120, 503, 569, 570, 641, 665, 666 og 667 i Vestre Toten kommune og gnr. 44, bnr 2 i Gjøvik kommune, og gjennom dette eierskapet drifte eiendommene, samt hva som hermed står i forbindelse, herunder investeringer i eiendommer som ligger i nærheten av forannevnte eiendommer og andre selskaper.”.

Key figures · 2024

Operating profit
NOK −119,000
Equity
NOK 1.2m
Est. value
NOK 858,000

Financial health · 2024

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

Who owns RAUFOSS INDUSTRIPARK II AS?

RAUFOSS INDUSTRIPARK HOLDING AS
RAUFOSS INDUSTRIPARK II AS
· NOK −119,000 profit

RAUFOSS INDUSTRIPARK II AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAUFOSS INDUSTRIPARK II AS

Who owns RAUFOSS INDUSTRIPARK II AS?

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

Where is RAUFOSS INDUSTRIPARK II AS based?

RAUFOSS INDUSTRIPARK II 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.