BIZTRAC BETA
Computer consultancy and computer facilities management activities

HELLAND CONSULTING AS

Org. no. 931950452 Limited company (AS) Stavanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 5.5m
Operating profit NOK 578,000
Equity NOK 584,000
Incorporated 2023
Share capital NOK 30,000

HELLAND CONSULTING AS is registered as a limited company in Stavanger, Rogaland with organisation number 931950452. 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 100000 shares. The company's stated purpose is: “Konsulentvirksomhet tilknyttet informasjonsteknologi, samt salg av produkter og tjenester tilknyttet dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.5m in revenue and NOK 578,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.5m
Operating profit
NOK 578,000
Equity
NOK 584,000
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns HELLAND CONSULTING AS?

HELLAND EMPIRE AS
HELLAND CONSULTING AS
NOK 5.5m rev. · NOK 578,000 profit

HELLAND CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELLAND CONSULTING AS

Who owns HELLAND CONSULTING AS?

HELLAND EMPIRE AS is the largest registered owner, with 100.0%.

What is the revenue of HELLAND CONSULTING AS?

HELLAND CONSULTING AS had revenue of NOK 5.5m in 2025.

Who is the general manager of HELLAND CONSULTING AS?

Jan Erik Helland is registered as general manager of HELLAND CONSULTING AS.

Where is HELLAND CONSULTING AS based?

HELLAND CONSULTING AS has its business address in Hundvåg.

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.