BIZTRAC BETA
COMPANY REGISTER PROFILE
925568392 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

ROLG INVEST AS

Org. no. 925568392 Limited company (AS) Nesodden Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 1.6m
Incorporated 2020
Share capital NOK 30,000

Signals

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

ROLG INVEST AS is registered as a limited company in Nesodden, Akershus with organisation number 925568392. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investering i aksjer og andre eiendeler i andre selskaper og foretak, samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
▼ −3 %
Equity
NOK 1.6m
▼ −0 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
73.0%
Very good
Equity as a share of total capital

Who owns ROLG INVEST AS?

ROLG INVEST AS
NOK 0 rev. · NOK −5,000 profit

ROLG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROLG INVEST AS own?

ROLG INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ROLG INVEST AS

Who owns ROLG INVEST AS?

ROLF-HARALD GRIMSTAD is the largest registered owner, with 100.0%.

What is the revenue of ROLG INVEST AS?

ROLG INVEST AS had revenue of NOK 0 in 2025.

Where is ROLG INVEST AS based?

ROLG INVEST AS has its business address in Fjellstrand.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

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