BIZTRAC BETA
COMPANY REGISTER PROFILE
889287772 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

HARELABB AS

Org. no. 889287772 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −28,000
Equity NOK 1.4m
Incorporated 2005
Share capital NOK 100,000

Signals

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

HARELABB AS is registered as a limited company in Oslo, Oslo with organisation number 889287772. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringsvirksomhet gjennom deltakelse i andre selskaper, samt investering i finansielle instrumenter og fast eiendom.”.

Key figures · 2025

Operating profit
NOK −28,000
▼ −4 %
Equity
NOK 1.4m
▲ +1 %
Est. value
NOK 873,000

Financial health · 2025

Liquidity
35.49
Very good
Current assets ÷ current liabilities
Profitability
1.4%
Weak
Return on total assets
Solidity
97.2%
Very good
Equity as a share of total capital

Who owns HARELABB AS?

HARELABB AS
· NOK −28,000 profit

HARELABB AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HARELABB AS

Who owns HARELABB AS?

JENS REIDAR HVEEM is the largest registered owner, with 100.0%.

Where is HARELABB AS based?

HARELABB AS has its business address in Oslo.

Property

Business address Ullevålsveien 71, 0454 Oslo
Cadastral unit 301-217/411/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 9 units

10 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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