BIZTRAC BETA
Other captive investment companies

ROSLAND INVEST II AS

Org. no. 997850262 Limited company (AS) Drangedal Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −57,000
Equity NOK 6.1m
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−57k kr).

ROSLAND INVEST II AS is registered as a limited company in Drangedal, Telemark with organisation number 997850262. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, selskapsandeler og annen investeringsvirksomhet. Selskapet kan delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −57,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −57,000
Equity
NOK 6.1m
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns ROSLAND INVEST II AS?

JAN INGE ROSLAND
ROSLAND INVEST II AS
NOK 0 rev. · NOK −57,000 profit

ROSLAND INVEST II AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROSLAND INVEST II AS own?

ROSLAND INVEST II AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ROSLAND INVEST II AS

Who owns ROSLAND INVEST II AS?

JAN INGE ROSLAND is the largest registered owner, with 100.0%.

What is the revenue of ROSLAND INVEST II AS?

ROSLAND INVEST II AS had revenue of NOK 0 in 2025.

Where is ROSLAND INVEST II AS based?

ROSLAND INVEST II AS has its business address in Neslandsvatn.

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.