BIZTRAC BETA
Construction of residential and non-residential buildings

MESTERLANDA AS

Org. no. 922906823 Limited company (AS) Asker Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 32.0m
Operating profit NOK 1.7m
Equity NOK 1.6m
Incorporated 2019
Employees 25
Share capital NOK 100,000

MESTERLANDA AS is registered as a limited company in Asker, Akershus with organisation number 922906823. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019 and has 25 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Tømrervirksomhet, salg av varer og tjenester innen håndverk og bygg, entreprenør, utleie av lager, anleggsutstyr og annen utleie knyttet til næringen. Prosjektering og oppføring av beboelseshus for kunder.”. The most recent filed accounts, for the 2024 financial year, show NOK 32.0m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 32.0m
Operating profit
NOK 1.7m
Equity
NOK 1.6m
Est. value
NOK 6.5m

Financial health · 2024

Liquidity
1.21
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.6%
Good
Equity as a share of total capital

Who owns MESTERLANDA AS?

ØYVIND LANDA
MESTERLANDA AS
NOK 32.0m rev. · NOK 1.7m profit

MESTERLANDA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MESTERLANDA AS

Who owns MESTERLANDA AS?

ØYVIND LANDA is the largest registered owner, with 80.0%.

What is the revenue of MESTERLANDA AS?

MESTERLANDA AS had revenue of NOK 32.0m in 2024.

Who is the general manager of MESTERLANDA AS?

Øyvind Landa is registered as general manager of MESTERLANDA AS.

Where is MESTERLANDA AS based?

MESTERLANDA AS has its business address in Asker.

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.