biztrac. BETA
COMPANY REGISTER PROFILE
935324734 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

BYGGMESTER ANDERSEN AS

Org. no. 935324734 Limited company (AS) Sandefjord Incorporated 2025 Active
Revenue 2025 NOK 736,000
Operating profit NOK 127,000
Equity NOK 128,000
Incorporated 2025
Share capital NOK 30,000

BYGGMESTER ANDERSEN AS is registered as a limited company in Sandefjord, Vestfold with organisation number 935324734. 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 30000 shares. The company's stated purpose is: “Tilby tømrertjenester, inkludert, men ikke begrenset til, oppføring, vedlikehold, og reparasjon av bygninger, konstruksjon av trestrukturer, og andre relaterte tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 736,000 in revenue and NOK 127,000 in operating profit.

Key figures · 2025

Revenue
NOK 736,000
Operating profit
NOK 127,000
Equity
NOK 128,000
Est. value
NOK 417,000

Financial health · 2025

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

Who owns BYGGMESTER ANDERSEN AS?

BYGGMESTER ANDERSEN AS
NOK 736,000 rev. · NOK 127,000 profit

BYGGMESTER ANDERSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER ANDERSEN AS

Who owns BYGGMESTER ANDERSEN AS?

KEVIN ANDERSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER ANDERSEN AS?

BYGGMESTER ANDERSEN AS had revenue of NOK 736,000 in 2025.

Where is BYGGMESTER ANDERSEN AS based?

BYGGMESTER ANDERSEN 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.