BIZTRAC BETA
Rental and operating of own or leased real estate

VIKEHORNET AS

Org. no. 933899721 Limited company (AS) Vanylven Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 235,000
Operating profit NOK −681,000
Equity NOK −553,000
Incorporated 2024
Share capital NOK 300,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−553k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−681k kr).

VIKEHORNET AS is registered as a limited company in Vanylven, Møre og Romsdal with organisation number 933899721. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og utleige av eigedom.”. The most recent filed accounts, for the 2025 financial year, show NOK 235,000 in revenue and NOK −681,000 in operating profit.

Key figures · 2025

Revenue
NOK 235,000
Operating profit
NOK −681,000
Equity
NOK −553,000

Financial health · 2025

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

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

Who owns VIKEHORNET AS?

A. M. VIK AS
VIKEHORNET AS
NOK 235,000 rev. · NOK −681,000 profit

VIKEHORNET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKEHORNET AS

Who owns VIKEHORNET AS?

A. M. VIK AS is the largest registered owner, with 100.0%.

What is the revenue of VIKEHORNET AS?

VIKEHORNET AS had revenue of NOK 235,000 in 2025.

Who is the general manager of VIKEHORNET AS?

Runar Vik is registered as general manager of VIKEHORNET AS.

Where is VIKEHORNET AS based?

VIKEHORNET AS has its business address in Syvde.

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.