BIZTRAC BETA
Other technical consultancy

ONEVISION CONSULTING AS

Org. no. 928717291 Limited company (AS) Tysvær Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 540,000
Equity NOK 68,000
Incorporated 2022
Share capital NOK 30,000

ONEVISION CONSULTING AS is registered as a limited company in Tysvær, Rogaland with organisation number 928717291. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Teknisk rådgivning og konsulenttjenester innen olje og gass, energi og andre fagområder.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 540,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 540,000
Equity
NOK 68,000
Est. value
NOK 2.0m

Financial health · 2025

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

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

Who owns ONEVISION CONSULTING AS?

RUBEN MUNZER HOLDING AS
ONEVISION CONSULTING AS
NOK 2.3m rev. · NOK 540,000 profit

ONEVISION CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ONEVISION CONSULTING AS

Who owns ONEVISION CONSULTING AS?

RUBEN MUNZER HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ONEVISION CONSULTING AS?

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

Who is the general manager of ONEVISION CONSULTING AS?

Ruben Münzer is registered as general manager of ONEVISION CONSULTING AS.

Where is ONEVISION CONSULTING AS based?

ONEVISION CONSULTING AS has its business address in Førresfjorden.

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.