BIZTRAC BETA
COMPANY REGISTER PROFILE
932675625 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

VIKINGEN AS

Org. no. 932675625 Limited company (AS) Hareid Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 811,000
Operating profit NOK 617,000
Equity NOK 2.6m
Incorporated 1982
Share capital NOK 150,000

VIKINGEN AS is registered as a limited company in Hareid, Møre og Romsdal with organisation number 932675625. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1982. Registered share capital is NOK 150,000, divided into 10 shares. The company's stated purpose is: “Handel og det som står i forbindelse med dette, herunder å delta i andre selskaper, kjøpe, eie og forvalte fast eiendom og å drive annen økonomisk virksomhet. ”. The most recent filed accounts, for the 2025 financial year, show NOK 811,000 in revenue and NOK 617,000 in operating profit.

Key figures · 2025

Revenue
NOK 811,000
▲ +18 %
Operating profit
NOK 617,000
▲ +41 %
Equity
NOK 2.6m
▲ +9 %
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
8.34
Very good
Current assets ÷ current liabilities
Profitability
17.2%
Very good
Return on total assets
Solidity
67.5%
Very good
Equity as a share of total capital

Who owns VIKINGEN AS?

VIKINGEN AS
NOK 811,000 rev. · NOK 617,000 profit

VIKINGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIKINGEN AS

Who owns VIKINGEN AS?

JOHANNES CHRISTIAN RIISE is the largest registered owner, with 100.0%.

What is the revenue of VIKINGEN AS?

VIKINGEN AS had revenue of NOK 811,000 in 2025.

Who is the general manager of VIKINGEN AS?

Johannes Christian Riise is registered as general manager of VIKINGEN AS.

Where is VIKINGEN AS based?

VIKINGEN AS has its business address in Hareid.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.