biztrac. BETA
COMPANY REGISTER PROFILE
929555058 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

ROLANDSKROKEN INVEST AS

Org. no. 929555058 Limited company (AS) Larvik Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −19,000
Equity NOK 1.5m
Incorporated 2022
Share capital NOK 30,000

Signals

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

ROLANDSKROKEN INVEST AS is registered as a limited company in Larvik, Vestfold with organisation number 929555058. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering aksjer og andeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −19,000
▲ +4 %
Equity
NOK 1.5m
▲ +602 %
Est. value
NOK 9.1m

Financial health · 2025

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

Who owns ROLANDSKROKEN INVEST AS?

ROLANDSKROKEN INVEST AS
NOK 0 rev. · NOK −19,000 profit

ROLANDSKROKEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROLANDSKROKEN INVEST AS

Who owns ROLANDSKROKEN INVEST AS?

Hilde Synnøve Nordahl Olsen is the largest registered owner, with 100.0%.

What is the revenue of ROLANDSKROKEN INVEST AS?

ROLANDSKROKEN INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of ROLANDSKROKEN INVEST AS?

Hilde Synnøve Nordahl Olsen is registered as general manager of ROLANDSKROKEN INVEST AS.

Where is ROLANDSKROKEN INVEST AS based?

ROLANDSKROKEN INVEST AS has its business address in Helgeroa.

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.