BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER LUND AS

Org. no. 935861381 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 476,000
Equity NOK 396,000
Incorporated 2025
Share capital NOK 30,000

BYGGMESTER LUND AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935861381. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “å utvikle, hus, bygge- som omhandler, rivingsarbeide, renovering av bygg, byggevirksomhet som omhandler, snekker, gjenbruk og engasjere seg i selskaper innen samme bransjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 476,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 476,000
Equity
NOK 396,000
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns BYGGMESTER LUND AS?

HANS OLE FRISNES
BYGGMESTER LUND AS
NOK 1.1m rev. · NOK 476,000 profit

BYGGMESTER LUND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER LUND AS

Who owns BYGGMESTER LUND AS?

HANS OLE FRISNES is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER LUND AS?

BYGGMESTER LUND AS had revenue of NOK 1.1m in 2025.

Who is the general manager of BYGGMESTER LUND AS?

Hans Ole Frisnes is registered as general manager of BYGGMESTER LUND AS.

Where is BYGGMESTER LUND AS based?

BYGGMESTER LUND AS has its business address in Trondheim.

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.