BIZTRAC BETA
Other technical consultancy

OPSHAUG CONSULTING AS

Org. no. 923832009 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 689,000
Equity NOK 396,000
Incorporated 2019
Share capital NOK 30,000

OPSHAUG CONSULTING AS is registered as a limited company in Bergen, Vestland with organisation number 923832009. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester og teknologiutvikling til industri og oljebransje. Salg og distribusjon, samt utleie av varer og tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 689,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 689,000
Equity
NOK 396,000
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
51.1%
Very good
Equity as a share of total capital

Who owns OPSHAUG CONSULTING AS?

OPSHAUG AS
OPSHAUG CONSULTING AS
NOK 2.3m rev. · NOK 689,000 profit

OPSHAUG CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OPSHAUG CONSULTING AS er morselskap for 1 datterselskap:

Frequently asked questions about OPSHAUG CONSULTING AS

Who owns OPSHAUG CONSULTING AS?

OPSHAUG AS is the largest registered owner, with 100.0%.

What is the revenue of OPSHAUG CONSULTING AS?

OPSHAUG CONSULTING AS had revenue of NOK 2.3m in 2025.

Who is the general manager of OPSHAUG CONSULTING AS?

Ole Andreas Rødland Opshaug is registered as general manager of OPSHAUG CONSULTING AS.

Where is OPSHAUG CONSULTING AS based?

OPSHAUG CONSULTING AS has its business address in Tertnes.

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.