biztrac. BETA
COMPANY REGISTER PROFILE
933837912 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

AS HOLENLØKKEN III

Org. no. 933837912 Limited company (AS) Oslo Incorporated 1950 Active
Revenue 2025 NOK 144,000
Operating profit NOK 86,000
Equity NOK 107,000
Incorporated 1950
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-07-21 Adresseendring registrert 2026-07-21.

AS HOLENLØKKEN III is registered as a limited company in Oslo, Oslo with organisation number 933837912. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1950. Registered share capital is NOK 100,000, divided into 12 shares. The company's stated purpose is: “Innkjøp eller feste av tomt til oppføring av gar- asjeanlegg og drift av dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 144,000 in revenue and NOK 86,000 in operating profit.

Key figures · 2025

Revenue
NOK 144,000
▲ +200 %
Operating profit
NOK 86,000
▲ +1143 %
Equity
NOK 107,000
▲ +470 %
Est. value
NOK 219,000

Financial health · 2025

Liquidity
1.61
Good
Current assets ÷ current liabilities
Profitability
31.4%
Very good
Return on total assets
Solidity
38.7%
Good
Equity as a share of total capital

Who owns AS HOLENLØKKEN III?

AS HOLENLØKKEN III has 11 registered shareholders:

All shareholders and roles →

Which companies does AS HOLENLØKKEN III own?

AS HOLENLØKKEN III holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AS HOLENLØKKEN III

Who owns AS HOLENLØKKEN III?

Herman Steen is the largest registered owner, with 16.7%.

What is the revenue of AS HOLENLØKKEN III?

AS HOLENLØKKEN III had revenue of NOK 144,000 in 2025.

Where is AS HOLENLØKKEN III based?

AS HOLENLØKKEN III has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.