BIZTRAC BETA
Arts creation activities in literature

H OUSTAD AS

Org. no. 881168162 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK −342,000
Equity NOK 22.3m
Incorporated 1999
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−342k kr).

H OUSTAD AS is registered as a limited company in Oslo, Oslo with organisation number 881168162. The business is classified under arts creation activities in literature (NACE 90.111). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet innen presse, medier og landbruksvirksomhet, kurs og informasjonsformidling, kjøp-, salgs-, import og eksportvirksomhet foruten finansforvaltning og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK −342,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK −342,000
Equity
NOK 22.3m
Est. value
NOK 13.6m

Financial health · 2024

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

Who owns H OUSTAD AS?

HANS OLA HØRSAND OUSTAD
H OUSTAD AS
NOK 2.3m rev. · NOK −342,000 profit

H OUSTAD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does H OUSTAD AS own?

H OUSTAD AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about H OUSTAD AS

Who owns H OUSTAD AS?

HANS OLA HØRSAND OUSTAD is the largest registered owner, with 100.0%.

What is the revenue of H OUSTAD AS?

H OUSTAD AS had revenue of NOK 2.3m in 2024.

Where is H OUSTAD AS based?

H OUSTAD 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 15.06.2026.

Report a problem

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