BIZTRAC BETA
Wholesale of other machinery and equipment

HESTBRAATEN CONSULTING AS

Org. no. 923857281 Limited company (AS) Lillestrøm Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2019
Share capital NOK 30,000

HESTBRAATEN CONSULTING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 923857281. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Import av maskiner og utstyr. Salg av maskiner og utstyr. Konsulent tjenester for offentlige innkjøp.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 38,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HESTBRAATEN CONSULTING AS?

JAN HESTBRÅTEN
HESTBRAATEN CONSULTING AS
NOK 0 rev. · NOK 0 profit

HESTBRAATEN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HESTBRAATEN CONSULTING AS

Who owns HESTBRAATEN CONSULTING AS?

JAN HESTBRÅTEN is the largest registered owner, with 100.0%.

What is the revenue of HESTBRAATEN CONSULTING AS?

HESTBRAATEN CONSULTING AS had revenue of NOK 0 in 2025.

Who is the general manager of HESTBRAATEN CONSULTING AS?

Jan Hestbråten is registered as general manager of HESTBRAATEN CONSULTING AS.

Where is HESTBRAATEN CONSULTING AS based?

HESTBRAATEN CONSULTING AS has its business address in Sørumsand.

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.