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

HAGA CONSULTING AS

Org. no. 935701260 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 908,000
Operating profit NOK 862,000
Equity NOK 702,000
Incorporated 2025
Share capital NOK 30,000

HAGA CONSULTING AS is registered as a limited company in Oslo, Oslo with organisation number 935701260. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet samt annen virksomhet som naturlig faller inn under dette - inkludert publisering av bøker. Selskapet kan også investere i aksjer og andre investeringer, samt det som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 908,000 in revenue and NOK 862,000 in operating profit.

Key figures · 2025

Revenue
NOK 908,000
Operating profit
NOK 862,000
Equity
NOK 702,000
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns HAGA CONSULTING AS?

ÅSLAUG MARIE HAGA
HAGA CONSULTING AS
NOK 908,000 rev. · NOK 862,000 profit

HAGA CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAGA CONSULTING AS

Who owns HAGA CONSULTING AS?

ÅSLAUG MARIE HAGA is the largest registered owner, with 100.0%.

What is the revenue of HAGA CONSULTING AS?

HAGA CONSULTING AS had revenue of NOK 908,000 in 2025.

Where is HAGA CONSULTING AS based?

HAGA CONSULTING 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.