biztrac. BETA
COMPANY REGISTER PROFILE
924201312 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

INNLANDSPORTEN EIENDOM 2 AS

Org. no. 924201312 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 9.0m
Operating profit NOK 5.5m
Equity NOK 31.3m
Incorporated 2019
Share capital NOK 360,000

INNLANDSPORTEN EIENDOM 2 AS is registered as a limited company in Oslo, Oslo with organisation number 924201312. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 360,000, divided into 1200 shares. The company's stated purpose is: “Å eie og drifte fast eiendom, eierskap i selskaper som driver tilsvarende virksomhet samt annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.0m in revenue and NOK 5.5m in operating profit.

Key figures · 2025

Revenue
NOK 9.0m
▼ −7 %
Operating profit
NOK 5.5m
▼ −0 %
Equity
NOK 31.3m
▲ +2 %
Est. value
NOK 30.8m

Financial health · 2025

Liquidity
0.41
Not satisfactory
Current assets ÷ current liabilities
Profitability
6.9%
Satisfactory
Return on total assets
Solidity
40.7%
Very good
Equity as a share of total capital

Who owns INNLANDSPORTEN EIENDOM 2 AS?

INNLANDSPORTEN EIENDOM 2 AS
NOK 9.0m rev. · NOK 5.5m profit

INNLANDSPORTEN EIENDOM 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INNLANDSPORTEN EIENDOM 2 AS

Who owns INNLANDSPORTEN EIENDOM 2 AS?

RAGDE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of INNLANDSPORTEN EIENDOM 2 AS?

INNLANDSPORTEN EIENDOM 2 AS had revenue of NOK 9.0m in 2025.

Where is INNLANDSPORTEN EIENDOM 2 AS based?

INNLANDSPORTEN EIENDOM 2 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.