BIZTRAC BETA
Construction of residential and non-residential buildings

MESTERBYGG ØSTFOLD AS

Org. no. 825537872 Limited company (AS) Fredrikstad Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −142,000
Equity NOK 73,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−142k kr).
  • Nylig endring 2026-07-02 Adresseendring registrert 2026-07-02.

MESTERBYGG ØSTFOLD AS is registered as a limited company in Fredrikstad, Østfold with organisation number 825537872. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Fremstilling/salg av byggmester tjenester og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp, salg og utleie av eiendom.”.

Key figures · 2024

Operating profit
NOK −142,000
Equity
NOK 73,000
Est. value
NOK 75,000

Financial health · 2024

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

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

Who owns MESTERBYGG ØSTFOLD AS?

PREUTZ HOLDING AS
MESTERBYGG ØSTFOLD AS
· NOK −142,000 profit

MESTERBYGG ØSTFOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MESTERBYGG ØSTFOLD AS

Who owns MESTERBYGG ØSTFOLD AS?

PREUTZ HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of MESTERBYGG ØSTFOLD AS?

Evaldas Stongvilas is registered as general manager of MESTERBYGG ØSTFOLD AS.

Where is MESTERBYGG ØSTFOLD AS based?

MESTERBYGG ØSTFOLD AS has its business address in Manstad.

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.