BIZTRAC BETA
COMPANY REGISTER PROFILE
933526011 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Business and other management consultancy activities

HOÅS CONSULT AS

Org. no. 933526011 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 391,000
Equity NOK 345,000
Incorporated 2024
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-03-23 Adresseendring registrert 2026-03-23.

HOÅS CONSULT AS is registered as a limited company in Oslo, Oslo with organisation number 933526011. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Konsulenttjenester innenfor prosjektledelse, jernbanevirksomhet og vann- og avløp.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 391,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 391,000
Equity
NOK 345,000
Est. value
NOK 1.8m

Financial health · 2025

Liquidity
1.48
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
32.6%
Good
Equity as a share of total capital

Who owns HOÅS CONSULT AS?

HÅKON HOÅS
HOÅS CONSULT AS
NOK 2.0m rev. · NOK 391,000 profit

HOÅS CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOÅS CONSULT AS

Who owns HOÅS CONSULT AS?

HÅKON HOÅS is the largest registered owner, with 100.0%.

What is the revenue of HOÅS CONSULT AS?

HOÅS CONSULT AS had revenue of NOK 2.0m in 2025.

Who is the general manager of HOÅS CONSULT AS?

Håkon Hoås is registered as general manager of HOÅS CONSULT AS.

Where is HOÅS CONSULT AS based?

HOÅS CONSULT 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.