BIZTRAC BETA
Rental and operating of own or leased real estate

VIKEGATA EIGEDOM AS

Org. no. 924021977 Limited company (AS) Ørsta Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 364,000
Operating profit NOK 36,000
Equity NOK −261,000
Incorporated 2019
Share capital NOK 37,000

Signals

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

VIKEGATA EIGEDOM AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 924021977. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 37,000, divided into 5714 shares. The company's stated purpose is: “Investering i eiendom og andre langsiktige investeringsobjekter. Selskapet kan investere i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 364,000 in revenue and NOK 36,000 in operating profit.

Key figures · 2025

Revenue
NOK 364,000
Operating profit
NOK 36,000
Equity
NOK −261,000
Est. value
NOK 386,000

Financial health · 2025

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

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

Who owns VIKEGATA EIGEDOM AS?

KROSELMA AS
VIKEGATA EIGEDOM AS
NOK 364,000 rev. · NOK 36,000 profit

VIKEGATA EIGEDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIKEGATA EIGEDOM AS

Who owns VIKEGATA EIGEDOM AS?

KROSELMA AS is the largest registered owner, with 50.0%.

What is the revenue of VIKEGATA EIGEDOM AS?

VIKEGATA EIGEDOM AS had revenue of NOK 364,000 in 2025.

Where is VIKEGATA EIGEDOM AS based?

VIKEGATA EIGEDOM AS has its business address in Ørsta.

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.