BIZTRAC BETA
Rental and operating of own or leased real estate

RISLØKKFARET 6 AS

Org. no. 922097097 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −1.7m
Equity NOK 135,000
Incorporated 2019
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,7 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RISLØKKFARET 6 AS is registered as a limited company in Asker, Akershus with organisation number 922097097. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, investering og utvikling av fast eiendom. Oppføring av nybygg. Samt, deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −1.7m in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −1.7m
Equity
NOK 135,000
Est. value
NOK 123,000

Financial health · 2024

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.0%
Not satisfactory
Equity as a share of total capital

Who owns RISLØKKFARET 6 AS?

TOMTEPROSJEKT AS
RISLØKKFARET 6 AS
NOK 0 rev. · NOK −1.7m profit

RISLØKKFARET 6 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RISLØKKFARET 6 AS

Who owns RISLØKKFARET 6 AS?

TOMTEPROSJEKT AS is the largest registered owner, with 100.0%.

What is the revenue of RISLØKKFARET 6 AS?

RISLØKKFARET 6 AS had revenue of NOK 0 in 2024.

Where is RISLØKKFARET 6 AS based?

RISLØKKFARET 6 AS has its business address in Nesøya.

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.