BIZTRAC BETA
Business and other management consultancy activities

COMPASS VISION AS

Org. no. 990422044 Limited company (AS) Tønsberg Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 138,000
Operating profit NOK 16,000
Equity NOK −203,000
Incorporated 2006
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−203k kr).

COMPASS VISION AS is registered as a limited company in Tønsberg, Vestfold with organisation number 990422044. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Bedriftsrådgivning og annen forretningsmessig tjenesteyting og alt som står i forbindelse med dette, herunder utvikling og eie av andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 138,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 138,000
Operating profit
NOK 16,000
Equity
NOK −203,000
Est. value
NOK 153,000

Financial health · 2025

Liquidity
0.32
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-213.1%
Weak
Equity as a share of total capital

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

Who owns COMPASS VISION AS?

BØRGE FURU
COMPASS VISION AS
NOK 138,000 rev. · NOK 16,000 profit

COMPASS VISION AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about COMPASS VISION AS

Who owns COMPASS VISION AS?

BØRGE FURU is the largest registered owner, with 45.0%.

What is the revenue of COMPASS VISION AS?

COMPASS VISION AS had revenue of NOK 138,000 in 2025.

Where is COMPASS VISION AS based?

COMPASS VISION AS has its business address in Barkåker.

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.