BIZTRAC BETA
Business and other management consultancy activities

HILLESTAD-CONSULTING AS

Org. no. 920240607 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 5.1m
Operating profit NOK 187,000
Equity NOK 1.6m
Incorporated 2017
Share capital NOK 30,000

HILLESTAD-CONSULTING AS is registered as a limited company in Bærum, Akershus with organisation number 920240607. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulent og rådgivningstjenester innen varehandel, primært innen tekstil og sportsutstyr, og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.1m in revenue and NOK 187,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.1m
Operating profit
NOK 187,000
Equity
NOK 1.6m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns HILLESTAD-CONSULTING AS?

STEINAR HILLESTAD
HILLESTAD-CONSULTING AS
NOK 5.1m rev. · NOK 187,000 profit

HILLESTAD-CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HILLESTAD-CONSULTING AS

Who owns HILLESTAD-CONSULTING AS?

STEINAR HILLESTAD is the largest registered owner, with 100.0%.

What is the revenue of HILLESTAD-CONSULTING AS?

HILLESTAD-CONSULTING AS had revenue of NOK 5.1m in 2025.

Who is the general manager of HILLESTAD-CONSULTING AS?

Steinar Hillestad is registered as general manager of HILLESTAD-CONSULTING AS.

Where is HILLESTAD-CONSULTING AS based?

HILLESTAD-CONSULTING AS has its business address in Lommedalen.

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.