BIZTRAC BETA
Computer consultancy and computer facilities management activities

ESPEN BRUUN CONSULTING AS

Org. no. 990478740 Limited company (AS) Holmestrand Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 716,000
Equity NOK 105,000
Incorporated 2006
Share capital NOK 100,000

ESPEN BRUUN CONSULTING AS is registered as a limited company in Holmestrand, Vestfold with organisation number 990478740. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selge konsulenttjenester for ERP systemer, samt annet som står i forbindelse med dette. ”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 716,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK 716,000
Equity
NOK 105,000
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns ESPEN BRUUN CONSULTING AS?

ESPEN BRUUN
ESPEN BRUUN CONSULTING AS
NOK 2.2m rev. · NOK 716,000 profit

ESPEN BRUUN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESPEN BRUUN CONSULTING AS

Who owns ESPEN BRUUN CONSULTING AS?

ESPEN BRUUN is the largest registered owner, with 100.0%.

What is the revenue of ESPEN BRUUN CONSULTING AS?

ESPEN BRUUN CONSULTING AS had revenue of NOK 2.2m in 2025.

Who is the general manager of ESPEN BRUUN CONSULTING AS?

Espen Bruun is registered as general manager of ESPEN BRUUN CONSULTING AS.

Where is ESPEN BRUUN CONSULTING AS based?

ESPEN BRUUN CONSULTING AS has its business address in Hof.

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.