BIZTRAC BETA
Construction of residential and non-residential buildings

MESTERBYGG AS

Org. no. 977467411 Limited company (AS) Lørenskog Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK 138,000
Equity NOK 1.8m
Incorporated 1997
Employees 6
Share capital NOK 150,000

MESTERBYGG AS is registered as a limited company in Lørenskog, Akershus with organisation number 977467411. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1997 and has 6 registered employees. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Kjøp, salg, forvaltning og utleie av fast eiendom, samt tømrer- og entreprenørvirksomhet og virksomhet som står i naturlig forbindelse med dette, herunder konsulentvirksomhet, samt å erverve eierandeler i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK 138,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK 138,000
Equity
NOK 1.8m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns MESTERBYGG AS?

JONNY VONK
MESTERBYGG AS
NOK 7.0m rev. · NOK 138,000 profit

MESTERBYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MESTERBYGG AS

Who owns MESTERBYGG AS?

JONNY VONK is the largest registered owner, with 70.0%.

What is the revenue of MESTERBYGG AS?

MESTERBYGG AS had revenue of NOK 7.0m in 2024.

Who is the general manager of MESTERBYGG AS?

Jonny Vonk is registered as general manager of MESTERBYGG AS.

Where is MESTERBYGG AS based?

MESTERBYGG AS has its business address in Lørenskog.

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.