BIZTRAC BETA
Rental and operating of own or leased real estate

SLETTA EIENDOM II AS

Org. no. 920810837 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 1.6m
Equity NOK 4.1m
Incorporated 2018
Share capital NOK 330,000

Signals

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

SLETTA EIENDOM II AS is registered as a limited company in Oslo, Oslo with organisation number 920810837. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 330,000, divided into 300 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 2.0m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 1.6m
Equity
NOK 4.1m
Est. value
NOK 5.9m

Financial health · 2024

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

Who owns SLETTA EIENDOM II AS?

NORDISK RENTING AS
SLETTA EIENDOM II AS
NOK 2.0m rev. · NOK 1.6m profit

SLETTA EIENDOM II AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SLETTA EIENDOM II AS er morselskap for 1 datterselskap:

Frequently asked questions about SLETTA EIENDOM II AS

Who owns SLETTA EIENDOM II AS?

NORDISK RENTING AS is the largest registered owner, with 100.0%.

What is the revenue of SLETTA EIENDOM II AS?

SLETTA EIENDOM II AS had revenue of NOK 2.0m in 2024.

Where is SLETTA EIENDOM II AS based?

SLETTA EIENDOM II 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.