BIZTRAC BETA
Construction of residential and non-residential buildings

FR MESTERBYGG AS

Org. no. 935204399 Limited company (AS) Flesberg Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 35,000
Equity NOK 57,000
Incorporated 2025
Share capital NOK 30,000

FR MESTERBYGG AS is registered as a limited company in Flesberg, Buskerud with organisation number 935204399. 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 300 shares. The company's stated purpose is: “Tømrer- og snekkervirksomhet og alt som står i forbindelse med dette, samt salg av andre tjenester innen bolig- og hytteservice.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 35,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 35,000
Equity
NOK 57,000
Est. value
NOK 145,000

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FR MESTERBYGG AS?

ANNA MAIJA FLAATA RØED
FR MESTERBYGG AS
NOK 1.2m rev. · NOK 35,000 profit

FR MESTERBYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FR MESTERBYGG AS

Who owns FR MESTERBYGG AS?

ANNA MAIJA FLAATA RØED is the largest registered owner, with 50.0%.

What is the revenue of FR MESTERBYGG AS?

FR MESTERBYGG AS had revenue of NOK 1.2m in 2025.

Who is the general manager of FR MESTERBYGG AS?

Sondre Flaata Røed is registered as general manager of FR MESTERBYGG AS.

Where is FR MESTERBYGG AS based?

FR MESTERBYGG AS has its business address in Lampeland.

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.