BIZTRAC BETA
Other construction installation

INGVALDSEN & MYRSTUEN AS

Org. no. 813261472 Limited company (AS) Gjøvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK 474,000
Equity NOK 1.4m
Incorporated 2014
Share capital NOK 200,000

INGVALDSEN & MYRSTUEN AS is registered as a limited company in Gjøvik, Innlandet with organisation number 813261472. The business is classified under other construction installation (NACE 43.240). The company was incorporated in 2014. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Service og installasjoner av maskinelt utstyr til produksjon av ventilasjonsprodukter, samt opplæring og kursing av operatører for slikt utstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK 474,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK 474,000
Equity
NOK 1.4m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns INGVALDSEN & MYRSTUEN AS?

KIM ERIK INGVALDSEN
INGVALDSEN & MYRSTUEN AS
NOK 4.4m rev. · NOK 474,000 profit

INGVALDSEN & MYRSTUEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about INGVALDSEN & MYRSTUEN AS

Who owns INGVALDSEN & MYRSTUEN AS?

KIM ERIK INGVALDSEN is the largest registered owner, with 50.0%.

What is the revenue of INGVALDSEN & MYRSTUEN AS?

INGVALDSEN & MYRSTUEN AS had revenue of NOK 4.4m in 2024.

Who is the general manager of INGVALDSEN & MYRSTUEN AS?

Kim Erik Ingvaldsen is registered as general manager of INGVALDSEN & MYRSTUEN AS.

Where is INGVALDSEN & MYRSTUEN AS based?

INGVALDSEN & MYRSTUEN AS has its business address in Hunndalen.

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.