biztrac. BETA
COMPANY REGISTER PROFILE
921143184 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

HUSEKLEPP INVEST AS

Org. no. 921143184 Limited company (AS) Oslo Incorporated 2018 Active
Operating profit NOK −16,000
Equity NOK 424,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

HUSEKLEPP INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 921143184. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i eiendom og andre selskaper og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −16,000
▼ −22 %
Equity
NOK 424,000
▲ +162 %
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns HUSEKLEPP INVEST AS?

HUSEKLEPP INVEST AS
· NOK −16,000 profit

HUSEKLEPP INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HUSEKLEPP INVEST AS own?

HUSEKLEPP INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HUSEKLEPP INVEST AS

Who owns HUSEKLEPP INVEST AS?

Hans Alexander Huseklepp is the largest registered owner, with 100.0%.

Who is the general manager of HUSEKLEPP INVEST AS?

Hans Alexander Huseklepp is registered as general manager of HUSEKLEPP INVEST AS.

Where is HUSEKLEPP INVEST AS based?

HUSEKLEPP INVEST 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 03.10.2026.

Report a problem

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