BIZTRAC BETA
Manufacture of locks and hinges

LÅSESMEDMESTER HVEDING AS

Org. no. 988980048 Limited company (AS) Sola Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 333,000
Equity NOK 2.2m
Incorporated 2005
Share capital NOK 100,000

LÅSESMEDMESTER HVEDING AS is registered as a limited company in Sola, Rogaland with organisation number 988980048. The business is classified under manufacture of locks and hinges (NACE 25.620). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapet utøver virksomhet innen lås- og beslag og sikkerhetsbransjen med hovedvekt på design og funksjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 333,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 333,000
Equity
NOK 2.2m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns LÅSESMEDMESTER HVEDING AS?

BÅRD EILIF HVEDING
LÅSESMEDMESTER HVEDING AS
NOK 3.6m rev. · NOK 333,000 profit

LÅSESMEDMESTER HVEDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LÅSESMEDMESTER HVEDING AS

Who owns LÅSESMEDMESTER HVEDING AS?

BÅRD EILIF HVEDING is the largest registered owner, with 100.0%.

What is the revenue of LÅSESMEDMESTER HVEDING AS?

LÅSESMEDMESTER HVEDING AS had revenue of NOK 3.6m in 2025.

Who is the general manager of LÅSESMEDMESTER HVEDING AS?

Bård Eilif Hveding is registered as general manager of LÅSESMEDMESTER HVEDING AS.

Where is LÅSESMEDMESTER HVEDING AS based?

LÅSESMEDMESTER HVEDING AS has its business address in Sola.

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.