BIZTRAC BETA
COMPANY REGISTER PROFILE
992733721 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

HLK INVEST AS

Org. no. 992733721 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −1.6m
Equity NOK 58.2m
Incorporated 2008
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,6 mill kr).

HLK INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 992733721. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 400,000, divided into 2 shares. The company's stated purpose is: “Investere i verdipapirer og fast eiendom.”.

Key figures · 2025

Operating profit
NOK −1.6m
▼ −398 %
Equity
NOK 58.2m
▲ +4 %
Est. value
NOK 49.1m

Financial health · 2025

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

Who owns HLK INVEST AS?

HLK INVEST AS
· NOK −1.6m profit

HLK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HLK INVEST AS

Who owns HLK INVEST AS?

HENNING LEO KNUDSEN is the largest registered owner, with 100.0%.

Where is HLK INVEST AS based?

HLK INVEST AS has its business address in Oslo.

Property

Business address Granveien 15E, 1178 Oslo
Cadastral unit 301-157/85/0/0
Building Rekkehus · 1 unit

3 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.