BIZTRAC BETA
Rental and operating of own or leased real estate

VIKEGATA 17 AS

Org. no. 961277213 Limited company (AS) Ørsta Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 66,000
Equity NOK 3.4m
Incorporated 1991
Share capital NOK 3.6m

VIKEGATA 17 AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 961277213. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991. Registered share capital is NOK 3.6m, divided into 3635 shares. The company's stated purpose is: “Investering og utleige av fast eigedom og å delta i andre selskap med liknande føremål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 66,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 66,000
Equity
NOK 3.4m
Est. value
NOK 2.5m

Financial health · 2024

Liquidity
0.42
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
43.7%
Very good
Equity as a share of total capital

Who owns VIKEGATA 17 AS?

VEIBERG HOLDING AS
VIKEGATA 17 AS
NOK 1.5m rev. · NOK 66,000 profit

VIKEGATA 17 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIKEGATA 17 AS own?

VIKEGATA 17 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIKEGATA 17 AS

Who owns VIKEGATA 17 AS?

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

What is the revenue of VIKEGATA 17 AS?

VIKEGATA 17 AS had revenue of NOK 1.5m in 2024.

Who is the general manager of VIKEGATA 17 AS?

Petter Myklebust is registered as general manager of VIKEGATA 17 AS.

Where is VIKEGATA 17 AS based?

VIKEGATA 17 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.