BIZTRAC BETA
Rental and operating of own or leased real estate

WELHAVENSGT. 1 AS

Org. no. 994867156 Limited company (AS) Gjøvik Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 684,000
Operating profit NOK 315,000
Equity NOK 3.3m
Incorporated 2009
Share capital NOK 132,000

WELHAVENSGT. 1 AS is registered as a limited company in Gjøvik, Innlandet with organisation number 994867156. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 132,000, divided into 131880 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå investeringer, herunder kjøp, salg og drift av faste eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 684,000 in revenue and NOK 315,000 in operating profit.

Key figures · 2025

Revenue
NOK 684,000
Operating profit
NOK 315,000
Equity
NOK 3.3m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns WELHAVENSGT. 1 AS?

KRISTOFFER ERIK AMUNDSEN
WELHAVENSGT. 1 AS
NOK 684,000 rev. · NOK 315,000 profit

WELHAVENSGT. 1 AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about WELHAVENSGT. 1 AS

Who owns WELHAVENSGT. 1 AS?

KRISTOFFER ERIK AMUNDSEN is the largest registered owner, with 99.9%.

What is the revenue of WELHAVENSGT. 1 AS?

WELHAVENSGT. 1 AS had revenue of NOK 684,000 in 2025.

Who is the general manager of WELHAVENSGT. 1 AS?

Oddleif Amundsen is registered as general manager of WELHAVENSGT. 1 AS.

Where is WELHAVENSGT. 1 AS based?

WELHAVENSGT. 1 AS has its business address in Gjøvik.

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.