BIZTRAC BETA
Development of building projects

LØKENÅSENTUNET AS

Org. no. 922675953 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 263,000
Operating profit NOK −102,000
Equity NOK −985,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−985k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−102k kr).

LØKENÅSENTUNET AS is registered as a limited company in Oslo, Oslo with organisation number 922675953. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eiendomsutvikling”. The most recent filed accounts, for the 2025 financial year, show NOK 263,000 in revenue and NOK −102,000 in operating profit.

Key figures · 2025

Revenue
NOK 263,000
Operating profit
NOK −102,000
Equity
NOK −985,000

Financial health · 2025

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

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

Who owns LØKENÅSENTUNET AS?

HUSI AS
LØKENÅSENTUNET AS
NOK 263,000 rev. · NOK −102,000 profit

LØKENÅSENTUNET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØKENÅSENTUNET AS

Who owns LØKENÅSENTUNET AS?

HUSI AS is the largest registered owner, with 50.0%.

What is the revenue of LØKENÅSENTUNET AS?

LØKENÅSENTUNET AS had revenue of NOK 263,000 in 2025.

Who is the general manager of LØKENÅSENTUNET AS?

Jon Anders Rønaas is registered as general manager of LØKENÅSENTUNET AS.

Where is LØKENÅSENTUNET AS based?

LØKENÅSENTUNET 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.