biztrac. BETA
COMPANY REGISTER PROFILE
986157913 ORG. NO. 2025 ACCOUNTS 12 SECTIONS
In liquidation UPDATED 03.10.2026
⚠HETLANDHUS AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Retail sale of household articles and equipment n.e.c.

HETLANDHUS AS

Org. no. 986157913 Limited company (AS) Oslo Incorporated 2003 In liquidation
Ownership graph ↗
Operating profit NOK −42,000
Equity NOK 12.0m
Incorporated 2003
Share capital NOK 10.1m

Signals

3 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−42k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HETLANDHUS AS is registered as a limited company in Oslo, Oslo with organisation number 986157913. The business is classified under retail sale of household articles and equipment n.e.c. (NACE 47.559). The company was incorporated in 2003. Registered share capital is NOK 10.1m, divided into 10100000 shares. The company's stated purpose is: “Byggevirksomhet, handel og annen virksomhet i tilknytning til dette.”.

Former names: HUSEBY KJØKKENMAKERI AS

Key figures · 2025

Operating profit
NOK −42,000
▲ +37 %
Equity
NOK 12.0m
▲ +2 %

Financial health · 2025

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

Who owns HETLANDHUS AS?

HETLANDHUS AS
· NOK −42,000 profit

HETLANDHUS AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HETLANDHUS AS er morselskap for 67 datterselskaper:

Frequently asked questions about HETLANDHUS AS

Who owns HETLANDHUS AS?

OBOS BLOCK WATNE AS is the largest registered owner, with 100.0%.

Where is HETLANDHUS AS based?

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