BIZTRAC BETA
COMPANY REGISTER PROFILE
899235622 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Buying and selling of own real estate

VIMON AS

Org. no. 899235622 Limited company (AS) Tysvær Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 20,000
Operating profit NOK 16,000
Equity NOK −337,000
Incorporated 2012
Share capital NOK 30,000

Signals

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

VIMON AS is registered as a limited company in Tysvær, Rogaland with organisation number 899235622. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak, samt annen virksomhet som naturlig faller sammen med dette. Investering i eiendom og andre kapitalplasseringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 20,000 in revenue and NOK 16,000 in operating profit.

Key figures · 2025

Revenue
NOK 20,000
Operating profit
NOK 16,000
Equity
NOK −337,000
Est. value
NOK 121,000

Financial health · 2024

Liquidity
6.11
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-755.6%
Weak
Equity as a share of total capital

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

Who owns VIMON AS?

VIDAR MONSEN
VIMON AS
NOK 20,000 rev. · NOK 16,000 profit

VIMON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIMON AS

Who owns VIMON AS?

VIDAR MONSEN is the largest registered owner, with 100.0%.

What is the revenue of VIMON AS?

VIMON AS had revenue of NOK 20,000 in 2025.

Where is VIMON AS based?

VIMON 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.