BIZTRAC BETA
Other captive investment companies

ROBIN HOLDING AS

Org. no. 912830322 Limited company (AS) Bergen Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 982,000
Incorporated 2013
Share capital NOK 50,000

Signals

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

ROBIN HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 912830322. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Investeringer i andre aksjeselskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 982,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns ROBIN HOLDING AS?

ROAR DANIELSEN NYLUND
ROBIN HOLDING AS
NOK 0 rev. · NOK −12,000 profit

ROBIN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROBIN HOLDING AS own?

ROBIN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ROBIN HOLDING AS

Who owns ROBIN HOLDING AS?

ROAR DANIELSEN NYLUND is the largest registered owner, with 100.0%.

What is the revenue of ROBIN HOLDING AS?

ROBIN HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of ROBIN HOLDING AS?

Roar Danielsen Nylund is registered as general manager of ROBIN HOLDING AS.

Where is ROBIN HOLDING AS based?

ROBIN HOLDING AS has its business address in Rådal.

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.