BIZTRAC BETA
Development of building projects

MESTERHUS TØNSBERG AS

Org. no. 966623381 Limited company (AS) Tønsberg Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 5.9m
Operating profit NOK −69,000
Equity NOK 1.3m
Incorporated 1993
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−69k kr).

MESTERHUS TØNSBERG AS is registered as a limited company in Tønsberg, Vestfold with organisation number 966623381. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1993. Registered share capital is NOK 500,000, divided into 5000 shares. The company's stated purpose is: “Ivareta aksjonærenes felles interesser innenfor bygg- og anleggsektoren på områdene salg og markedsføring, planlegging, administrasjon av virksomhet i felles regi samt alt hva hermed står i naturlig forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.9m in revenue and NOK −69,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.9m
Operating profit
NOK −69,000
Equity
NOK 1.3m
Est. value
NOK 9.2m

Financial health · 2024

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

Who owns MESTERHUS TØNSBERG AS?

H W ANDERSEN HOLDING AS
MESTERHUS TØNSBERG AS
NOK 5.9m rev. · NOK −69,000 profit

MESTERHUS TØNSBERG AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about MESTERHUS TØNSBERG AS

Who owns MESTERHUS TØNSBERG AS?

H W ANDERSEN HOLDING AS is the largest registered owner, with 20.0%.

What is the revenue of MESTERHUS TØNSBERG AS?

MESTERHUS TØNSBERG AS had revenue of NOK 5.9m in 2024.

Where is MESTERHUS TØNSBERG AS based?

MESTERHUS TØNSBERG AS has its business address in Tønsberg.

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.