BIZTRAC BETA
Construction of residential and non-residential buildings

MESTERBYGG MOSS AS

Org. no. 991603026 Limited company (AS) Moss Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 43.5m
Operating profit NOK 110,000
Equity NOK 3.2m
Incorporated 2007
Employees 18
Share capital NOK 100,000

MESTERBYGG MOSS AS is registered as a limited company in Moss, Østfold with organisation number 991603026. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2007 and has 18 registered employees. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Handel- og byggevirksomhet, herunder kjøp, salg og utleie av fast eiendom, samt deltagelse i andre selskaper med beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 43.5m in revenue and NOK 110,000 in operating profit.

Key figures · 2025

Revenue
NOK 43.5m
Operating profit
NOK 110,000
Equity
NOK 3.2m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns MESTERBYGG MOSS AS?

MORSA HOLDING AS
MESTERBYGG MOSS AS
NOK 43.5m rev. · NOK 110,000 profit

MESTERBYGG MOSS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MESTERBYGG MOSS AS

Who owns MESTERBYGG MOSS AS?

MORSA HOLDING AS is the largest registered owner, with 40.0%.

What is the revenue of MESTERBYGG MOSS AS?

MESTERBYGG MOSS AS had revenue of NOK 43.5m in 2025.

Who is the general manager of MESTERBYGG MOSS AS?

Jan Lexerød is registered as general manager of MESTERBYGG MOSS AS.

Where is MESTERBYGG MOSS AS based?

MESTERBYGG MOSS AS has its business address in Moss.

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.