BIZTRAC BETA
Manufacture of wire products, chain and springs

MYHRE LÅS- OG MEK VERKSTED AS

Org. no. 940317045 Limited company (AS) Nittedal Incorporated 1986 Active
Ownership graph ↗
Revenue 2024 NOK 9.8m
Operating profit NOK 190,000
Equity NOK 1.0m
Incorporated 1986
Employees 11
Share capital NOK 102,000

MYHRE LÅS- OG MEK VERKSTED AS is registered as a limited company in Nittedal, Akershus with organisation number 940317045. The business is classified under manufacture of wire products, chain and springs (NACE 25.930). The company was incorporated in 1986 and has 11 registered employees. Registered share capital is NOK 102,000. The company's stated purpose is: “Drive produsksjon og låsservice.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.8m in revenue and NOK 190,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.8m
Operating profit
NOK 190,000
Equity
NOK 1.0m
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.7%
Satisfactory
Equity as a share of total capital

Who owns MYHRE LÅS- OG MEK VERKSTED AS?

VIDAR DAGFINN MYHRE
MYHRE LÅS- OG MEK VERKSTED AS
NOK 9.8m rev. · NOK 190,000 profit

MYHRE LÅS- OG MEK VERKSTED AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about MYHRE LÅS- OG MEK VERKSTED AS

Who owns MYHRE LÅS- OG MEK VERKSTED AS?

VIDAR DAGFINN MYHRE is the largest registered owner, with 50.0%.

What is the revenue of MYHRE LÅS- OG MEK VERKSTED AS?

MYHRE LÅS- OG MEK VERKSTED AS had revenue of NOK 9.8m in 2024.

Who is the general manager of MYHRE LÅS- OG MEK VERKSTED AS?

Vidar Dagfinn Myhre is registered as general manager of MYHRE LÅS- OG MEK VERKSTED AS.

Where is MYHRE LÅS- OG MEK VERKSTED AS based?

MYHRE LÅS- OG MEK VERKSTED AS has its business address in Nittedal.

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.