BIZTRAC BETA
Buying and selling of own real estate

ROLIGHETEN HOLDING AS

Org. no. 933370356 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −226,000
Equity NOK −312,000
Incorporated 2024
Share capital NOK 30,000

Signals

4 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−312k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−226k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-11 Adresseendring registrert 2026-04-11.

ROLIGHETEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 933370356. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikling og salg av egen fast eiendom ellers.”.

Key figures · 2024

Operating profit
NOK −226,000
Equity
NOK −312,000

Financial health · 2024

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ROLIGHETEN HOLDING AS?

G. CHRISTENSEN EIENDOM AS
ROLIGHETEN HOLDING AS
· NOK −226,000 profit

ROLIGHETEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROLIGHETEN HOLDING AS own?

ROLIGHETEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ROLIGHETEN HOLDING AS

Who owns ROLIGHETEN HOLDING AS?

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

Where is ROLIGHETEN HOLDING AS based?

ROLIGHETEN HOLDING 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 15.06.2026.

Report a problem

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