BIZTRAC BETA
Uoppgitt

HØLABRØTIN INVEST AS

Org. no. 930791407 Limited company (AS) Hole Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 67,000
Operating profit NOK 19,000
Equity NOK 81,000
Incorporated 2023
Share capital NOK 30,000

HØLABRØTIN INVEST AS is registered as a limited company in Hole, Buskerud with organisation number 930791407. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eierskap i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 67,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2024

Revenue
NOK 67,000
Operating profit
NOK 19,000
Equity
NOK 81,000
Est. value
NOK 111,000

Financial health · 2024

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

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

Who owns HØLABRØTIN INVEST AS?

ERIK SLETAKER LANDMARK
HØLABRØTIN INVEST AS
NOK 67,000 rev. · NOK 19,000 profit

HØLABRØTIN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HØLABRØTIN INVEST AS own?

HØLABRØTIN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HØLABRØTIN INVEST AS

Who owns HØLABRØTIN INVEST AS?

ERIK SLETAKER LANDMARK is the largest registered owner, with 100.0%.

What is the revenue of HØLABRØTIN INVEST AS?

HØLABRØTIN INVEST AS had revenue of NOK 67,000 in 2024.

Who is the general manager of HØLABRØTIN INVEST AS?

Erik Sletaker Landmark is registered as general manager of HØLABRØTIN INVEST AS.

Where is HØLABRØTIN INVEST AS based?

HØLABRØTIN INVEST AS has its business address in Røyse.

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.