BIZTRAC BETA
Roofing activities

MESTERTAKET AS

Org. no. 922994145 Limited company (AS) Sandefjord Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 31.8m
Operating profit NOK −5.0m
Equity NOK −4.6m
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−4,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5,0 mill kr).

MESTERTAKET AS is registered as a limited company in Sandefjord, Vestfold with organisation number 922994145. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tak- og blikkarbeid, snekring, maling, takfornying og det som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 31.8m in revenue and NOK −5.0m in operating profit.

Key figures · 2024

Revenue
NOK 31.8m
Operating profit
NOK −5.0m
Equity
NOK −4.6m

Financial health · 2024

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-136.0%
Weak
Equity as a share of total capital

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

Who owns MESTERTAKET AS?

BO-TETT AS
MESTERTAKET AS
NOK 31.8m rev. · NOK −5.0m profit

MESTERTAKET AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about MESTERTAKET AS

Who owns MESTERTAKET AS?

BO-TETT AS is the largest registered owner, with 33.3%.

What is the revenue of MESTERTAKET AS?

MESTERTAKET AS had revenue of NOK 31.8m in 2024.

Who is the general manager of MESTERTAKET AS?

Tom Thoresen is registered as general manager of MESTERTAKET AS.

Where is MESTERTAKET AS based?

MESTERTAKET AS has its business address in Sandefjord.

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.