BIZTRAC BETA
Rental and operating of own or leased real estate

HOLMENVEIEN 11 AS

Org. no. 994535811 Limited company (AS) Oslo Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 976,000
Operating profit NOK 529,000
Equity NOK 9.6m
Incorporated 2009
Share capital NOK 1.0m

Signals

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

HOLMENVEIEN 11 AS is registered as a limited company in Oslo, Oslo with organisation number 994535811. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering i fast eiendom, herunder utleie, drift kjøp og salg, samt investering i aksjer og andre verdipapirer, herunder aktiv deltagelse i andre selskaper. I tillegg kommer annen nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 976,000 in revenue and NOK 529,000 in operating profit.

Key figures · 2024

Revenue
NOK 976,000
Operating profit
NOK 529,000
Equity
NOK 9.6m
Est. value
NOK 8.1m

Financial health · 2024

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

Who owns HOLMENVEIEN 11 AS?

ULNICA AS
HOLMENVEIEN 11 AS
NOK 976,000 rev. · NOK 529,000 profit

HOLMENVEIEN 11 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOLMENVEIEN 11 AS

Who owns HOLMENVEIEN 11 AS?

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

What is the revenue of HOLMENVEIEN 11 AS?

HOLMENVEIEN 11 AS had revenue of NOK 976,000 in 2024.

Where is HOLMENVEIEN 11 AS based?

HOLMENVEIEN 11 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.