BIZTRAC BETA
Rental and operating of own or leased real estate

RJUKAN NÆRINGSEIENDOM AS

Org. no. 991706062 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 942,000
Operating profit NOK 290,000
Equity NOK 1.7m
Incorporated 2007
Share capital NOK 800,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RJUKAN NÆRINGSEIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 991706062. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 800,000, divided into 80000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 942,000 in revenue and NOK 290,000 in operating profit.

Key figures · 2024

Revenue
NOK 942,000
Operating profit
NOK 290,000
Equity
NOK 1.7m
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns RJUKAN NÆRINGSEIENDOM AS?

LØVENSKIOLD EIENDOM AS
RJUKAN NÆRINGSEIENDOM AS
NOK 942,000 rev. · NOK 290,000 profit

RJUKAN NÆRINGSEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RJUKAN NÆRINGSEIENDOM AS

Who owns RJUKAN NÆRINGSEIENDOM AS?

LØVENSKIOLD EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of RJUKAN NÆRINGSEIENDOM AS?

RJUKAN NÆRINGSEIENDOM AS had revenue of NOK 942,000 in 2024.

Where is RJUKAN NÆRINGSEIENDOM AS based?

RJUKAN NÆRINGSEIENDOM 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.