BIZTRAC BETA
Computer consultancy and computer facilities management activities

HBB CONSULT AS

Org. no. 831964162 Limited company (AS) Jevnaker Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 463,000
Operating profit NOK 12,000
Equity NOK 53,000
Incorporated 2023
Share capital NOK 30,000

HBB CONSULT AS is registered as a limited company in Jevnaker, Akershus with organisation number 831964162. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 463,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 463,000
Operating profit
NOK 12,000
Equity
NOK 53,000
Est. value
NOK 95,000

Financial health · 2025

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

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

Who owns HBB CONSULT AS?

ØYVIND BAKKEN
HBB CONSULT AS
NOK 463,000 rev. · NOK 12,000 profit

HBB CONSULT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HBB CONSULT AS

Who owns HBB CONSULT AS?

ØYVIND BAKKEN is the largest registered owner, with 100.0%.

What is the revenue of HBB CONSULT AS?

HBB CONSULT AS had revenue of NOK 463,000 in 2025.

Who is the general manager of HBB CONSULT AS?

Øyvind Bakken is registered as general manager of HBB CONSULT AS.

Where is HBB CONSULT AS based?

HBB CONSULT AS has its business address in Jevnaker.

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.